The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: KConfigXT
by Andras Mantia on Thursday 06/May/2004, @13:29
|
No, or not yet. The reasons are:
- KDE 3.1.x compatibility (but we drop this after this release, so we can use it. KConfigXT is present in KDE 3.2, no?)
- I haven't took the time to look at KConfigXT (and the tutorials).
I'm sure it would help us and simplify the code, but well, somebody has to do it (and that somebody needs time to do it).
Andras
|
[
Reply To This | View ]
|
Re: KConfigXT
by Sebastian on Friday 07/May/2004, @01:45
|
KConfigXT is present in KDE 3.2, I already ported a small app to KConfigXT running KDE 3.2.2.
Porting is easy, first writing a XML file and after converting the function calls. Maybe you could do this with some substitution commands.
|
[
Reply To This | View ]
|
|
Re: KConfigXT
by janne on Friday 07/May/2004, @00:10
|
What exactly is KConfigXT? Is it something like Gconf on steroids?
|
[
Reply To This | View ]
|
Re: KConfigXT
by Benjamin Meyer on Friday 07/May/2004, @12:33
|
GConf is to KConfig as ? is to KConfigXT :)
KConfigXT does a number of things. Mostly it boils down to 2 things:
1) Settings and default values are stored in 1 xml file, not all over in code, in ui files, in config files, etc etc
2) Configure dilalogs don't really need to be coded anymore. Toss together some ui files, give it a pointer to your kconfigxt and wham it does the rest. Takes care of loading, disabling, saving, etc. This amounts to major major savings both in time wasted coding, debuging and in user interface as every config dialog that uses kconfigxt behaves the same.
Check out the tutorials or some apps in cvs (KTron in kdegames is a excellent small simple application that uses it)
-Benjamin Meyer
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|