Deconstructing Ajax!

The Web 2.0 movement is a new approach to building Web applications that are more responsive and user-centric. You can think of it as a second generation or second wave of Web applications. One of the main differences is that users don’t have to click and wait while using a Web application. Instead, updates and changes can happen in the background while the user does something else.

One of the most common approaches to building Web 2.0 applications is something called Ajax. The term Ajax doesn’t describe a technology. Instead, it refers to a collection of existing technologies and the way that they work together to build Web 2.0 applications.

Ajax-style applications use the following technologies:

• XHTML and CSS to describe the interface
• DOM to locate and manipulate different parts of the interface and the data source
• XML and XSLT to describe and transform data for the application
• XMLHttpRequest object to request and load external data
• JavaScript to bind the other technologies together

In this article, I’ll explain a bit more about the role that each technology plays. Let’s start by looking at how the Ajax technologies react together.

Choosing Between Ajax and Flash

Web 2.0 describes a new approach to creating and structuring Web applications. One of the aims is to increase responsiveness so that Web applications operate in a similar manner to their desktop cousins. Two of the approaches to creating Web 2.0 applications include Ajax and Flash/Flex.

In this article, I want to compare and contrast these two approaches. I will discuss the advantages and disadvantages of each approach and show you what to consider when choosing between the two. I’ll finish by introducing a process that might help you to make your decision!

This article isn’t trying to explore which is the BETTER of the two approaches. Both have their merits and uses. Instead, I’m trying to help you decide whether Ajax or Flash/Flex will suit you better, given the circumstances of your Web application.

Don’t forget that an alternative to using either Ajax or Flash/Flex is to stick with a Web 1.0 approach using XHTML and CSS. If you don’t need to create a complex interface, you’re not loading large amounts of external data and you don’t have a requirement to include multimedia, a simple XHTML interface may suffice. Creating a Web 1.0 application that adheres to Web standards can make it easier to distribute the application to a range of browsers and operating systems. It can also improve accessibility for people with disabilities.

I want to start by looking at Ajax and examining its advantages and disadvantages.

Free, an interview with Jesse James Garrett, the man behind AJAX

DMXzone.com held a special interview with Jesse James Garrett the man behind AJAX. Jesse James thought of the term AJAX  to describe a technological approach that seemed promising without having an idea how popular it would ultimately become.

In the interview we we learn more about Jesse, his company and his thought on usability, AJAX and related technologies. Jesse explains how he thinks developers should use AJAX and he gives his view on how to prevent usability mistakes.

Read on for an extract of the interview, you can read the complete interview in the October 2006 e-Magazine.

Five star rating system Part 1

Introduction

Everyone likes to feel that his opinion counts and often finds enjoyment expressing it to others. In that sense Internet has certainly come as a handy invention. Various forums, chat rooms, guestbooks, blogs and finally, for those with unapplied acting talents, podcasts – all for a chance to say (or type) something we feel absolutely MUST be said (or typed J).

Apparently, to encourage us exercise our freedoms more often many web sites, including DMXzone, are giving us opportunity to rate their content, products or services. With this great feature we can both send our feedback and learn from the experience of our peers on a particular item.