On Tue, 03 Apr 2012 10:06:38 -0300, Chris Mylonas <ch...@opencsta.org>
wrote:
thanks again Mr T
heheheh I don't look like him much, but I sometimes read some questions in
this mailing lists (fortunately, just a few) and think "what's this
jibber-jabber you're talking?", hehehe
tapestry could benefit from a "rosetta stone" of the equivalent methods
of doing the same thing.
That's a good documentation suggestions . . . JIRA please? :) Usually,
Tapestry avoids to provide more than one way of doing the same thing. On
the other hand, sometimes the Tapestry flexibility and architecture ends
up providing alternatives.
i've spent a few hours today templating my first component with
MarkupWriter.element()/end(), writeRaw() and .tml files.
Each have their strengths.
Yep. Templates are generally easier to read and write, but MarkupWriter is
better when you have more complex logic and attributes that may or may not
be added. In addition, MarkupWriter supports recursion (it's just Java
code, after all), while templates don't.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
