Freedesktop.org on KDE/Gnome, New Goals
fdo writes "OSNews has a long and juicy interview with the freedesktop.org developers regarding many aspects of their project, including interoperability between GNOME/KDE, the new X Server, the new Hardware Abstraction Layer library, accessibility, package management and in general, all things desktop."
Finally an excuse for even the most die-hard "oh no, I don't play games" programmer to go and get a decent graphics card, and not to use a Matrox G500 because it does 2 screens best
Simon
Physicists get Hadrons!
It's all very well thinking of the technical considerations (and there's quite a lot to consider), but don't forget to consider users and the usability of the desktop. Why do people use Microsoft products? because they're either forced to (at work) or they they find them easy to use (at home). Microsoft spends a lot of time ensuring their products are very usable and open source desktops need to do the same. Usability labs, heuristic evaluation etc.. all should be used (yes I am studying HCI before you ask).
Why do people use Microsoft products? because they're either forced to (at work) or they they find them easy to use (at home)
a) It came with their computer
b) It's "free" since it came with their computer
c) They don't know anything else
d) They are industry standards
e) They're the same as at work (familiarity)
f) They've had basic Windows training at work
g) Your poweruser friends likely know more Windows
h) It runs off-the-shelf software
i) It's inherently badly designed security-wise (security vs usability)
Pick any of the above, and I swear it's more of a reason than "easy to use". I bet 99%+ have never tried using a preinstalled, well configured Linux system (like the Windows install that came on their PC) at all. Without knowing the alternative, they have no basis to know that Windows is easier - they just assume so.
Kjella
Live today, because you never know what tomorrow brings
Havoc says "When you add drag and drop to an application you have a list of types that you support dragging or dropping, such as "text/plain". Applications simply don't agree on what these types are. So we need a registry of types documenting the type name and the format of the data transferred under that name."
x .html) Why reinvent that particular wheel? Most every system has a file 'mime.types' describing some portion of the IANA media types registry.
Isn't this what the IANA media types registry is for? (http://www.iana.org/assignments/media-types/inde