I've been working on a number of web based applications recently, and have taken to using a few techniques that I thought I would share. I won't be sharing the code so much, which is ASP.Net centric, but will discuss what I am trying to accomplish.More...

Okay, I was playing around with the DOM Ready vs Window Load events with prototype.js and noticed that in my simple example, the window event actually fired before the dom event in IE8.  This could lead to some issues, especially on cached pages, so I wanted to make a note of it.

    1 var ready = { document: false, window: false };
    2 function DocumentReady() {
    3     alert("Document Ready");
    4 }
    5 function DocumentLoaded() {
    6     alert("Document Loaded");
    7 }
    8 document.observe("dom:loaded", function() {
    9     DocumentReady();
   10     ready.document = true;
   11     if (ready.window)
   12         DocumentLoaded();
   13 });
   14 Event.observe(window, "load", function() {
   15     ready.window = true;
   16     if (!ready.document) return;
   17     DocumentLoaded();
   18 });

The previous example shows how to handle this case. Why is it even an issue? Well, using the DOM ready event will allow you to hide things as soon as the tree has it. Using the window loaded event is necessary in order to handle flowing layouts in terms of size/proportion.

After reviewing the following recent blog postings (Top 30 popular websites Using CSS and Using Tables), I just want to state my own opinions regarding Tables vs. CSS based design. More...