[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [PATCH] Multi-Protocol IO-Slave
From:       Michael Pyne <mpyne () purinchu ! net>
Date:       2008-01-15 1:08:14
Message-ID: 200801142008.19622.mpyne () purinchu ! net
[Download RAW message or body]


On Sunday 13 January 2008, nf2 wrote:
> Also, having a Qt based client library is less liberal in terms of
> licenses. 

Well the Qt based client library (including everything that goes with using 
Qt) is a choice we made.  It seems that just as soon as GNOME got 
commercialized it became a rallying cry that people can write proprietary 
apps using GTK+.  Which seems sad given the support provided to GNOME by 
Stallman and the FSF.

> Of course, rewriting the core of KIO in plain C (or better
> GLib + main-loop + C) should have happened many years ago.

Why should the core of KIO be rewritten in plain C again?  You have convincing 
arguments about the structure and advantages of the GNOME VFS and then go on 
talking about how devolving KIO to a C library would somehow be an 
improvement?

What I'm interested in is what Kevin Krammer was mentioning?  Is it possible 
to provide a line-interface compatible KIO-like interface to the GIO mount 
daemons (like how DBUS has nice language bindings)?  i.e. using the same KIO 
classes but with GIO job class implementations.

Regards,
 - Michael Pyne

["signature.asc" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]