On Fri, 30 Apr 2010 11:38:21 -0300, Howard Lewis Ship <[email protected]>
wrote:
I think it's a balancing act: perfect backwards compatibility means
leaving a long-lasting mess behind just to be compatible with features
that almost nobody uses ... but I tend to lean a bit towards "make it
right' vs. "make it compatible".
IMHO, the compatibility that must be kept in Tapestry is features that are
used in page and component classes, as they comprise most of an web tier
implementation. A change regarding how translators are contributed
wouldn't be an issue, I guess. Few lines of code would need to be changed.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
