upgrade Servoy 3.1.6 to 5.x

Classic Servoy
1

we have an old solution, in need of upgrading

can this be done, in one shot?

any suggestions / warnings appreciated

greg

2

Hi Greg,

Well one thing that comes to mind is to put all your controller.find() code (to get INTO find mode) in an IF statement because there are situations where you won’t get into find mode (unsaved invalid data for instance)and you will be editing code instead of putting in search criteria.

if ( controller.find() ) {
   field1 = '%mysearch%';
   controller.search();
}

Another thing is that you might want to add databaseManager.saveDate() in places where you want to make sure the data is saved to the backend.

These 2 are the ones that I can think of right of the bat.

Hope this helps.

3

only those two? :shock:
what about the new JSEvent object?

4

I’m upgrading two large solutions from 3.5.12 to 5.1.4, this is what I have found so far:

  • You have to deal with all the errors and warnings from Servoy, we had 1,300 and 950 on the two projects. A few of these can be fixed using Servoy’s ‘Quick Fix’ command.

  • You need new versions of all plugins, since they now need to be signed by the vendors (IT2be and others provide new versions) or you’ll have to sign them yourself.

  • You should name all function parameters instead of using parameters[0], parameters[1] etc

  • You can switch on strict mode for javascript to find more potential issues.

  • Since you are going from 3.1, you may find some things are easier to implement using table events, but you don’t have to change anything.

  • A number of plugins including the popupMenu plugin have been combined, and the old plugins deprecated. Your code will still work, but the new window plugin seem significantly faster.

The new Servoy Eclipse-based developer is MUCH MUCH better than the old developer. It is quite different, but once you get used to it there is no way back. The profiler is great for spotting slow code and to see what is really going on. It is a much more productive environment.

Hope this helps,

5

Harjo:
what about the new JSEvent object?

Eh, yes. That one too (like I said, right of the bat. Didn’t say this is all ;) )

6

Thanks to all. I see I have quite a bit of work to do

the If ( controller.find ) tip is very interesting …

I did find a JSEvent explanation here:
http://www.servoyguy.com/knowledge_base … o_servoy_5

greg

7

I just finished an upgrade from 3.5 to 5.1. There were 1759 errors and warnings. Very daunting, but in the end it was done in a few days.

There are some fixes that cannot be done using Properties. Laurian at Servoy taught me a trick to be able to see behind the interface and see the raw code.

If you are looking at the form: Click on Navigate in menubar, Show In, Navigator. It will highlight the form. Right click and open with text editor. Here you can usually figure out what the problem is.

8

another post about if ( controller.find() ) {

viewtopic.php?f=3&t=12951

odd that Find somehow worked in 3.1, but not in 4 and higher ( or I just didn’t notice )

greg

Well one thing that comes to mind is to put all your controller.find() code (to get INTO find mode) in an IF statement