Version 4.2.6 for Mainframes
 —  Natural for Ajax  —

Some Background Information

This document covers the following topics:


Name Binding between Controls and Adapter

Which are the critical parts when building the "Hello World!" application?

There is a name binding between the layout definition and its corresponding adapter. This is the simple and effective approach of the Application Designer's development process: The adapter represents a logical abstraction of what the page displays. All layout definitions are kept in the page - all the logic is kept in the adapter. (Or better: behind the adapter. The adapter itself should only be a facade to the "real" application logic.)

Top of page

Data Exchange at Runtime

What happens at runtime?

With a standard HTTP connection, only the changed content of the screen is passed when operating on one page. The layout is kept stable in the browser. Consequently, there is no flickering of the page due to page reloading.

All steps described in the list above are done completely transparent to your adapter; i.e. you do not have to cope with session management, stream parsing, error management, building up HTML on the server, etc. You just have to provide an intelligent HTML page by defining it in the Layout Painter and an adapter object.

Top of page

Files and their Locations

Have a look at the files created for your "Hello World!" application and take notice of the directory in which they are located.

All files are located in the directory <installdir>/cisnatural/cisnatfirst. The <installdir>/cisnatural directory is the directory of the web application instance. The <installdir>/cisnatural/cisnatfirst directory is the directory that has been created for your new project.

Top of page