On Wed, 30 Oct 2013 21:51:40 -0200, Lenny Primak <lpri...@hope.nyc.ny.us>
wrote:
We have scenario #2 with the caveat that designer used their own tool to
edit templates and the IDE runs in the background so they can check how
the web site looks live.
In the end, with any kind of dynamic page, Tapestry or Wicket or Play or
PHP or anything else, running the application is the only way of the
designer be sure the result of their edits is the expected one. And I
really love the fact that Tapestry templates, even when using complex
components that generates lots of markup by itself, still look like
regular, ordinary HTML. Now compare with JSF templates, specially
non-facelet ones, for example.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
