GNOME/KDE Integration Gets A Few Boosts
Balinares writes "Great bunch of news on the Linux desktop unification front. After the unification of GTK and Qt themes that Slashdot already reported on, it is OpenOffice's turn to get the unified look treatment (screenshot 1, screenshot 2, screenshot 3).
In related news, the recently released QtGTK library allows to merge the Qt event loop with that of GTK. In other words, this means you can now easily use KDE's DCOP, IOslaves, and, last but not least, file dialogs, from inside your GTK apps. (Screenshot of this feature used in XMMS2: 1 2). It comes with a tutorial that explains the basics.
Finally, the new fuse_kio tool now makes it possible to use KDE's IOslaves directly at the filesystem level, from any Linux app. 2004 is really beginning well for all those of us who use Linux as their primary desktop!"
When I first installed Linux I flipped a coin to decide between the two :) Yes, I didn't want to make a choice, as Redhat gave no background to base my decision.
Plus the kioslaves are glorious.
.tar.gz which was open in Konqueror straight into an FTP site, also open in Konqueror. A bit later, I was copying Ogg Vorbis files off an audio CD.
The other day, I was copying stuff out of a
There's loads of other kioslaves, like smb:, fish:, lan:, kamera:, floppy: and sftp: - they can make tasks which previously required entirely separate applications utterly seamless instead.
I'd love the opportunity to be able to use them on the command line, and to use them with other, non-KDE software, which it sounds like fuse_kio thing will offer...
There's no reason to worry about the KDE print dialog. Any app can be programed to output postscript and then pipe it to kprinter. KDE has the printing thing licked, and has for a long time. I can use KDE's print dialog with mozilla, openoffice, and just about any other program that lets me chose what program to use for the print que.
Why is it so hot? Where am I going? What am I doing in this handbasket?
Does anyone know if a closed-software maker is violating the GPL if it has originally linked to an LGPL library (legal), which has an independently created GPL analogue?
If not, then isn't it a matter of a LD_PRELOAD to transfer all or many GTK calls into QT calls, where the preloaded library is fully GPL, and gtk+ software was originally linked to the LGPL original gtk?