I guess better approach (or say not better but proper from the dojo
perspective) is to use dojo event framework to associate needed events
via dojo. There are some advantages of this approach:
1. Multiple listeners can be associated with the same event in the
cross-bowser compatible manner
2. It looks cleaner.
More on Dojo events you will find http://dojotoolkit.org/node/134 or
in any other place where dojo event system is described.
About the timer you can use dojo class dojo.animation.Timer although
I'm not sure how stable and working it is.
Renat
On 26/06/07, craigham <[EMAIL PROTECTED]> wrote:
Hi,
I recently upgraded to 4.1.1, and have run into an issue with backwards
compatibility and cannot seem to find the documentation on how to resolve.
I have a screen which was auto-refreshing with the following in the @Shell
onload="window.setTimeout('document.form.submit();',1000);"
It is my understanding this api changed with the dojo addition. How would I
do this in the most recent tapestry?
Also, I a quite sure there is a better solution to this. Prior to loading
this screen I call an asynchronous method, and then redirect to this
screen. This screen just refreshes every second and in the pageBeginRender
method I check the status of the job, and if done do a redirect. This is
very similar to a shopping cart processing the call to the credit card
companies. Does anyone have a suggestion as to what would be a better
approach to solving this?
thanks,
craig
--
View this message in context:
http://www.nabble.com/upgrade-to-4.1.1-tf3983447.html#a11309241
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best regards,
Renat Zubairov
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
