On Monday 17 January 2005 23:09, Aaron J. Seigo wrote: > On Monday 17 January 2005 03:38, Esben Mose Hansen wrote: > > Me, I was looking for support for user defined structs. I tried path the > > paramterized variants, and found path insufficient for this purpose. > > However, it is possible to inject a class between KConfigSkeleton and the > > KConfig compiler, so I'm writing the support there. > > > > I could shine this up to 4.0 and make it a general support for custom > > objects, if it has any interest. > > yes, KConfigXT needs a number of improvements for 4.0, user defined data > sets being one of them. i wonder, however, if making the developer write > more code (toVariant, toMyStruct, etc) is the only/best way? would "nested" > KConfigXT objects be enough? We probably also want to introduce "nested groups" to the .ini format so that we can map such structures a little bit better to the actual file. Take a look at khotkeysrc to get an idea about the problems with the current approach. It won't make a fundamental difference, it would basically change [Data_2_7Triggers0] to something like [Data][2][7][Triggers][0] Cheers, Waldo -- bastian@kde.org | Free Novell Linux Desktop 9 Evaluation Download bastian@suse.com | http://www.novell.com/products/desktop/eval.html >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<