Changes from Girder 5
|Top Previous Next|
Girder 6 is a rebuild from ground up. As such it's not compatible with the Girder 5 structure. In fact it's a major overhaul of the Girder architecture. This has allowed Girder to run as a service, be ported to many different Operating Systems, including Android, Mac, Linux and BlackBerry (iOS soon). Not all ports are publicly available but can be obtained upon special request.
The GML tree looks very similar between Girder 5 and 6. In fact a lot of the actions are indeed the same. Some things have changed however. Any of the actions that deal with interacting with other Windows are now asynchronous. For example the Wait for Window action no longer blocks the Girder execution. You can safely use larger timeouts here. This however means that if your existing GML relies upon that wait to be synchronous things might not work as they did before.
Some actions are no longer available. If you encounter an action that is missing and you really need it, contact support.
The device manager code has been completely overhauled to be more like the PEAC device manager. Old code will not work.
The transport classes have been overhauled to be compatible with the PEAC classes. The code is similar in structure but you'll need to do a little work.
The webserver code has been redone to allow for websockets to be created. Compatibility functions exists in the namespace.
Sadly, none of the old plugins are supported by Girder 6.
The volume actions have been changed to deal with the new Audio Subsystem of Windows and be more flexible in general.
Girder has the NetRemote replacement built-in. This no longer loads CCF files however.