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

List:       kwrite-devel
Subject:    Re: Uninitialized config values
From:       Dominik Haumann <dhaumann () kde ! org>
Date:       2013-11-17 19:18:01
Message-ID: 1464404.hJfddzzIt3 () eriador
[Download RAW message or body]

On Sunday 17 November 2013 17:23:05 Alex Turbov wrote:
> On Sun, Nov 17, 2013 at 5:01 PM, Dominik Haumann <dhaumann@kde.org> wrote:
> > > Hey,
> > > 
> > > I proposed that a while ago already. I think the problem was Kate's
> > > distinction between global properties and "non-global" properties (e.g.
> > 
> > ones
> > 
> > > that might get overwritten by modelines and such) -- afair.
> > > 
> > > KConfigXT doesn't really provide infrastructure (speak: API) for having
> > 
> > this
> > 
> > > kind of cascading config settings.
> > 
> > Correct, I also think this is a problem.
> 
> I think it does not! we can still use .kcfg file to define what options
> should be read from katerc (or sessionrc).
> konfig_compiler will create a base class to further extend it w/ ability to
> override some setting w/ vars & etc...
> but that generated class will take care about proper initialization,
> reading and writing configurable parameters...
> 
> > It would probably not be too hard to write a script that generates these
> > config classes, though.
> 
> reinventing the `kconfig_compiler` w/ few differences doesn't looks like a
> good idea to me :)
> (but extending it sounds better :))
>  working w/ .kgcf files recently I have few ideas to improve it ...

If you can provide a minimal working example to demonstrate this, that would 
be fine. Not with kate code, just some small snippets.

Greetings,
Dominik
_______________________________________________
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]