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

List:       kde-core-devel
Subject:    Re: Redefining kdelibs and kdebase
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2005-08-27 19:31:52
Message-ID: 200508272131.07509.nicolasg () snafu ! de
[Download RAW message or body]

On Saturday 27 August 2005 12:30, Simon Hausmann wrote:
> On Saturday 27 August 2005 11:35, Andras Mantia wrote:
> > > applications that are included with this package.  Your average
> > > application shouldn't have dependancies to KDE desktop unless they
> > > are a component such as a screen-saver or panel applet.  Once
> > > libraries such as KIO are portable then they should be moved into
> > > frameworks.
> >
> > [...]
> >
> > > -KDEPrint
> > > -KFileDialog
> >
> > 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.

And how is this supposed to work with KDE's KIO slaves, especially for complex 
ones like media: or for the ones that do not exist in GNOME like fish: ?

Have a nice day!

>
> Simon

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