On Jul 27, 2005, at 12:44 PM, Nick Westgate wrote:
I see the consistency problem if ognl is the default for templates.
(Adding jwcid shouldn't require changing prefixes for other
attributes.)
But if literal is the default for specs, we'll have ognl: everywhere
and a 'shallow' violation of DRY.
This is why I suggested there be a Tapestry property that can be set
to override the default for the more advanced user.
Templates and spec files are different.
To me, this is saying implicitly and explicitly declared components
are different. Now, of course the component is unaware of all of
this, but if I need to give consideration to the context in which the
component is declared when specifying parameter values, they are for
all intents and purposes, different. I typically start off
implicitly declaring components, and as they get larger, I move them
out to the spec file. Say I have n components, each with m
parameters, then when I move these components, I have n x m
opportunities to screw up the translations, which are odds I don't
very much care for.
It appears to me that default bindings across the board really take
care of this issue . . .
--
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
