KConfigXT Flaws

[Benjamin Meyer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 26 January 2004 3:02 pm, Waldo Bastian wrote:
> On Mon January 26 2004 19:30, Reinhold Kainhofer wrote:
> > Waldo Bastian wrote:
> > >> - kconfig_compiler assumes "Mutators=false" as the default; this does
> > >> not seem to make much sense, I'd say the point of a configuration
> > >> facility is to make it possible to *change* values. IMHO mutators
> > >> should be enabled by default.
> > >
> > > In 99% of the cases you don't need the mutators because mutation
> > > happens via KConfigDialog which uses setProperty() calls. No need to
> > > generate code that isn't used.
> >
> > Oh, really? AFAIK KConfigDialog can't be used with KCMs, and almost all
> > kdepim applications use kcms for their config dialogs. Am I missing
> > something here?
>
> You can use KConfigDialogManager in combination with KCMs, but something
> easier to use for KCMs is still missing, yes.
>
> Cheers,
> Waldo

???  What do you mean missing?  KAutoConfig had a KCM class before being 
stripped out.  You mean there wasn't/isn't a replacment for it?

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAFyLy1rZ3LTw38vIRArpsAJ0e9Hy3rR060lgpj3vM6uokXrP0pgCgk1Ss
Frxcr1vnfHf8WWf+o0rDiNQ=
=UJQj
-----END PGP SIGNATURE-----