You can use Function.defer() from Prototype to make your JavaScript call after Tapestry.init() (actually when the intepretor is idle).
The problem is functions within Tapestry.init are not ordered, I don't know if this should be considered a bug. On Fri, Nov 21, 2008 at 1:41 PM, Fernando Padilla <[EMAIL PROTECTED]> wrote: > Yeah. I saw that too. I was wondering if the zone init stuff should happen > before any user defined javascript as well. > > Nick Davies wrote: >> >> Hi, >> >> Apologies if I'm being dull here, but I'm trying to trigger an AJAX call >> automatically once a page has finished loading - the idea is that the >> main page is cached and a small amount is re-rendered each time. >> Obviously, this needs to happen after the call to the Tapestry.init() >> javascript function, which sets up the zone. I can't find a way of >> getting anything to run after this - tapestry puts the init call in a >> DOM loaded event listener, and anything you register with RenderSupport >> runs immediately before this. >> >> We're using Tapestry 5.0.15 >> >> Thanks, >> >> Nick >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
