Slashdot Mirror
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."
WOW! Linux enters the late eighties!
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).
I don't know if GTK or KDE are too complex but these names sure are:
Rayiner Hashem, Havoc Pennington, Eugenia Loli-QueruWhat ever happen to Dick and Jane?
an ill wind that blows no good
Windows fanboy: "When will Linux look and behave exactly like WindowsXP and therefore be ready for the desktop?"
Linux fanboy: "When will the Longhorn fake-commandline-console look and behave like bash and therefore be ready for serious work?"
I can hardly wait for the next Freedesktop.org article FreeDesktop.org updates web pages, which by my calculations is due in about 3.4 hours.
But maybe I'm wrong. Maybe it will be:
FreeDesktop.org dreams about a better future (code release TBD)
FreeDesktop.org builds a better X (code release TBD)
FreeDesktop.org builds a better desktop (code release TBA)
FreeDesktop.org builds a better menu (code release TBD)
Ummm...
Last I knew a nipple was, by default, an ouput device
Time flies like an arrow, fruit flies like a banana.
Yeah, that's just what I need. Hours of tech support talking people through "sucking on breasts".
"What do you mean you don't know how? A 2 year old could do that!"
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
As often as I see stories like this and the tidal wave of resulting comments (and suggestions) it makes me a little frustrated that there is no on site that we can go to give 'Linux' feedback. I'd love to see the number 1 desktop complaint. We are absolutely brimming with comments (some I agree with, some I do not) and it seems like its all pretty wasted. We just end up rehashing our old opinions and Linux distro's keep doing what it is they think they need to do. Isn't that an unnecessary disconnect?
;-)
Give me a site with polls and commented stories! I think as a group we've at least got some interesting rants and I'd love for some of that feedback to be collected in some type of organised manner. Just imagine the flame wars!
Quack, quack.
I support a fork in Xfree86 because the regime that controls it has dropped the ball. There are many improvements that need to be made that have thusfar been prevented. At the same time I am very afraid that many of the things that were great about X will be lost in all of the commotion.
My greatest fear is that network transpancy will be lost because because everybody just wants to make X render faster on local hardware. Network transparency is what made X really great in the first place; without that, any replacement is totally worthless to me.
The second thing that made traditional X great was that it did not confuse its primary job as a graphical interpreter as being the window manager and middle ware. Each piece should separate, distinct, and intermatchable just like the ISO networking layers. Otherwise jobs will become so intertangled that the stack will no longer be cleanly configurable outside of a heterogenous stack of software. This is much like the situation with GNOME and KDE vs everything else is now -- great within them selves but not operable between them. The X server has a particular job to do and its new features should not try to take over what should be down by other parts of the stack
Don't just throw out the X Resource Database. Before QT and GTK came along breaking all of X tradition, the XRD was a great tool for configuring everything to behave they way that you want it to. Since these rouge widget sets have entered the scene, a vast majority of people have forgotten about what great tools these once were. I am not totally blind that XRD could use some modification but be sure to keep it in the spirit in which these tools were originally created (idea -- maybe using a structure built on an external DB like MySQL wouldn't be out of the question.)
X may be a very old technology like the first poster stated. Like unix tradition many things were very well thought out when it was created. All to often people are throwing away years of hard thought unix design for the latest fad with not even the faintest thought as to what they might be throwing away. No unix does not walk and talk just like the newer fancer interfaces of today -- there are good reasons for this. Some of these new wiper snappers are turning about and starting to do things the old fashion way because they found out that they were not so bad in the first place. Many of the things which at first seem archaic are actually built on much better paradigms then the newest fads. Advances in technology should be made in consideration of what was done before them. They should extend and enhance what has been done. They should not just throw everything out the window calling it old.
There are many things that need to be revamp in a new X server but please keep the good things in along with all of the improvements.
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
Bzzzt, wrong. Whether something is held in memory or not effects startup time more than responsiveness. The Win32 widget toolkit renders ridiculously fast because:
a) It's primitive and crude. For instance, it has NO layout management at all. Supporting internationalization is a pain in the arse. It uses UTF-16 rather than the somewhat more convenient (but more CPU intensive) UTF-8. Typically Windows desktops are not fully anti-aliased (yes yes, cleartype, not on by default) and when it is, Windows has better HW accel anyway.
b) Microsoft have a lot of people working on performance issues, and entire teams dedicated to optimization. We don't.
Only one GUI library would need to be loaded and everyone could use their favorite. It would certainly help for Windows ports as well. Thoughts?
No offence, but I think that's a bad idea. The thing to understand here is that wxWindows is a toolkit abstraction, and when you abstract things the differences between the underlying implementations are at the same time blurred but they also leak out. A wxWindows app doesn't feel integrated anywhere, and it struggles to hide the underlying differences between the real widget toolkits. Subtle details like focus semantics can break and cause wierd bugs in applications.
When you abstract something, you lose something. Unfortunately the quirks of history have meant we have lots of widget toolkits sitting on our desktop today. The real killer issues from this are integration, consistency and interoperability. Memory overhead is certainly not a big issue compared to these lot - I think you should perhaps do some profiling of applications and then you'd see that having 3/4 toolkits loaded at once is not the real problem, it's the performance quirks of those toolkits that are the issue.