Yes, I guess it's possible. Are you setting the screen using data.setScreen() or passing it along the url?
I agree the client side is more difficult. Have you ever tried dojo? :: Leandro On 10/7/06, Thomas Vandahl <[EMAIL PROTECTED]> wrote:
Leandro Saad wrote: > Correct. > > JSON is not AJAX. JSON is a (very good) way to serialize your data and send > it to the client. > IMHO turbine should leverage the pipeline concept in order to promote reuse > on modules for classic and ajax requests. I've done this on Guara, a small > framework based on Turbine. In Guara, you can execute the exact same > action, > for instance, ListUsers or AddUser, but send a totally different > response to > the browser because the pipeline for ajax does not render the layout, for > example. > You can do that in plain Turbine as well. I have used the JAXB approach quite successfully (actually I use the Altova generated classes from a XSD, but this is very similar) This is using a RawScreen, thus bypassing the template engine. This approach works nice for all kinds of plain Ajax requests. *But* you need to write the stuff to extract the data needed for display in JavaScript anyway. Prototype and Scriptaculous help a bit but it is still a PITA, given the fact that testing/debugging JavaScript cross-browser is still a nightmare. So from my point of view the whole Ajax stuff is not an issue of the server framework, but the client support. Bye, Thomas. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
