> You would need to implement your own ValidationDecorator. I just thought
> of it yet. It would be a better solution to your specific problem. There
> were some messages in this mailing list about it. The Tapestry sources are
> other nice places to see some examples about it.
ValidationDecorator
Em Sun, 06 Dec 2009 20:52:17 -0200, Piero Sartini
escreveu:
Hi Thiago,
Hi!
Thanks for the hint. I've thought in this direction as well but was not
sure if it would be possible at all. I like the mixin strategy because
writing myown components seems to duplicate lots of the
tapestry-c
Hi Thiago,
> I can think of two ways: using your own component to get the validation
> errors from the ValidationTracker or write a mixin that rewrites the
> generated DOM.
Thanks for the hint. I've thought in this direction as well but was not sure
if it would be possible at all. I like the mi
Em Sun, 06 Dec 2009 18:10:24 -0200, Piero Sartini
escreveu:
Hello,
Hi!
I want to overwrite the markup that is generated from tapestry for
client side validation.
I can think of two ways: using your own component to get the validation
errors from the ValidationTracker or write a mixin
Hello,
I want to overwrite the markup that is generated from tapestry for client side
validation. To be more detailed, I need to integrate the forms.css of the YAML
css framework:
http://www.yaml.de/en/dokumentation/css-bausteine/formularbaukasten.html
To use it the right way, it is not enough
