OSDL to Bridge GNOME and KDE 321
Trax88 writes "Open Source Development Labs is previewing work that will attempt to make life easier for software companies by bridging GNOME and KDE. The effort, called Portland Project, began showing its first software tools on in conjunction with this week's LinuxWorld Conference & Expo. Using them, a software company can write a single software package that works using either of the prevailing graphical interfaces. Working with Freedesktop.org on unifying interface issues, they plan to release a beta version of the software in May and version 1.0 in June. Ultimately, advocates hope that it will be part of a larger but separate effort called Linux Standard Base, which is designed to make the operating system easier for software companies to use."
But... (Score:5, Informative)
"I personally just encourage people to switch to KDE.
This "users are idiots, and are confused by functionality" mentality of
Gnome is a disease. If you think your users are idiots, only idiots will
use it. I don't use Gnome, because in striving to be simple, it has long
since reached the point where it simply doesn't do what I need it to do.
Please, just tell people to use KDE."
Let's not get off track. (Score:2, Informative)
Gnome Logo on Slashdot (Score:5, Informative)
Please consider this email a formal request from the GNOME Foundation.
We, being the GNOME Foundation, as well as many GNOME Foundation members and
contributors to the project, have contacted you numerous times over the last
four years regarding the use of the old GNOME logo on Slashdot. We've posted
comments on Slashdot stories covering GNOME. We've been very nice about it.
Please update the icon used for GNOME stories on Slashdot. We have used this
logo since 2002, when GNOME 2.0 was released. It has been a *very long* time
since the marble foot logo represented our project. We're now at GNOME 2.14,
so we've shipped seven releases since the new logo was adopted. In that time
you have posted over 120 articles in the GNOME category on Slashdot.
We'd really appreciate it if you updated the icon. It may not be a big deal
to you guys, but our logo is a mark of pride for our project. We'd like to
see it used.
Thanks,
- Jeff
From: http://mail.gnome.org/archives/foundation-list/20
http://blogs.gnome.org/view/jamesh/2006/03/20/0 [gnome.org]
http://www.gnome.org/~jdub/random/logo/ [gnome.org]
Re:Will they be able to deal with KDE sound apps? (Score:5, Informative)
The UI and speed is horrendous and gnome is improving with every release. Kde4 is going to have a much cleaner and better interface with huge architectural changes. I look forward to it so I can try kde again.
Gnome user Converted to KDE Here (Score:5, Informative)
Gnome was doing me well until I wanted to change something and couldn't. (Window manager metacity blows) So i switched to KDE's window manager, kwin.
Then one day I realized I liked Amarok and digiKam so I installed Kubuntu Desktop via apt-get while using Ubuntu. Figured I'd give KDE a try.
Within an hour I had KDE configured to look exactly like my gnome desktop, to every last button and taskbar. Then I realized, I didn't have to make it like gnome at all!
So in summary. KDE Is better than GNOME because KDE can look like GNOME but GNOME cannot look like KDE. Same as all squares are rectangles but not all rectangles are squares. Gnome is a square.
Also, i had a preconcieved notion that KDE was a Windows desktop clone, which it might be at first glance, but you can quickly and easily make it your own.
Gnome is just inferior in comparison, but I still run it on my laptop.
Re:Merge ? (Score:3, Informative)
Well, I'd say fairly different design philosophies. Using two completely different toolkits, written in two different lanuages. Actually, I think it's more the latter than the former. If you could incorporate both Gnome and KDE as a set of "preferences" of the same desktop manager, there'd at least be a lot less reason to argue about it. But in reality it's just as much a Gtk/Qt competition underneath. Since the C/C++ standard library is tiny compared to many languages, both sides know a whole lot about their own toolkit and little about the other. Not to mention C and C++ aren't actually the same, despite C++ once branched off from C. It's like trying to get a Java and C# programmer to talk together (ok, not quite as bad). That and that Gtk is LGPL, while Qt is GPL + commercial license. Naturally some people will fall into each camp.
Besides, it wouldn't be that bad if projects like this means Gnome and KDE projects would actually mix in a good way. Why should it really matter to the end-user what it was programmed in? For all he cares it could be written in ruby on rails. Then he can pick on its merits and not just which "side" an application is on. Now, I could get started on packaging formats but then I'd just work up some frustration. Download sites have one build for every Windows version, and one build for every version of every Linux distro. Which may not even look well unless you're on the "right" side.
Re:Let's not get off track. (Score:5, Informative)
This is not a new desktop. This is a layer of separation between developers and the underlying graphics libraries Qt (KDE) and GTK (Gnome).
No it isn't. It is a set of tools that will allow applications (including installers) to do things like add menu items, add icons to the desktop, enable/disable the screensaver, etc. in a desktop-independent way.
What it does (Score:4, Informative)
The Portland project page isn't particularly informative either -- the description is too low-level: "we're going to create two interfaces." OK, two interfaces to do what?
The Integration Tasks [freedesktop.org] page actually provides information about what kinds of things they want to do: make sure apps built for both desktops will talk to the screen saver in the same way, deal with power management, share preferences like default apps, etc.
Sounds like a logical continuation of FreeDesktop.org's efforts so far, and something that will improve matters for people like me who like some apps from one desktop and some from the other.
Re:Merge ? (Score:0, Informative)
On Linux, Firefox uses GTK widgets and the GTK file browser to choose files (during Save as... etc).
Re:Merge ? (Score:5, Informative)
If I didn't like Firefox so much more than Konqueror, I'd switch myself. I hate the dialogs. The KDE versions are _much_ better, and I say this as a Fluxbox user who has spent a lot of time in both gnome and KDE.
--Tyler
no, it won't (Score:2, Informative)
Re:Let's not get off track. (Score:3, Informative)
One thing that looks as if it will happen is that Gtk+, Qt, and any widget set wishing to be a part of the family will have a common event loop:
http://lists.osdl.org/pipermail/desktop_architect
One of the cool things that results from this is that it'll be possible to embed Gtk+ applications into Qt and vise versa. That will eventually allow you to write a KPart (in KDE) or GPart (in GNOME) that can be embedded transparently in the other:
http://www.scheinwelt.at/~norbertf/common_main_lo
There also appears to be some work in unifying the GNOMEVFS and KIOSLAVES:
http://www.scheinwelt.at/~norbertf/common-vfs/ [scheinwelt.at]
Re:GTK File completion broken in all versions trie (Score:3, Informative)
Re:But... (Score:5, Informative)
The KDEPrint framework is the same: every app that can print can print to PDF, by default. The dialogue is always the same; everything is very consistent across apps. In KDE, if you've seen one print dialogue, you've literally seen them all. Gnome feels unintegrated by comparison.