suggestion: In the Documentation - Justify vs Blueprints
Just a suggestion.
I think it would be useful to see in the documentation what this offers that Blueprints don't at the moment, it looks like this is not different to Blueprints.. Maybe I am missing something but it might help to write up why you would use this instead.
Maybe the example is just to small. Does this example help you more?
Actually, plugins have nothing to do with blueprints. Of course you can register Blueprints in Plugins to extend your application. So what does this extension offer? It basically allows you to just drop a plugin into a specified plugins/ folder and after you have restarted the application (and probably "installed" & enabled the plugin) the plugin will extend the application.
Thanks for your response.. Your bigger example is better - and would make the documentation clearer. However I still cannot see it.
Would it be fair to say that it adds Dynamic loading/unloading of parts of the application?
Sorry this might