Qt/Mac KDE Call for Help
aqsalter writes "Benjamin Reed of Fink fame is calling for help porting KDE to Mac using Qt/Mac. Interested parties should swarm the KDE-Darwin mailing list. KWrite for Mac here we come!"
← Back to Stories (view on slashdot.org)
If I understand correctly, the effort is not to port the GUI itself, but applications that use the kdelibs and arts libraries (i.e. koffice, konqueror, etc).
Porting KDE is another beast altogether, we are not talking about a few controls and widgets. We are talking about application design frameworks. This means:
- Handle inter-application data transfers: clipboard, drag-drop, services. Both framework use different internal formats (rich text, images, sounds, urls) so you have to convert things on the fly.
- Link KDE application on OS X services for printing, file-management, filename mapping, icons, etc...
- Link KDE application settings like internationalisation, appearances, user preferences to the OS X system.
- Handle application level events and scripting - i.e make it possible for KDE application to understand apple-events like quit, open, print, but also OSAX scripting.
All those things require a tremendous amount of work.No. There's no KDE library code in KHTML. There was some QT code, unfortunately, but Apple's programmers wrote a little shim library that presents an identical interface to QT's foundation classes (strings and whatnot) to get around that. This library is now part of KHTML. So the QT dependencies are slowly being removed. That's a good thing.
The library is actually called "KWQ", and it's a bridge between things like QString and the Cocoa stuff that does the same thing. WebKit handles the UI, I think.
At the beginning, I think the idea is just to get the apps running on QT/Mac effectively.
(KDE already links into OSX's printing, since that uses the open-source CUPS, although it still uses its own GUI.)
Why won't slashdot let me change my terrible username
Use Eudora. It's better.