Thanks for the replies. Actually its not causing problems, I've solved
it by putting it around a window.onload{} and for now its ok,
following the YAGNI principle, it is working :)
I'm using Tap 4.0.2
and I need an onload, because it sets a timer for me, for eg:
function receiveMessages(){
//ajax stuff
setTimeout("receiveMessages()",2000);
}
window.onload= receiveMessages();
But once again, thank you guys for the help :P
Regards
On 8/21/06, andyhot <[EMAIL PROTECTED]> wrote:
Jesse Kuhnert wrote:
> Saying <node>.on<event>=<foo> ~will~ blow away other peoples changes.
Of course, that's why i said it's ugly...
But for non dojo, non Tap4.1 cases,
one can easily google for the 4 lines js function that appends stuff to
window.onload
instead of overwriting them...
But anyway, what i would like to know is what Tapestry version
Vinicius uses and why is the <initialization> tag causing him problems?
Why must he use window.onload?
--
Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr
Tapestry / Tacos developer
Open Source / J2EE Consulting
---------------------------------------------------------------------
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]
