clean way for disabling dhtml functionality until page is fully loaded ?

[sonic_soul]

Hello,
I am finishing up creating a fairly complex page that is very rich in
DHTML. In addition to updating it self every couple of seconds,
various components on it support sync and async communication with
various web services.

The problem is that if a user tries to click on any JS driven content
before the page is fully loaded, it will not work properly since it
relies on many onLoad scripts that initiate webservices etc.

is there a clean way, to simply disable any page functionality before
it loads ?

other than explicitly enabling every control in window.onload() event.

TIA
-s

[Jim Ley]

On 5 Nov 2004 09:28:35 -0800, sq**********@ho tmail.com (sonic_soul)
wrote:

other than explicitly enabling every control in window.onload() event.

Yes, this is much more sensible approach, don't give them anything to
click on until you're ready to handle it.

It's not difficult.

Do not use SYNC in webpages though, with JS sharing the UI thread, the
lockups you get are nasty.

Jim.

[Grant Wagner]

sonic_soul wrote:

Hello,
I am finishing up creating a fairly complex page that is very rich in
DHTML. In addition to updating it self every couple of seconds,
various components on it support sync and async communication with
various web services.

The problem is that if a user tries to click on any JS driven content
before the page is fully loaded, it will not work properly since it
relies on many onLoad scripts that initiate webservices etc.

is there a clean way, to simply disable any page functionality before
it loads ?

other than explicitly enabling every control in window.onload() event.

Set a global enabling boolean in window.onload() and have your functions
test it:

<script type="text/javascript">
window.onload = function() { window.isLoaded = true; }

function foo(bar) {
if (window.isLoade d) {
// do your stuff
} else {
alert('The page has no finished loading yet!');
}
}
</script>

--
Grant Wagner <gw*****@agrico reunited.com>
comp.lang.javas cript FAQ - http://jibbering.com/faq

[Jim Ley]

On Fri, 05 Nov 2004 18:00:00 GMT, Grant Wagner
<gw*****@agrico reunited.com> wrote:

sonic_soul wrote:

other than explicitly enabling every control in window.onload() event.

Set a global enabling boolean in window.onload() and have your functions
test it:

The problem with this though, is that the user can still attempt all
the actions and just get confused by nothing happening..

Jim.

[jbjonesjr]

Perhaps load the page as the last thing possible. Load the code and ui
into a frame, and the page into another frame. But the last load event
will be to change the navigation frame from a "wait while loading"
document to the document you want.

[Fred Oz]

Jim Ley wrote:

On Fri, 05 Nov 2004 18:00:00 GMT, Grant Wagner
<gw*****@agrico reunited.com> wrote:

sonic_soul wrote:

other than explicitly enabling every control in window.onload() event.

Set a global enabling boolean in window.onload() and have your functions
test it:

The problem with this though, is that the user can still attempt all
the actions and just get confused by nothing happening..

1. put a big banner at the top saying "Please wait for page to load"

2. if any user event is fired whilst window.loaded = false; put up an
alert to say wait

3. In the onload(), hide the banner (display: none) and set
window.loaded = true;

Cheers, Fred.