jcompagner:
if you have many top level solutions that you want to have common shared logic
then that shared logic should just be in module that all the other top level solutions or other modules) to include that shared module that has all the global functions you want to have.as i said before solutions and modules are the same thing they are just a “package of functionality” that others can include… Pure for servoy the difference between a “pure” module and a soluiton is that a solution is “startable”
but you can make a fully structure of just solutions (so not modules)
The name “module” really means this is a solution that is meant to be included, it is not a standalone startable entity.But steve also descirbed it nicely
A Module could have a “MyBaseClass”
and then any other module (or the normal solution) that would include that Module could then extends that “MyBaseClass” , because it can see that MyBaseClass and can extend/enhance on top of it
But MyBaseClass has no idea that there are SubClasses build on top of that, it doesn’t see those
Okay so, I’m curious about this. The reason why I made my entire project be modules is because I thought Solutions and Modules are the same thing.
What is the advantage of having multiple Solutions? Like what can I do with multiple ‘startable’ points?