- User Since
- Oct 9 2019, 2:45 PM (24 w, 3 d)
Thu, Mar 26
Thu, Mar 19
I was thinking you might want to use pointer to RuleSettings members instead of config item name strings inside of RuleItem. Also maybe it would be worthwhile to make RuleItem a template (I think it doesn't need to be a QObject) instead of your Type enum.
Hi @iasensio , I can help with porting your code to KConfig XT . Do you mind if I rebase your branch and make some modifications ?
Mon, Mar 16
Remove double delete smell
Fri, Mar 13
Mon, Mar 9
fix stack overflow, export
KConfig XT is based on KConfig, and there is an underlying KConfig Object with entries/groups. But the entire point of KConfig XT is not to use them, and use the auto generated accessors instead. The kconfig compiler can also make RuleBookSettings a QObject with Q_PROPERTIES and signals that you can connect to your model.
Fri, Mar 6
remove unecessary group deletion
Move rulesettings* to source root
Tue, Mar 3
Hi @iasensio, great work on the UI redesign! I currently have a patch https://phabricator.kde.org/D27682 to port the existing kwinrules KCM to KConfig XT. Hopefully this can help bridge existing configuration with your model, as well as import/export.
Add second kcfg, clean class hierachy
Fri, Feb 28
Feb 27 2020
Don't write item if rule is set to unused
Fix non-KCM build
Feb 26 2020
Can confirm this works
Feb 25 2020
Feb 24 2020
const, change method name, reformat code
Feb 19 2020
Add reference files for other tests that were impacted
Reduce number of lines in generated test code
Yet more style fixes