In today's world everyone knows the power of the Internet and every web surfer
has been impressed at one time or another by the vast wealth of the Web.

HTML, DHTML and Macromedia's FlashT are generally used to create web pages that are published on the Internet. But none of them allow developers to create astounding user experiences because all of them are based on fundamentally limited models.

In contrast, Laszlo, the language that OpenLaszlo utilizes, is a declarative approach to creating widgets or entire applications with XML and JavaScript. This melding of a markup language and a scripting language is similar to the current HTML/JavaScript combination. Rather than interpret the language on the client side with a browser, Laszlo is transformed on the server side into Macromedia's Flash format. This provides for virtually automatic cross-browser support, since Flash provides a standard runtime. As the Flash format is vector based, it also allows for very flexible and fluid user interface components, which can be reused in a broad sense.

However, this is not the sum total of OpenLaszlo. OpenLaszlo is backed by an optional server-side container, the OpenLaszlo Server, which provides extended integration and support for remote procedure calls, Web services, and transcoding services (which help to do things like stream lengthy MP3 files to the user). Laszlo as a language also employs exciting concepts and design methodologies that allow you to create truly reusable components in minutes. The components you make will also be extremely visually appealing and familiar to users.

OpenLaszlo @ Jeevan
At Jeevan Technologies, we have harnessed the Laszlo UI Design thoughts for Architecture in the SOLO mode. The objective was to make design methodologies that allow us to create truly reusable components in very little time. This is to reduce the downloading time and also seamlessly integrate data with forms

Based on the above high level architecture design, the User Interface is a Laszlo-based .swf (flash) file which communicates with the .NET web service which in turn communicates to the DAO (Data Access Objects) layer and fetches the required information from the database and transfers the data to web service. The response is in the form of .aspx/.xml file that can be interpreted by the UI.

Client Behavior Overview
With direction from the customer, the Laszlo client application is designed to give the user a sequence of tabs, which encourages them to follow an order in specifying the information in the application. Each tab contains "topics" that are presented as sliders; each slider in turn contains fields. A topic is defined as a logical collection of information, similar to a group of boxes on a form--for example, address information.

The Laszlo client is designed to be flexible, deriving much of the content of the screens from a server-side API that can drive the content of the tabs, the fields on the screen, the acceptable values for these fields and their validation rules. This allows easy and quick generation of a client anticipated to have over 5,000 potential screens; the on-demand nature in which the screens are read keeps the client's size small, allowing for faster downloading and good performance on "diminished clients".