On Wednesday, 2013-08-07, Pier Luigi wrote: > 2013/8/7 Kevin Krammer <[email protected]>:
> > Not to forget that there is a third option: contribute an implementation > > to Qt upstream and then use oficial Qt API. > > I recently shared my work on the Qt development mailing list: > > http://lists.qt-project.org/pipermail/development/2013-July/012028.html Nice work! > Currently there's a class that reads a JSON schema, sort of what > GSettings does, and offer a simple value()/setValue() API much like > current QSettings. > This is currently done at runtime but I realize now that it's pretty > complicated to get it right, I see benefits moving the burden to > compile time much like KConfig does. > A cli program would read the schema and generate a nice C++ class, > maybe even QML code if asked to, with proper typing and default > values. Might be as simple as adding Q_PROPERTY macros for each setting to the generated classes if the config keys are not hierachical. Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
