Looking at the docs, it appears the lower-level API might be well-suited for our needs, at least here. It would be nice to leave all of the property page layout in the hands of the plugin devs. We'd provide a base settings page class from which their custom pages must be derived, along with some helper functions for signaling and other stuff. We would only need to instance whatever settings page they've built, attach it to the tab widget and connect the signals and slots... Of course, this means everyone's creating a unique class for each settings page, but at this point, it seems much less of an issue to me than it did before. Frankly, I see it as a great solution for what we're dealing with here - why not use it?Zini wrote:I don't think this link is applicable here. The idea about plugins was to use a python as a scripting system, which would totally bypass all of Qt.
Also, regarding sections being equivalent to pages, I think that will be the best assuming that the plugin sections do not require sections of their own (sub-sections, I suppose). Even with a moderately complex settings file, I don't see that we'd ever need to do anything different.