05-06-2016, 05:14 PM
In creating a plugin too large to be practical in one source file, would you recommend breaking some segments of the code into separate classes and use calls such as hdi::core:lugin::instance() to reference the main plugin to create callbacks, tools, menus etc. in methods called by the main plugin at startup, postStartup, shutdown, etc.? Or would it be better to just put it in separate source files and include them as was "toolFormatting" in the Tool sample?
A lot of sizable chunks of my code are reused in different plugins and as I rewrite them in CORE it would again be helpful to take a modular approach.
A lot of sizable chunks of my code are reused in different plugins and as I rewrite them in CORE it would again be helpful to take a modular approach.