Thanks Tiago
Really strange component behavior since it's in total contradiction with
the framework spirit :
"Designers love it because Tapestry templates are so close to ordinary
HTML, without all the cruft and confusion seen in JavaServer Pages."
"The goal in Tapestry is for component templates, such as Index.tml, to
look as much as possible like ordinary, static HTML files. /By static,
we mean unchanging, as opposed to a dynamically generated Tapestry
page./ In fact, the expectation is that in many cases, the templates
will start as static HTML files, created by a web developer and then
be/instrumented/ to act as live Tapestry pages."
I suppose that the "ignoreBody" parameter is a king of palliative but
really boring in the long time ...
Shouldn't it be put in conformity with the remaining of the framework
before the final 5.0 release ???
Stephane
Thiago H. de Paula Figueiredo a écrit :
Em Wed, 22 Oct 2008 06:54:33 -0300, Stephane Decleire
<[EMAIL PROTECTED]> escreveu:
But with the following piece of code, the result is the hardcoded
"Firstname" string. Localization of the string did not occured ...
<t:label for="firstname">Firstname</t:label><input t:type="TextField"
t:id="firstname" ... />
This is how the Label component works: if you provide a body, it uses
that body and doesn't use the internationalized label. I don't think
this is a good idea because it breaks the component's previewability.
Tapestry CRUD has a Label component that works like you (and me)
expect:
http://www.arsmachina.com.br/maven/tapestry-crud/ref/br/com/arsmachina/tapestrycrud/components/ImprovedLabel.html.
