Hi all,
We are working on an application in which we'd like to have components refreshed independently in the same window. So we wanted to embed these components in iframes, and have some javascript to refresh them periodically.
We thus started to do stuff in this way, using seaside's #urlForAction: method to get the src parameter of the iframe tag, but we have a problem, which is that seasides does not generate only the component, but a whole application page when the browser fetches the url. Hence we have an infinite loop of iframes ...
So do you think it would involve significant work to allow this behavior ?
Thanks in advance, Cyril & Romain
On Jun 28, 2004, at 7:13 AM, Romain Robbes wrote:
Hi all,
We are working on an application in which we'd like to have components refreshed independently in the same window. So we wanted to embed these components in iframes, and have some javascript to refresh them periodically.
We thus started to do stuff in this way, using seaside's #urlForAction: method to get the src parameter of the iframe tag, but we have a problem, which is that seasides does not generate only the component, but a whole application page when the browser fetches the url. Hence we have an infinite loop of iframes ...
So do you think it would involve significant work to allow this behavior ?
If you are using Seaside 2.5, what you want is to start a new instance of the RenderLoop for each iframe. Each RenderLoop has its own root component. So, if I were setting up iframes, I might do something like
src := html urlForAction: [WARenderLoop new root: MyComponent new; run].
Avi
seaside@lists.squeakfoundation.org