Glad we agree. The advantage of all the annotations, naming
conventions and meta programming is that you can gracefully evolve
(away from stupid names, etc.).
On Thu, Nov 6, 2008 at 3:55 AM, Geoff Callender
<[EMAIL PROTECTED]> wrote:
> Hi Howard,
>
> I completely understand your position on this.
Hi Howard,
I completely understand your position on this. If any of the
suggestions people have made in https://issues.apache.org/jira/browse/TAP5-274
are on the right track then it's not a trivial task, so it would be
better to get 5.0 out first.
Cheers,
Geoff
On 06/11/2008, at 6:13 A
I don't see this as a "last chance" ... we can define a new annotation
with a better name and deprecate @ApplicationState, but still support
it indefinitely.
I'm trying to stick to the absolutely essential work to get a release
out; bad naming is ugly but workable.
On Wed, Nov 5, 2008 at 9:59 AM,
Good Suggestion for ApplicationSessionObject.
I usually don't like it when such a commonly used feature is changed this
"late" in the game.
My suggestion would be to have the old annotation deprecated for a while,
with the new Annotation in place.
Furthermore, if a new annotation for Application
I think we must support both @ApplicationStateObject and the new
annotation, but i suggest not to change de acronym ASO because is so
widely used that would break a lot of useful searchs and is a common
lingo in tapestry, so the new annotation may be
@ApplicationSessionObject.
César.
Tapestry users"
Sent: Wednesday, 5 November, 2008 3:30:18 PM GMT +02:00 Athens, Beirut,
Bucharest, Istanbul
Subject: T5: @ApplicationState is misleading - voters wanted!
With the final version Tap 5.0 fast approaching, this may be the last
chance to address issues of confusing terminol
With the final version Tap 5.0 fast approaching, this may be the last
chance to address issues of confusing terminology.
If you feel that the term @ApplicationState is misleading - that is,
if you have ever felt that @ApplicationState implies a field will
become shared between all users in
