Slashdot Mirror
KDE 3.2 Release Candidate 1 Debuts
danalien writes "Before a early Feb. release of the (stable) KDE 3.2, KDE has today announced the first 'Release Candidate', and hopefully the last pre-release, for its 'Open Source graphical desktop environment for Unix workstations'. Get it from download.kde.org, or use Konstruct if you don't feel like calling configure by yourself."
Remeber the mirrors http://www.kde.org/mirrors/ftp.php Rus
CPanel + Root from $35/mo - 10% off with discount code SLASHDOT
KDE 3.2 Feature Plan
main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
If you have ever worked or contributed in any way to a KDE project / KDE application, then you get some idea of just how dedicated the key people are. My own opinion of this phenomenon is that developers know (feel) that KDE is the best desktop suite we have, and we want it to be better. Also, with tools like QT Designer, and KDevelop, making applications for KDE is actually quite a pleasant experience (and this is from someone who loathes GUI programming). Well done chaps !
"I am not bound to please thee with my answers" [William Shakespeare]
I've been running KDE 3.2 built from CVS on 2004-01-14 for a week and so far, so good. This release should be nice. Now waiting for an ebuild...
It's a bit faster. I wish it would be much faster. But generally when this happens I reboot in XP for a day, then I realize that speed isn't all that counts. Prelinking helps, too.
I think I'll delete KDE 3.1.x entirely, since there is no need for it anymore.
-- Home is where you eat your heart out.
KDE does not run only on Linux, it also runs on the BSD's, Solaris, and (just recently and still in development) Mac OS X.
Liberal (adj.): Free from bigotry; open to progress; tolerant of others.
main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
i've been using KDE3.2 built from source since the early alphas. even then it was rock-solid stable with just a few rough edges. once i knew all of the workarounds, i migrated my production/work environment up to 3.2 as well, for the cool/useful features. highly recommended upgrade.
What about K3B, Quanta+, eric3, and scribus? There are tons more great KDE apps at the new KDE-Apps.org. The future of KDE application development looks bright. Remember that you're comparing KDE apps against the complete set of all other open-source applications. I think KDE is doing pretty well, myself.
main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
Um... No, it doesn't. GNOME uses GTK. GIMP uses GTK. That's how they're related.
/usr/lib/libgtk-1.2.so.0 (0x4002e000) /usr/lib/libgdk-1.2.so.0 (0x40139000) /usr/lib/libgmodule-1.2.so.0 (0x40169000) /usr/lib/libglib-1.2.so.0 (0x4016c000) /lib/libdl.so.2 (0x40191000) /usr/X11R6/lib/libXi.so.6 (0x40195000) /usr/X11R6/lib/libXext.so.6 (0x4019d000) /usr/X11R6/lib/libX11.so.6 (0x401ac000) /lib/i686/libm.so.6 (0x4028b000) /lib/i686/libc.so.6 (0x402ad000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
$ ldd `which gimp`
libgtk-1.2.so.0 =>
libgdk-1.2.so.0 =>
libgmodule-1.2.so.0 =>
libglib-1.2.so.0 =>
libdl.so.2 =>
libXi.so.6 =>
libXext.so.6 =>
libX11.so.6 =>
libm.so.6 =>
libc.so.6 =>
$
No GNOME libraries there. Compare it to the output of:
ldd `which gedit`
and you'll see what I'm talking about.
STOP . AMERICA . NOW
GTK+ - GIMP Toolkit. The widget toolkit used by GNOME.
Glib - GNOME utility library. Contains useful stuff like lists and hash maps.
Bonobo - Component toolkit to allow embedding of applications in other applications.
And before anyone flames, I've simplified, I know. But I have no idea of what the programming skills are of the parent poster.
Many of the weekly CVS digests include merged changes from Apple. While I have no idea how many have been merged, a great deal have, and I would venture to say that the Safari team has been very helpful.
KDE/Qt isn't any more monolithic than GNOME/GTK+. All the stuff that GNOME has as completely seperate libraries (libxml, etc) are seperate modules of Qt.
I think the "KDE is monolithic" viewpoint arises from the excellent integration between KDE applications and the desktop. Because they all operate as though they're a single, large piece of code, people assume they are. Ironically, it's the modularity of the code base that makes such seamless integration possible for a distributed development team.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
"The main idea remains that the idea of gnome was to to reuse as much stuff as possible (even when it shouldn't have), while KDE wrote much of these "from scratch" and has its stuff "more integrated" (just think about window managers)."
Actually...
According to Stallman and the GNU project, the idea of GNOME was to write a desktop to specifically replace KDE. The idea was that QT was not 100% free at the time, and the GNU project saw KDE's popularity as hurting the goals of the GNU project's operating system vision. So they started 2 projects: one to create a free replacement for QT, and another to create a replacement for the already free KDE. Since QT was GPL'd, the free replacement project was killed. But the GNOME project was already started and the developers decided to keep on working. In the process, GNOME made different choices on many aspects. Choosing to use CORBA to do their component technology was just one of the many different (than KDE's existing technology) choices the GNOME project chose. It just turns out that CORBA/bonabo (the Network Object Model part of GNOME) never got incorporated into many GNOME applications, and so now GNOME applications == GTK/glib applications.
When you think of the GNOME project, you should think of turning a primitive incomplete widget toolkit (the Gimp ToolKit) into what GTK+ is today, plus a set of applications which use this toolkit, plus guidelines on how these applications should behave. When you think of KDE today, you should think about the same things, but using already developed QT insted of GTK+ along with the ability to embed current applications into new ones efficienatly.
None of this has anything to do with KDE wanting to re-write everyting. In fact, they started with existing complete QT. and GNOME started with an incomplete GTK toolkit. The GNOME project is basically the GTK+ project combined with application rewriting with GTK+. So which project is the one that did the massive rewrites? I think that would be GNOME.
If you consider writing a program using GTK+ widget set and glib a GNOME application, you probably don't know the definition of Network Object Model Environment. (Hint, several KDE applications use such features, but most "GNOME" applications don't use bonobo.)
Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.