Laszlo's Roadmap

Laszlo development is divided into two branches:

Endotoxin 2.2It is the main branch, with priority to stability and bug fixing. This is the direction of commercial recommendation, and this version does not support 3.0 features.

Endotoxin 3.0Is a branch of the development version. The main feature of LPS 3.0 is that it does not depend on the server deployment mode, supports Unicode, integrates browsers, and adjusts the application size and speed. Applications created by LPS 3.0 will require support from flash 6 or later versions, which will provide some other features.

 

LPS 2.2.1

Fixed a bug in 2.2. Fixed execution efficiency defects when using soap and XML-RPC. The source code and Installer of this version will be released in the early November S.

LPS 3.0 Beta 1

The source code of LPS 3.0 will be released by openlaszlo.org In The Middle Of November. This beta version includes the following features:

Unicode

The released version supports Unicode text, including program source code, user interface elements, request data, and returned data.

 

Client Fonts

LPS 2.2 only supports embedded fonts, which limits the execution performance and increases the size of the application. This version will remove this restriction.

 

Canvas resizing

You can adjust the size of the browser window when the application is running again ..

 

Internal Compression

LPS 2.2 uses gzip encoding, which reduces the amount of transmission, but the size of applications in the browser cache is still large. The internal compression mechanism can detect and determine whether Gzip is needed for processing in the file, so that the browser does not need to decompress the file.

 

LPS 3.0 Beta 2

The second beta version of LPS 3.0 is planned to be released in early 2005. The following features will be added:

Back button)

Integrate the "back" button of the browser

 

Serverless deployment)

You can deploy compiled applications on a Web server without the Laszlo Presentation Server.

 

Drawing API (drawing API)

You can use the program API to create a graph.

 

Dynamic Loading class library (dynamically-loaded libraries)

This mechanism delays the download of some code that is not needed to initialize the application.