This is why in this tutorial I’ll try to give you an idea on how the actual design works. I’ll be heavily relying on my last tutorial for the layout of the final application, but we’ll go much more into detail about the decisions we take. Some parts may be applicable to non-Web-2.0 Web design and some even come in handy when designing completely non-web related applications.
Most AJAX applications in use right now load everything on startup, images, javascript and content. While this is surely an easy way to do things it’s not the best, because it takes a long time (sometimes too long) for the application to be ready, and much of the stuff that is loaded is never used, or used pretty late during execution. For exactly this reason we’ll divide the application into modules.
Modules are independent parts of the application, like in our case these would be:
Page: a simple module which will be implemented in this part of the tutorial. It will load an HTML file from the server and display it in the content area.
Gallery: a gallery made of user pictures, the goal would also be to use Flickr as a backend for the pictures (e.g. take a group pool and display it, display pictures of a user, display pictures with a certain tag, …)
News: simply an extension to the Page module this will allow administrators and moderators to post news. News are passed to the Javascript engine using XML. Its main purpose is to demonstrate how to use XML-Files.
Messages: A module for sending and receiving private messages.
Forum: the most complex module we’ll see during this tutorial.
First of all we’ll see how to load modules and register them into a module handler (the Engine) and then we’ll move on to actually design the modules.
For now take a look at the working copy of the application here, or download a snapshot of the code here.
 Read More...
|
Rate this Ajax Tutorials
Error connecting to mysql |
|
Special offer for AjaxImpact.com Visitors!!
Subscribe to Oracle Magazine for Free!
