What Are Its Benefits

The Framework can provide you with a single and consistent application model for both Windows and Web. The advent of WAMs makes the single application model capabilities even stronger than before.

Standard interface

A design loosely based on Microsoft Outlook. Outlook is very popular around the world and almost all users are familiar with it, whether at work or at home. 

This model provides a cockpit or dashboard style design where everything that an end-user might need to do is just a few clicks away.

XML-based external design schema

The Framework is instantly executable.

Because of the modular design, many developers can work on different parts of the application at the same time.

The versions of the prototype can be quickly emailed for evaluation and feedback.

Rapid prototyping

Applications, business objects and commands can be defined in a few minutes and can be used in emulation mode before any code to support them actually exists.

A vision of how the completed result will look, act and feel can be formed and executed before a single line of code is written.

This process also acts as a way of rapidly uncovering new or hidden business requirements.

Prototype becomes the application

You do not have to discard any part of your prototype. When you are ready to turn the prototype into a real application, you simply snap your custom-made parts in the Framework. This means you keep the basic structure of the application, its business objects, commands, menus and images.

Rapid modernization

You can use the Framework RAMP tools to quickly enable your System i applications for Windows.

Absolutely no change to the 5250 application is required and yet RAMP offers  advanced navigation, search and organization capabilities that go well beyond other modernization tools.

Simple to code

The Framework gives the developer much easier access to advanced Visual LANSA and LANSA for the Web features. For example, it implicitly handles multi-form and multi-component interactions and referencing.

Load-on-demand architecture

A load-on-demand architecture that dynamically loads application components as they are used. This prevents having to load your entire application during start up. 

Standards for development and user interfaces

The modular structure of the snap-in filters and command handlers encourages standardized development practices.

The user interface is to a large extent controlled by the Framework which enforces consistency.

Productivity improvements in addition to Visual LANSA

The Framework handles all the basic functions of the application, such as multi-form interactions and referencing.

A huge "jump start" for new Visual LANSA or LANSA for the Web developers

The environment helps the developers in getting started with the application development and guides them towards a standard implementation.

Gradual and benefits driven introduction to some of the heavier OO concepts

The Framework is based on OO concepts such as inheritance. This underlying structure and its benefits become gradually more obvious to the Framework developers as they progress in implementing the application.