config stuff
Sandy Meier
smeier at kdevelop.org
Thu Sep 14 08:58:14 UTC 2000
On Tue, 12 Sep 2000 you wrote:
> On Tue, 12 Sep 2000, Falk Brettschneider wrote:
> Now I remember what was really ugly: KConfig is too primitive
> for a component-based application. If you give each components
> its own group, then all the component can store is key/value
> pairs - KConfig doesn't have nested groups. A workaround is
> to use multiple groups (the doc tree view is an example), but
> then the whole structure gets lost and the file becomes a
> glorious mess (btw the stuff stored by KDockMainWindow::writeConfig()
> is already an obvious example of such a mess)
>
> Can't we use XML+QDom for project files? :-)
> Then one could replace the setupGUI() to components with the pair
>
> void saveConfig(QDomElement element)
> void restoreConfig(QDomElement element)
I have taken a look at QDom and XML and will try to port the class ProjectSpace
and class Project to this "technology" next week.
Ciao!
Sandy
--
email: smeier at kdevelop.org ICQ: 27681958
the KDevelop project: http://www.kdevelop.org
--
"Solange es Schlachthäuser gibt, wird es auch Schlachtfelder geben." (Leo Tolstoi)
More information about the KDevelop-devel
mailing list