by Matthieu GIROUX
Many software publishers use old versions of their tool. In fact they do not know how to migrate to a new version of the tool. Also, in times of economic contraction, companies are struggling to see on the long term.
It is practically impossible to migrate a software made with non-Rapid Application Development language to new Frameworks. With a non RAD tool, choosing the Framework is therefore essential. This framework must be sufficiently simple and ingenious to save time.
W4 EXPRESS is an engine that transforms analysis to software with a software engine. Customization can be programmed with plugins called "behaviors". It also allows you to add operating systems with minimal programming. So integrators whose used W4 EXPRESS benefited from ANDROID and iOS in 2013, without having to program. W4 EXPRESS also creates a lightweight software from data. XML Frames is a free project showing the portability of passive W4 EXPRESS files.
There is also ATK Framework or JELIX JFORMS in PHP. These frameworks can inherit from tools’ Framework. The Framework ATK also creates a lightweight software from data. It should be possible to use passive W4 EXPRESS files to create a JELIX or ATK interfaces. These Frameworks are made from your sharing. They help to create management software faster.
Nevertheless, the problem of non RAD languages is that they tend to make programming more dificult. A trouble while programming creates misunderstanding among programmers, leading to poorly developed sources or poorly presented sources.
With a RAD tool it will be possible to migrate more easily than non-RAD languages, if its RAD tool has many components with sources. Indeed Sources can create reliable software to find its failures, but also separating sources can easily migrate to a new version of the tool.
Also inheriting of components is necessary. In fact, creating components can begin the migration to create indeed a software, but also to transfer gradually to the new version of tool. Expertise created will also find new customers by creating a method and keywords that had been developed. With a RAD tool, it will create also different versions of its softwares easier, centralizing, in the simpliest way, structuring with an intuitive deployment for developers.
If components do not exist on the new version of the tool and the sources are not free, it is also necessary to inherit other components . Missing properties will be created with the inherit. We create software to replace some key words. This will be the migration tool.
Know-how will also consider using automation Model Driven Engineering. Unlike Model Driven Architecture, we do not create sources which may not recreate the model. Led by Model Driven Engineering, we will create an engine reading analysis to create the software, with automated Components inherited.
We also inherit the Components to allow more possibilities to software . Extended LAZARUS and DELPHI 2006 Framework automates the creation of reports. So it is now possible to allow to the user adjusting the columns’ widths of printing. Extended will migrate software made with DELPHI to LAZARUS .
LAZARUS permits to switch to LINUX. LINUX Systems give you the speed of the LINUX kernel, as demonstrated by the STEAM platform. You also have the speed of recent partitions used for recent drives. There is also the safety and shared UNIX softwares. It will be interesting to remain compatible with DELPHI. DELPHI software is faster and lighter than LAZARUS software on WINDOWS.
LAZARUS will migrate regularly, so more easily. Indeed there will be no need to buy a set of licenses for the developers. By against free languages often require sharing during migration, especially when moving from DELPHI to LAZARUS.