steve1376656734:
I thin the confusion here comes from what you consider to be the parent and child. If you take a diagram from the link you have referenced that shows multiple inheritance:
[attachment=1]Multiple Inheritance.png[/attachment]The equivalent diagram for a Servoy environment would be:
[attachment=0]Servoy Inheritance.png[/attachment]
The above diagram assumes that the fields and methods in the modules are declared as public and not protected or private.This, to me, seems perfectly logical and follows the OOP concept of inheritance as the solution “inherits” the public fields and methods from the modules in the same way that the sub-classes inherit them from the parent classes.
Hope this helps
Steve
This is exactly the problem here. See how you define the Modules as Parents that create a ‘sub class’? … Well it’s the opposite in Servoy. The Solution has to exist, it’s the root of the node tree. Modules are the sub class.
jcompagner:
The name “module” really means this is a solution that is meant to be included, it is not a standalone startable entity.
So it is backwards by how Servoy defines it.
Which again, backwards is great with an Observation pattern. And I assume I can improve my project structure by implementing more Solutions, which I haven’t attempted yet.