jcompagner:
Or maybe i didn’t understand it right what you want…
What I want is a way to build modules with the reasonable expectation that they can be easily plugged into any Servoy solution.
Servoy has not taken the lead in setting out guidelines and best practices in this area and Servoy’s module implementation has well known deficiencies. This has lead to various approaches to solving the problem – we have our approach, Servoy development services has another approach, and various independent developers dive in with whatever ad hoc module setup that makes sense to them at the time. The end result being that nobody’s module system works very well with anyone else’s.
Contrast Wordpress marketplace to Servoy’s Marketplace. One is typically used many times over for an average project and the other is lucky to be discovered by the typical developer. Servoy’s lead as exemplified via their marketplace is a dead end.
In contrast, the Servoy plugin setup is completely democratic and interchangeable. No surprise…there is healthy plugin ecosystem. (I would argue that Patrick coming along and writing a simple plugin creation guide was something Servoy should have done years earlier…)
I believe the ease of interchangeability is a primary indicator of success with any platform. Servoy doesn’t have this figured out within the scope of modules – or at least they are not communicating the guidelines clearly. If technical changes are needed (and I have argued certain changes would make things a lot easier), I believe they are worth implementing at the cost of backwards compatibility.
Give us the pluggable framework for module portability and 3rd party developers will create. The current system is very frustrating for us.