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

List:       kde-core-devel
Subject:    Re: KDE is not an OS platform... (And neither is Gnome)
From:       nf2 <nf2.email () gmail ! com>
Date:       2009-11-04 1:30:50
Message-ID: aaed7a190911031730q7ff5760bp3f8070403e9c6d27 () mail ! gmail ! com
[Download RAW message or body]

On Wed, Nov 4, 2009 at 2:18 AM, David Faure <faure@kde.org> wrote:
> On Wednesday 04 November 2009, nf2 wrote:
>> * But Qt-only apps?
>>
>> And i do believe Qt is quite important for getting more apps written
>> for the FOSS desktop. As its portability is very attractive.
>
> OK, that's a good point. However QFile/QDir is not the answer IMHO.
> Qt has a nice API for async networking requests already: QNetworkAccessManager
> (for which we have a KIO backend; the qt-kde platform plugin (cf the thread
> from Olivier) could even use that when kdelibs is around).
> But for file dialogs, it misses directory listing, and stat, at least.
> And for file management, it misses mkdir, del, copying and moving files.
> But I'm really afraid that saying this will result in a NIH "QIO" framework in
> Qt. Noooo ;-) It should really end up using KIO, of course. Funny how
> apparently, runtime usage of KDE isn't such of a big deal compared to using
> KDE API in the first place...
>

Yeah - or GIO. ;-)

Here you can see some autogenerated Qt/C++ bindings...

http://live.gnome.org/GObjectIntrospection/GObjectConsume

The async part isn't complete unfortunately, as the callback
forwarding to Qt slots isn't finished...

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