I wrote a blog post some time ago about how to make a feature optional. It comes from a non-developer/layman perspective to encourage people to look into the code. Perhaps it’s a bit helpful. https://design.blog.documentfoundation.org/2018/04/14/easyhacking-how-to-make-a-feature-optional/
> Am 01.02.2019 um 09:31 schrieb Winfried Donkers <winfried.donk...@dekimo.com>: > > Hi Michael, > >>>> utl::ConfigItem is sort of deprecated and you should have a really good >>>> excuse to use it in new code. >>> >>> I have no better excuse than that it existed in the same component. >>> Which method should I use instead (or where can I find good examples of >>> code to use as guide)? >> >> just "git grep officecfg::" will find lots of examples, there are >> headers generated that have a class for every config item and you can >> get() and set() it. > > I found sufficient examples to use; so far chart2 (where I'm currently > working) does use officecfg:: yet. > Thanks! > > Winfried > _______________________________________________ > LibreOffice mailing list > LibreOffice@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/libreoffice _______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
