My intent is that for complex UIs, you should be able to choose to use Backbone or Ember or ExtJS, etc. That Tapestry should get out of the way.
On Mon, Jun 11, 2012 at 10:05 AM, yazdog8 <[email protected]> wrote: > I think your summary of the current pain points with the Tapestry 5.3 JS > model were excellent. I had read a few of your posts about the possibility > of including a JS MVC with the system like Backbone or Ember. Is this still > a possibility or are you trending away from this? > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/More-details-about-Tapestry-5-4-JavaScript-tp5713773p5713776.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- 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: [email protected] For additional commands, e-mail: [email protected]
