Jon A. Cruz wrote:
A proper splitting would not really get rid of toolbox.cpp, but instead create a new toolbox.cpp *per* tool.
That's kind of the whole point, to have this code neatly separated :)
However, we still will need toolbox.cpp to load up the defined ones from the XML definition and assemble the actual UI presentation. But, yes, splitting each tool to a functional code unit and a UI code unit could simplify creation and addition of them.
The way I intend to do this, toolbox.cpp is in fact not necessary. The design idea I mentioned in an earlier post about actions ("static plugin") can be also applied to tools, so that there are no centralized files which list all tools that must be initialized. It would also potentially allow extensions to define new tools.
Regards, Krzysztof Kosiński