This is quite a milestone release for swingweb as many major features are finally in place. Quite a few performance issues and problems due to swing implementation have been resolved as well.

For the next release we will focus on validating the framework by implementing some real applications. Some additional components might be added along the way to facilitate application implementation.

Additional screenshots in the forum section

- update peers to be 1.5 compatible - pack separate toolkit jar for 1.5
- add support for threadless event queue - which is the default setting now
- implement share-app mode for scalability - add ViewComponent and SharedJLabel for share-app mode development
- add session management support through SessionLocal. Add url manipulation support through URLLocal
- add SwingWebRepaintManager to eliminate painting events?
- allow using of per-instance template at runtime
- add listener mechanism for render/input event
- add session lifecycle listener mechanism for session event
- implement selection event for JList, JTable, JTree component

- refactor SwingWebServlet to AbstractSwingWebServlet, SwingWebServlet, SwingWebShareAppServlet
- event queue is per session - add component manager interface for implementing shareapp mode
- make ComponentCssGenerator more extensible
- remove BridgeEvent layer

- fix dialog to hide after ok/cancel like normal swing
- fix layout problem in some complex layout scenario particularly involve lots of rowspan/colspan
- turn off double buffering in SwingWebRepaintManager

Here are some introduction to the framework:

Swingweb is a web-application framework that enables AWT/Swing application to be operating inside a web container and presented as a web application to the web browser, purely in HTML/CSS/javascript. The swing application will render and behave the same in the web-container as it is running as a desktop application. There are little knowledge required for the developer to start developing swingweb application as long as they are familiar with swing UI development.

The main goals of the Swingweb framework are to:
   1. Enable true component-based web-application development platform
   2. Use swing UI model for web application development
   3. Allow rapid development using existing GUI editors for web application development
   4. Save development cost by merging the development process of swing desktop application and web application

Some of the features of Swingweb include the following:
    * Support web-environment with multiple concurrent application sessions
    * Component-oriented architecture that allows developers to enable existing swing component to web environment easily
    * Flexible template-based approach allowing changing look/functionality of component/application
    * Transparent URL manipulation and session management inside swingweb application
    * Share-app mode to allow developing scalable high traffic web-application