question about the new configuration framework

[Adam Treat]

On Thursday 17 August 2006 3:36 am, Jens Herden wrote:
> On Thursday 17 August 2006 00:16, Matt Rogers wrote:
> > On Wed, Aug 16, 2006 at 11:22:34PM +0700, Jens Herden wrote:
> > > Hi,
> > >
> > > if I understood right the new configuration stuff in KDevelop is based
> > > on kconfigXT now. So whenever I have a plugin that needs configuration
> > > I should create a *.kcfg and *.kcfgc file, right?
> >
> > No, the configuration stuff is based on the KSettings framework which is
> > currently residing in the kutils folder of kdelibs.
> >
> > > So from what I know inside the *.kcfg file the name of the rc-file is
> > > written and the generated class gets this in the constructor. Does this
> > > mean that a plugin always saves its configuration in kdeveloprc if
> > > there is no project open?
> > >
> > > From reading the code I understand that the configuration dialog looks
> > > for *.desktop files where the entry X-KDE-ParentApp is set to the
> > > instance name of the application. How can this work if the application
> > > is not kdevelop but something else?
> >
> > This is still something that has yet to be worked out. It might involve
> > extending the KSettings framework a bit to allow the functionality we're
> > looking for.
>
> Would it be possible to just add another file. Now you are using kdeveloprc
> and insert the global and local project files on demand. So if we would
> insert in this layer system the configuration file of the current running
> instance on top of kdeveloprc would this work?

Nah, because then you'd have stuff like the codeview part settings in the 
documentview config file...

Or do you mean by 'instance' quantarc?  we can certainly do that, yes.

> Jens
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel