OpenLazlo Exploration

I went to the OpenLazlo site recently (http://www.openlaszlo.org/) and tried out the demos. They work very well. As I was looking through the overview to understand how it works, some questions came to mind.

OpenLazlo is a fairly interesting and unique design. Code is developed in Javascript and compiled into Flash. As I was reading, I started to wonder why they would choose this architecture. Who are they trying to appeal to? Flash is a stable and widely supported web design technology. You may find Javascript programmers wishing to wander into the world of Flash, but don't you stand to alienate staunch supporters of either technology? Is Flash performance/functionality so much superior/widely supported compared to Javascript to warrant the need to adopt the different technology? If you know Javascript, why not just use an existing and fully functional Javascript library such as Dojo or DHTML Goodies? Is there any consolation for Flash developers that don't know Javascript?

As I mentioned, the demo widgets worked very well, but there was nothing revolutionary in the functionality when considering the possibilities with other, pure Javascript libraries. Other offerings, such as Google Web Toolkit and Echo2, also choose the code conversion method of bringing rich user interfaces to the web. Developers using these frameworks are able to write purly in Java code and compile to Javascript and DHTML. This may enable Java programmers to venture into the web design arena, but is the transposition of a traditional application programming language on top of a web architecture a flexible enough concept? jMaki takes a different approach, embedding Javascript components in JSP/Servlet Tag libraries. Components can be placed on the page with JSP-type tags. This could be a good solution for the multitude of web designers with less programming skills.

What are your thoughts on these questions? Your personal experiences with these different technologies are welcome.

Just registered with Technorati

See my Technorati technical profile here:

Technorati Profile

Great Ajax Blog

This is a great Ajax (and other) blog...

http://www.ajaxian.com/

My Development Environment

This is my development evironment:

• Eclipse 3.2.2 - Eclipse is a really good IDE with a wealth of plugins. Netbeans has good JSP/Servlet/EJB wizards and integration with Glassfish, but Eclipse foundation has countered that with their own Web Tools Platform (WTP) (http://www.eclipse.org/webtools/main.php). The only problem is that it is a project to install and configure WTP with an existing Eclipse installation. Better to start with the complete bundled package.
• Glassfish v1 - I switched from Apache to Glassfish due to problems with Ajax on Apache 5.5. So far I am happy with it, but beware the autodeploy mechanism. Some old Javascript became stuck in one of the directories, and it was very difficult to figure out why I could not update it. Eventually, I found the directory with the old .js file and deleted it. Now I just use asadmin deploydir and undeploy.
• Apache 5.5 - I have used Apache since the beginning. There is a good Eclipse plugin that made servlet development so much easier. The reason I started something else was becuase of the Ajax problem. Maybe v6 will clear up the problem.
• JDK 6.0 - Just keeping up with the latest.

XMLHTTPResponse.status = 0

I am getting XMLHTTPResponse.status = 0 sometimes in my Ajax calls.

Anybody's insight as to why this is happening is much appreciated.

Ajax/Web Application Development

I am trying to research different Ajax/Comet technologies, but there is so much disparate information and crossover, that I am having trouble classifying them according to my needs. This blog is an attempt to create a classification of the different Ajax/Comet development tools available. I am just going to throw some things out there and see what evolves...

General technologies:

• Ajax - A method of asynchronous communication between a browser and server that enables parts of DHTML pages to be updated without a full page refresh.
• Comet - A method of communication between a browser and server that enables a communication channel to be kept open so a server can continually update the browser without client-side requests.

Javascript widget/component libraries:

• Dojo - Client side javascript communicates with [arbitrary server-side code?]. Consists of a Javascript library with several window controls and effects. Supports Ajax.
• DHTML Goodies - Client side javascript communicates with arbitrary server-side code. Cascade/Tile Windows!
• Prototype Windows - similar to Dojo and DHTML Goodies. Built on Prototype and script.aculo.us.
• Rico - similar to Dojo and DHTML Goodies, except no windows. Built on Prototype.
• Yahoo UI - Client side javascript librar with several window controls and effects. Very complete set of controls and offers some smooth animation effects. Supports Ajax.
• DWT - similar to Dojo and DHTML Goodies. Modeled after Eclipse SWT.
• Kabuki AjaxTK - client developer toolkit for Javascript widgets. Uses DWT. Created by Zimbra.

Frameworks:

• GWT - Google Web Toolkit. A Java library that allows a developer to create a rich browser application entirely in Java code. Translates the Java code into DHTML, XML, and Javascript. Supports Ajax.
• Echo2 - A complete IDE and code library that allows a developer to create a rich browser application. Similar to GWT in that you develop entirely in [language?], and this is translated to [javascript, dhtml, xml?]. Supports Ajax and Comet.
• OpenLazlo - Code in Javascript, compile to Flash.
• Zimbra - ??
• jMaki - a framework that allows you to wrap javascript widgets in jsp tags. Plugins available for Netbeans and Eclipse. Currently has support for some Dojo, Yahoo UI, and Prototype widgets, but you can create your own. Also provides full access to the html and javascript. (samples seem very slow)
• ZK - framework that utilizes ZUML to develop web based GUI's. No Javascript or Ajax knowledge required.
• Struts - A servlet-based Java framework that implements the MVC2 pattern. Consists of the architectural components to implement MVC2 and some additional taglibs that implement special html-based controls. Ajax can be implemented with struts, as Ajax can be used with servlets, but it is not really applicable to say that Struts supports Ajax.
• Pushlets - A servlet-based Java framework that implements event-based server-side push communication with a browser. A communication channel is kept open between the browser and server so that a server can update the browser continually without a request. Don't know if Ajax is responsible for the communication channel.
• Ruby on Rails - What are these and why are they so special?

... will update as your comments come in.

I am going to start breaking these up into frameworks, widget/component libraries, ...