Version 4.1 is the recommended release for DHTML and SWF development. This is a major release with over 800 bug fixes in the source code and many underlying architectural changes, in part paving the way for SWF9 support. OpenLaszlo 4.1 has been fully-qualified across the following browser/platform combinations: Safari3/OSX, Firefox2/OSX, Internet Explorer 7/WinXP, Firefox 2/WinXP, and Firefox 2/Linux. We have tested the full suite of demos, samplers, and example applications with the requirement that, when possible, DHTML applications behave the same as their SWF counterparts. Keep in mind that DHTML does not support audio and video. To include that in your application, you can embed a SWF application within your DHTML application, as in this example.
OpenLaszlo 4.1 also debuts the new and significantly improved documentation. There have been over 300 bug fixes made to the Reference Guide, and over 225 bug fixes in the Developer's Guide. The Reference Guide and Developer's Guide are also being built using the new doctool chain, which is described in the Developer's Guide, for contributors interested in adding to the documentation.
Preliminary support for SWF9 is included in this release. As such, we removed the swf9 button from the dev console for this release. You can compile applications for SWF9 by appending lzr=swf9 to the compilation URL. Or, if you are building the LPS from source, you can uncomment the swf9 radiobutton in lps/admin/dev-console.lzx, and then rebuild the dev-console by running the new console-rebuilding ant task there: cd lps/admin ant
Remember to clear your browser cache before reloading to see the rebuilt dev-console, as it is loaded as a SOLO application. We will add the SWF9 button to the developer console when support for this runtime is more complete.
For every release, we rely on the OpenLaszlo community to help ensure the quality of the platform release and to determine its future direction. To propose or participate in discussion of new features, see the Wiki.We encourage you to report any problems, and to make suggestions for enhancements, through our JIRA bug tracking system. We'd also like to hear from you on the mailing lists and in the forums.