changing the display/presentation of error messages is
just a matter of providing an own ValidationDecorator and
replacing the DefaultValidationDecorator in the environment.
Replacing or removing the 'bubbles' seems to be a bit harder
because they are hardcoded into tapestry.js. I've not found a
way yet to replace it.
g,
kris
public void
contributeMarkupRenderer(OrderedConfiguration<MarkupRendererFilter>
configuration, final Environment environment)
{
MarkupRendererFilter filter = new MarkupRendererFilter() {
public void renderMarkup(MarkupWriter writer, MarkupRenderer renderer)
{
environment.push(ValidationDecorator.class, new
MyValidationDecorator());
renderer.renderMarkup(writer);
environment.pop(ValidationDecorator.class);
}
};
configuration.add("MyValidationDelegate", filter,
"after:DefaultValidationDecorator");
}
(see https://issues.apache.org/jira/browse/TAPESTRY-1754)
"kranga" <[EMAIL PROTECTED]>
29.01.2008 01:02
Bitte antworten an
"Tapestry users" <[email protected]>
An
"Tapestry users" <[email protected]>
Kopie
Thema
T5 direction - general purpose vs specialized?
I was testing t5 (5.0.7) and saw that the form component automatically
throws bubble messages for validation. T5 also seems to utilize
Scriptaculous for achieving this. So my question is - is Tapestry meant to
be specialized or general purpose? All our clients dictate the look-n-feel
of error messages and such and so the default bubble will never work for
us.
I'm surprised that such a UI specific decision is made by T5. How much
work
will it be to use a different scheme for display/presentation of error
messages? How dependent is T5 going to be on Scriptaculous and how much
tweaking will one have to do to circumvent its use?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]