Common main loop: Qt ported to glib main loop (experimental)

Alexander Neundorf neundorf at kde.org
Fri Dec 3 18:03:57 EET 2004


On Friday 03 December 2004 16:49, nf wrote:
...
> Of course it has Qt-dependencies. Qt is almost like a C++ dialect (with
> the signals and slots stuff) - so it's used in all KDE libraries. As i
> said before: That wouldn't be a problem if the core (non-Gui) parts of
> Qt were LGPLed.

For this specific point it doesn't really matter whether it's GPL or LGPL. I 
mean, we are talking about the ioslaves, apps don't link to them, they talk 
via a pipe. Nothing hinders anybody (license-wise) from writing a non-free 
application, let's say with gtk, which is able to talk to GPL'd ioslaves.

...
> 3) We choose GNOME-VFS and steal ideas from KIO.

Dumping the existing solution of one project in order to go for the solution 
of the other project won't work. No matter in which direction.

> 4) We take a hammer and hammer GNOME-VFS into kdelibs to completely
> replace KIO. 

There is a practical problem. Who do you think will be able to take a hammer 
and hammer something into the kde core libraries ?

> With a common main loop that should work. (But make sure

Ioslaves run in their own processes, the mainloop doesn't matter to the 
application.

> that the KIO-API stays the same. KDE applications and the rest of the
> desktop should not have to change).

Yes.

Bye
Alex
-- 
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org                - http://www.kde.org
      alex at neundorf.net               - http://www.neundorf.net



More information about the xdg mailing list