Another Fun Day at J2EE Training

Posted on Posted in Corporate News, Technology Center

We had fun at J2EE training today, JM talked about YUI, prototype, Script.aculo.us and Dojo. These javascript toolkits surely know their way around the javascript quirks that’s been perstering lots of developers with browser incompatibilities. I agree that these toolkits help a lot in making more stable javascript codes.

Some pictures taken from the training:

Some of our observations are:

  1. Lots of these toolkits do the same functionality (e.g. String utilities, Ajax calls, Animations). Is there any standard body that is defining the new sets of javascript features? So we all live in one common world of javascript coding? Or is it a battle of the best platform?
  2. Seems like we’re going back to the world of client-server days. As rich-interface becomes popular, will thin-clients begin to disappear? And what’s with Flex, Silverlight, JavaFX?
  3. When prototype popularized Object-Oriented approach, they made a good point about the power of Javascript… but still, the flexibility of javascript codes make it difficult to standardize. It’s more of a developer’s conscious effort to create cleaner code.

One neat thing I learned about prototype is that it has a method “Try.these{…}” where all the statements within will be evaluated until one actually works. Sounds useful when making your javascript methods work across multiple browser.

4 thoughts on “Another Fun Day at J2EE Training

  1. JS toolkits are great. They help us avoid the headache of rewriting the same code over and over again. Most of its similar functionalities/features are DOM selection and manipulation, event handling, AJAX, animation, UI widgets, but with different twists. It’s necessary to choose and include only what is efficient and can handle the needs/requirements of the project to avoid going down to a path of architecture that bloats. When evaluating/comparing these toolkits you have to consider performance, usability, compatibility, simplicity, comprehensive documentation, active developer community, and the time and effort needed to grasp it properly. Popularity sometimes counts because unpopular frameworks may slowly become stale and eventually lead to lack of developer support.

  2. I’m really enjoying the theme/design of your blog. Do you ever run into any internet browser compatibility issues? A handful of my blog readers have complained about my blog not working correctly in Explorer but looks great in Safari. Do you have any advice to help fix this issue?

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.