I'm totally with Pat and Scott on this.
For a tool to behave consistently is a critical point, and to do this
you should avoid different behaviour without any apparent reason.
In the long run the simple routine of performing those little but
familiar steps will become automatical for you (believe me, it's true),
while
preserving consistency and clarity for the newbies.
-1 for automagical annotations =)
Ivano
Patrick Casey wrote:
I'm with Scott on this one. I think that less auto-magic, not more,
makes the framework infinitely simpler for new users to understand. One of
my long-term usability complaints about tapestry 3.0.3 has been the
inconstient use of the "ognl" prefix in an effort to save keystrokes because
tapestry should just "know" that I mean the litteral "foo" instead of the
derived value getFoo().
I'd hate to see the same confusion make its way into Tapestry 4.0 as
well. To my way of thinking the additional keystrokes required to annotate
everything the same way is more than offset by the shorter learning curve of
a system that has one, and only one, consistent way of injecting things into
pages.
--- Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
