On Mon, Jun 8, 2009 at 10:34 AM, Otho<taa...@googlemail.com> wrote: > Well, there are some bits and pieces missing to make that feasible. Most > notably an easy skinning support,
Why can't we already do that with a Layout component, CSS and the Delegate component? > core ability to draw templates from > arbitrary locations Some people in this list have already done that. > and some standard components which belong into the core > IMO like for example a standard login/security/user management system, a > standard messaging/email component... in effect about the things which are > also offered by GAE as services. This will eventually happen as time passes. Tapestry 5 is still a young framework. > If you build high level components on the raw framework you'll run into > compatibility and interoperability issues otherwise. I'm not following you. Please enlighten me on what these compatibility and interoperability are. :) > Grails' success comes mostly from the rich ecosystem of plugins (and Gorm) > which _mostly_ interoperate just fine. To achieve the same in Tapestry is > not possible in the way they do it there, Why not? > but it should be possible to come > near enough when there are some well defined interfaces where you can plug > in your components. I guess you mean services instead of components in this message, something that confuses your reasoning. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
