I've done work integrating Ext.GridPanel with Tapestry, but we've just let Ext render the data items on the client side. I've actually had a lot of frustration because of the impedance mismatch between Ext (the server provides just data) and Tapestry (the server renders all content).
On Wed, Mar 16, 2011 at 12:27 PM, Joe Klecko <buckof...@gmail.com> wrote: > > Thanks, I appreciate your response Howard. Your insight is helpful and > actually the behavior I was expecting from Tapestry (ie, injection of > javascript, css, etc). But I still feel I need to render the block into a > string so I can escape the output which can then be used as a javascript > parameter or a json value. I think it would be better for everyone if I > explain what I am trying to do: > > I'm in the process of creating a component library for Ext JS(which ehen > complete will be made open source), I'm currently working on a component > for the "GridPanel" and I am modeling it after Tapestries current grid,I've > where it determines the bean type from a datasource, creates the BeanModel > and has parameters such as "include, exclude, add, reorder". I have all of > this is working fine until I want to render properties which were added > using the "add" parameter. These properties will be rendered via a block > parameter (just like the tapestry grid) and since a "GridPanel" is updated > via a json object or javascript array, I need to render each of the block > parameters into a string(which can then have characters escaped by adding it > to a json object or manually), for my case I will be adding them to an > internal json object, and then rendering the the json object into a > javascript call which will be in a block which will be returned as part of > the zone update. I think some examples would make this a bit clearer: > > example in a page usage: > > > some rendered block which needs to have "double qoutes escaped" > > > > > example of GridPanel.tml block response: > > > > > > > example of GridPanel ajax response: > > > > As I see it there is no way to escape the rendering of a block. Which means > the output of a block can never be packaged up. > > If there is a better way to do this or if I'm going down a dead end street > please let me know. I'm also very open to alternate solutions. > > thanks in advanced! > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Rendering-a-Block-tp3401393p3795483.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
