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

List:       kde-core-devel
Subject:    Re: Porting kio-slaves to GnomeVFS modules
From:       Jason Keirstead <jason () keirstead ! org>
Date:       2004-12-28 22:51:35
Message-ID: 200412281851.35238.jason () keirstead ! org
[Download RAW message or body]

On December 28, 2004 11:59 am, nf2 wrote:
> I have started writing a plain C++ layer for writing portable VFS
> modules (to be be used in different VFS environmens like KIO, GnomeVfs,...)
>
> At the moment it's just the beginning of an interface proposal. But i am
> sure with your help it could become something useful... :-)

It looks way too C-ish to me.... open(), seek(), and close() calls with char* 
buffers? Why would we use such dated stuff when we have QT. Give me my 
KIO::Job into a nice safe QByteArrays back, thanks :) The only way I could 
see this type of thing being used in KDE is if the existing KIO layer were 
totally re-written to use this underneath. But that would be a lot of work 
for not much benefit.

Also - I don't know how you plan on making VfsUri UTF safe without using an 
external lib - and then you have the thing again where linking against said 
lib would just be duplicating functionality already present in QT.

This is the biggest problem with these cross-library proposals - you never 
want to depend on QT, so always end up using other libraries that basically 
duplicate portions of QT's functionality (hello glib:).  But in KDE we 
already use and love  QT, so why would we want to link againt other third 
party libraries that offer pieces of functionality already in QT, that are 
even often (arguably) inferior?

-- 
Jason Keirstead
http://www.keirstead.org
[prev in list] [next in list] [prev in thread] [next in thread]