You could also include custom events in your classes, to be fired on completion. For example, the onComplete function for Class A would instantiate Class B.
On Oct 7, 12:56 pm, "Iván N Paz" <[EMAIL PROTECTED]> wrote: > Why not move everything into DomReady???? > > IMHO thats the best choice... that way you concentrate everything in a > single point of entry and you avoid further race conditions... > > Using delays may solve this issue in some machines, but not in others, > since you dont have control on network bandwidth and/or processor > speed on the end machine... > > On 10/7/08, TheWickedFlea <[EMAIL PROTECTED]> wrote: > > > > > > > Hi Dan, > > > As far as the docs are concerned, DomReady only waits until the DOM > > itself is prepared and then fires the event. If you want to wait for > > the script elements in the page to finish executing there's always the > > fn.delay(10) option. Or alternatively, you could have a periodic > > timer variable that checks to see if a 'ready' property is the same > > count as the objects within the Controllers.controllers array. Only, > > don't forget to clear your timer when you've fired the event. > > > These are the only ideas I have, I hope they help. > > > Regards, > > Flea > > -- > ◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦◦www.ivanicus.com
