The LAS can do the automatic compilation by itself, just like Tomcat compiling our JSP files.Or we can compile the lzx file separately and then place the resultant swf file within the LAS folder and use it. The better method is to use the swf thus generated ALONG with the Laszlo Application Server( LAS). This is quite simple but if we use this method, we forego advanced features like SOAP communication etc.It may be remembered that Flex2 also has similar facility. This type of using the lzx file is known as ‘SOLO’ mode. When we compile the laszlo xml file, we get swf file and this file is displayed in the browser. As all modern browsers are already bundled with flashplayer, this swf file is displayed in browser without any special arrangement. The server then sends the swf file to the browser. There is provision for scripting also.This is compiled into a flashplayer format as swf(shockwave) file. Just like Flex 2.0, OpenLaszlo also begins with a source in special type of XML file( demo.lzx) for creating the GUI. Thus,both in Flex 2.0 and OpenLaszlo, browser variation problems are disposed off effectively.(However, it seems that extensions are being created to access the user’s hard disk,by scripting, so as to mimic a regular desktop application! This is a grave danger.) How OpenLaszlo works? ![]() But unlike Flex 2.0 which is free but not open-source, ( the Flex-IDE comes at a cost but Eclipse plug-in can be used instead.that makes Flex 2.0 also ALMOST free) OpenLaszlo is both open-source and free. ![]() OpenLaszlo also depends on the presence of Flash player in browser side. Flex 2.0 and OpenLaszloīut, Flex 2.0 and OpenLaszlo, base themselves on the ubiquitous Flash player which comes bundled with all modern and popular browsers. AJAX in JAVA wrappers.(JSF coders can make use of ICEFaces, which provides one such wrapper to be used with JSF). They just see the components as kind of a black box that they can drag and drop onto their applications and they don’t have to worry about the can of worms that’s inside”. So, one of the things we try to do is make it so that people who are using JavaScript components don’t actually have to worry about JavaScript at all. Because when you start to get out of line, the way JavaScript did, it just causes an interoperability nightmare for developers. And it’s kind of been… it’s the example that keeps convincing us that we have to be really,really careful about interoperability in the Java platform. Ajax is a technology that at its heart has been around for quite a few years and mostly took off when they came up with a clever name, but it really suffers from the fact that here are so many flavors of JavaScript. ![]() ![]() You can actually do, using Java applets, pretty much everything you can do in Ajax and you get much better portability. Google Web Toolkit is an AJAX toolkit, worth serious attention from Java coders, because it wraps AJAX in familiar Java code, is free and comes from a path-breaking company.It also frees the coder from the vagaries of browser-dependent variations in implementing javascript.It is instructive to note James Gosling’s views on plain AJAX, as given below. AJAX, Flex2 and OpenLaszlo are the three important RIA technologies. RIA tries to create browser-based applications,which are as rich and as responsive as stand-alone desktop applications. RIA stands for Rich Internet Applications. In this lab-oriented beginner’s tutorial, the author explores OpenLaszlo technology and explains its basic features.
0 Comments
Leave a Reply. |