05-09-2016, 11:46 PM
The hdi::core:lugin class is there to allow for basic plugin-level functionality, and of course its instance is necessary during startup to register your various callbacks. Otherwise, additional plugin-level functionality is up to you to provide wherever you find best for your workflow and/or the needs of your plugin. If you choose to do that via subclassing the hdi::core:lugin class, wrapping the hdi::core:lugin class, or altogether leaving hdi::core:lugin alone is up to you.
In the samples, their *:lugin classes are not there instead of hdi::core:lugin. It's more like in addition to.
In the samples, their *:lugin classes are not there instead of hdi::core:lugin. It's more like in addition to.