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

List:       kwrite-devel
Subject:    Re: KDE/kdelibs
From:       Joseph Wenninger <jowenn () kde ! org>
Date:       2007-09-17 11:31:44
Message-ID: 200709171331.44725.jowenn () kde ! org
[Download RAW message or body]

Hi !

I didn't have time to look at the plugin selector code,  so this are some 
uneducated questions:

*) If the config dialog and the plugin are separated from each other, how does 
a loaded instance get notified of a settings change ?  Watching the 
configuration file ?

*) Don't we still need the save settings method in unload, reason: If a plugin 
has some kind of history functionality, which is modified during working, not 
within the configuration dialog ?

*) Is it still possible to pass settings via the destkop file to plugin? Eg 
for meta plugins, eg something like a python plugin, which would have to be 
loaded more than once (Once for each underlying script file, which would be 
the "real" plugin) (We had that feature in the 3.x kate (not the python 
thing, but the metaplugin support) (at least in the app)

Kind regards
Joseph Wenninger

On Monday 17 September 2007 00:25:21 Dominik Haumann wrote:
> On Monday 17 September 2007, Dominik Haumann wrote:
> > SVN commit 713276 by dhaumann:
> >
> > katepart
> > * remove kpluginselector fork
>
> didn't do anything anyway yet.
>
>
> With regard to the other thrad: The attached patch removes the functions
> which need te be removed to make this work. I'll commit today if there are
> no objections.
>
> Dominik



-- 
KATE developer - Joseph Wenninger <jowenn@kde.org>
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]