Hey Esther, Esther Fuldauer a écrit : > Do you see the big picture now? I'm stuck with server-side scripting at > the moment.
Client-side, actually :-) > By the way, now that I have you in the thread, do you know or could "Now that you have *me* in the thread?" Uh?! > indicate me whree I could find some example on how to do this using xml > instead of html for the data? Well, I can't see how useful that would be. I mean, you're already applying a band-aid over it because you can't, so far, do it properly (server-side). Why would you want to add extra complexity by moving it to XML? This doesn't appear to be useful at all. I mean: 1) The data you're getting back are to be presented as HTML 2) Their semantics is probably properly represented by <p> and the like. 3) The data isn't generated by something else, then hand-converted to HTML, is it? It's created as HTML already, I suppose? So why adding unnecessary juggling? 4) Client-side processing of this XML would require manual exploration of its DOM (I assume you have no control over the client-side browsers, so XPath or E4X are out of the question), and XHTML DOM building (even with script.aculo.us' Builder...). Or even worse: XSL/T transforms! Yay! So, in a word: are you *sure* you want to add this extraneous complexity? -- 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 -~----------~----~----~----~------~----~------~--~---
