Genero introduces a new way to render screen forms by representing them logically as an XML tree. This method enables the logical abstraction of the business logic from the physical implementation of the client technology. As a result, applications may execute across multiple client technologies and fully exploit the local widget set, whether it be Windows, Linux, HTML or Java. User ‘A’ may be connected to Windows; User ‘C’ to a browser; while User ‘D’ is using a Linux or Motif workstation.

More Effort Required

In order to overcome the limitations imposed by the I4GL architecture, Genero has let go of some of the ‘baggage’ needed to deliver high compliance. Genero is largely based on BDS and is, as a result, largely compatible with I4GL; the essential differences arise from a brand new user interface subsystem, rewritten around a synchronized XML tree architecture.
Almost all of the language key words are the same and in many cases a simple recompilation of your I4GL source code with Genero will still work. But the result will lack panache. To unleash Genero’s power, form definition files and some parts of the code will need to be modified. Consequently, maintaining a single source code tree between I4GL and Genero is no longer possible.

As you review the design and ergonomics of your applications, you will quickly realize that the number of forms and the code length will reduce in size dramatically. You will also probably discover that anywhere between 50% and 75% of your business logic is actually managing presentation and that this code can be elegantly eliminated by manipulation of the XML presentation layer. But since XML didn’t exist when I4GL was created, I4GL provides no specific keywords to do this. That’s why these keywords have been added to Genero’s Business Development Language.

The result will be tighter more reliable code that executes faster than ever before. Take the time to investigate Genero – it will be a valuable investment of time.