You can now [finally] open an html doc in the deafault browser.
JDIC, Java Desktop Integration Components provide more integration into the host desktop environment: integrating the native web browser, mail, registered document viewing applications and installation.
Includes things like a file browser, tray icons, and Screensaver SDK
A real online "social network" would not run on a central server.
A real online "social network" would also allow you to integrate friends lists from places like SlashDot, ICQ and even use lists of mobile phone numbers. And use them in a way that does not give anyone one person or company access to your social network's structure.
If Fedora was merely the first release of a (forked) RedHat spinoff distribution with no direct connection to Red Hat whatsoever then Fedora would be considered quite a good version 1.
Instead, Red Hat cannot shake its badge from Fedora, so high expectations are given for (what the layman would term) the "New Rad Hat Distro". High expectations lead to disappointment, and so Red Hat is blamed (directly or indirectly) for Fedora's many flaws (of various degree) found in version 1.
Who is it really up to maintain a distribution which is set to take a large portion of the desktop market? Who should bring up Red Hat's baby?
This is exactly why it's important to have standards to define "all possible situations" rather than just textual error messages: so that an automated system (i.e. your email client) can read the error message itself and deal with it apropriately, e.g. relay the error message back to the user in a way s/he can understand; or automatically retry with an alternative email adddress, etc. Without making a standard as robust as it should be, the clients can never become as powerful as they should be able to be.
It is possible to add to a standard and simplify it at the same time.
The use of RED GREEN and BLUE is very human-specific. These colours are just spikes on the colour spectrum that would be meaningless to any life form that doesn't happen to have RGB cones in their retinas.
I propose we start manufacturing monitors that emit exact light frequencies below, above and between the three emitted by CRTs today.
I'd be terribly embarrassed to have Visitors and no monitor they could use.
"why the hell did they use only two bytes to represent characters when they knew that we'd eventually make contact?"
Actually the Unicode Consortium did consider extraterrestrial life, and included UTF-32 as a standard, even though only the first two bytes are ever used (by Earth people).
"4,294,967,296 glyphs (minus a bunch of reserved ones) ought to be enough for any body."
Yep. Both The Language Instinct and How the Mind Works are great books.
Programming style was one thing that I thought about when reading the language instinct -- Some of the ideas of making good English could be equally applied to making clear and readable code. For instance, a sentence is much more readable when it's (uh, i forget the exact words here) left-based or right-based rather than having its recursion right in the middle of the sentence. I'm sure someone else could explain this better.. But I generally find code where you have a functions inside functions only hard to decipher if the inner functions are someone in the middle of the arguments is a function, and it has more functions as arguments in the middle of it.. or something like that... something similar goes for loops within loops. I could probably give some examples if I had the book in front of me.
Slashdot Mirror
You can now [finally] open an html doc in the deafault browser.
JDIC, Java Desktop Integration Components provide more integration into the host desktop environment: integrating the native web browser, mail, registered document viewing applications and installation.
Includes things like a file browser, tray icons, and Screensaver SDK
https://jdic.dev.java.net/
congrats on getting /.'d, bluecrab.
from everyone on #dreamcastdev
Easiest way to find taboos is to see what people laugh at.
Comedians talk about the (wrongness of) war in iraq these days.
They used to make a lot of gay jokes, but now it's become more acceptable to be gay and gay jokes have become taboo.
Racist jokes before that, when racism was more of an issue.
I've noticed people laugh most at what is most taboo. These are usually issues in society that need addressing.
A real online "social network" would not run on a central server.
A real online "social network" would also allow you to integrate friends lists from places like SlashDot, ICQ and even use lists of mobile phone numbers. And use them in a way that does not give anyone one person or company access to your social network's structure.
One without sufficient programming skills is still in a position to help by filing a bug report.
I certainly have.
If Fedora was merely the first release of a (forked) RedHat spinoff distribution with no direct connection to Red Hat whatsoever then Fedora would be considered quite a good version 1.
Instead, Red Hat cannot shake its badge from Fedora, so high expectations are given for (what the layman would term) the "New Rad Hat Distro". High expectations lead to disappointment, and so Red Hat is blamed (directly or indirectly) for Fedora's many flaws (of various degree) found in version 1.
Who is it really up to maintain a distribution which is set to take a large portion of the desktop market? Who should bring up Red Hat's baby?
Finding usability flaws in a linux distribution is like microwaving a kitten. Not very difficult, but it takes a lot of heart to do it.
Let's not focus on how much software sucks, but on what we can each individually do to make it better for all concerned.
I don't know if this is the reason, but in China, Japan and Korea: 4 is an unlucky number (like 13 in the west).
This is exactly why it's important to have standards to define "all possible situations" rather than just textual error messages: so that an automated system (i.e. your email client) can read the error message itself and deal with it apropriately, e.g. relay the error message back to the user in a way s/he can understand; or automatically retry with an alternative email adddress, etc. Without making a standard as robust as it should be, the clients can never become as powerful as they should be able to be.
It is possible to add to a standard and simplify it at the same time.
The use of RED GREEN and BLUE is very human-specific. These colours are just spikes on the colour spectrum that would be meaningless to any life form that doesn't happen to have RGB cones in their retinas.
I propose we start manufacturing monitors that emit exact light frequencies below, above and between the three emitted by CRTs today.
I'd be terribly embarrassed to have Visitors and no monitor they could use.
Actually the Unicode Consortium did consider extraterrestrial life, and included UTF-32 as a standard, even though only the first two bytes are ever used (by Earth people).
"4,294,967,296 glyphs (minus a bunch of reserved ones) ought to be enough for any body."
Yep. Both The Language Instinct and How the Mind Works are great books.
Programming style was one thing that I thought about when reading the language instinct -- Some of the ideas of making good English could be equally applied to making clear and readable code. For instance, a sentence is much more readable when it's (uh, i forget the exact words here) left-based or right-based rather than having its recursion right in the middle of the sentence. I'm sure someone else could explain this better.. But I generally find code where you have a functions inside functions only hard to decipher if the inner functions are someone in the middle of the arguments is a function, and it has more functions as arguments in the middle of it.. or something like that... something similar goes for loops within loops. I could probably give some examples if I had the book in front of me.
Anyone care to share their views?
Pengo (of pengo.net)