Kevin Menard wrote:
It seems this issue is going nowhere.  All I can say at this point is that I
agree with Robert's sentiments.  Despite the lack of strong showing on this
thread, I've heard the same concerns voiced by numerous other users,
particularly on IRC.
[...]

If the issue need some voice, there is mine ;) More seriously, it's really something that come quite often in the ML and on irc.
Once again, it's not that it's technically broken.  It's that in nearly
every other avenue, Tapestry goes out of its way to work out context for the
developer.  A lot of niceties go on behind the scenes and contribute to the
beauty of the framework.  In this case, it breaks away from that philosophy,
wipes its hands of the messy part and puts everything on the developer's
shoulders.  And it feels like this was the result of the evolution of the
type coercion system rather than a legitimate design decision . . . i.e.,
given what we know now up front, I believe the design would have been
radically different than it is now, working more for the developer.
I can't agree more, thank you Keven for this summary.
I also think that this is not the kind of big architectural move that should be change before the 5.0 final : we *really* need a stable, even non perfect, framework, quickly. I mean, I, the developper, now that 5.0.2 was more stable in alpha than other "final" product (out of the mind, hmmm, maven ?). But when I explain to my chief that T5 is now in "beta", since too years, he is asking if it's google, and if it's really cleaver to use such a non final product (it's a caricature, but ideas are here).
But perhaps it would be a good point to try improve that point for the 5.1 ?

--
Francois Armand
Etudes & Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
-----------
InterLDAP - http://interldap.org FederID - http://www.federid.org/
Open Source identities management and federation


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to