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

List:       kde-core-devel
Subject:    Re: Redefining kdelibs and kdebase
From:       "Andras Mantia" <amantia () kdewebdev ! org>
Date:       2005-08-27 10:38:16
Message-ID: 1128.150.214.57.42.1125139096.squirrel () mail ! kdewebdev ! org
[Download RAW message or body]

> On Saturday 27 August 2005 11:35, Andras Mantia wrote:

>> Will be hard to not depend on KFileDialog (and KDEPrint), no?
>
> The idea is to run the file dialog, print dialog, etc. out of process.
> 'Our'
> implementation of the file dialog can reside in KDE workspace and all that
> is
> in KDE framework is an interface to launch the dialog. On Unix under KDE
> it
> could just do a dbus call to kded and fire up the out-of-process file
> dialog.
> When running the KDE app under GNOME it could use the same dbus interface
> to
> fire up the GNOME dialog. Under Windows it'd do it like Qt: Use the
> windows
> dialog.

Sounds good, but will this be powerful enough? What if there is
functionality in the current KFileDialog that will be not supported by the
GNOME, Windows, MacOS or whatever file dialog? Will we - the application
developers - loose functionality?

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