Huge upgrade to Servoy 6; Question about modules

Classic Servoy
1

Since 2005, I have been developing a suite of applications using Servoy. I upgraded to Servoy 4 in 2008 without much difficulty. Until now, I have been unable to put development on hold in order to upgrade to Servoy 6. Now that I am upgrading, I am faced with several challenges and need some advice.

Over the years, I have separated functionality that is shared between my three main solutions into separate modules. Now it seems that there are so many references to global variables, global relations and non-global relations across the modules themselves that it seems like I should make one module that contains all global variables and relations. Is it a good practice to have a module solely dedicated to storing global variables and relations? Should calculations or anything else be included also?

Steve in L.A.

2

Hi Steven,

I have converted two systems (105 tables and 90 tables) which started out in version 2, first to 5.2 and then 6.0.
For me the big change in Servoy 6 was that it does not allow circular references between modules. In an ideal world there should not be any, but my code had many such references.
I kept moving stuff around, but could not get it to work properly.

In the end I merged all my modules together except for my navigation, reporting and headless client modules.

You will get a scary number of error messages 1,000s from Servoy when converting, but it is worth working your way through them, I could get rid of 100+ an hour.

Good luck, the end result will be worth the effort.

C.

3

A brain dump on how we implement/organize modules: Module best practices