Thanks - that works for me. I was unclear how any <script> tags would be handled, but you've answered that for me.
Richard On Jan 26, 5:16 pm, Christophe Porteneuve <[EMAIL PROTECTED]> wrote: > Hey there, > > It doesn't really require a specific tutorial. Just look at simple use > cases for Ajax.Updater, you'll have everything you need. > > Of course the XHTML fragment you get back from your first, > DIV1-triggered calls to Ajax.Updater can contain <script> elements. > Those will even get stripped out of the inserted DOM fragment, and > executed right after DOM insertion. These could very well bind the new > links to further calls to Ajax.Updater, this time targetting 'DIV3'. > > If your function code for the DIV2 links is the same all the time (only > parameters vary), you may want to put it in a separate script file, > include it statically in your global page, and just provide event > binding code with your returned XHTML fragments. That'll help factor > stuff out and reduce the complexity of these results. > > -- > Christophe Porteneuve aka TDD > [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
