On Dec 17, 2010, at 12/1712:53 PM , Thiago H. de Paula Figueiredo wrote: > On Fri, 17 Dec 2010 16:35:43 -0200, Robert Zeigler <robe...@scazdl.org> wrote: > >> Just to clarify, I hope that by "true" you mean that id generation is turned >> /on/ by default. :) > > Your hope isn't in vain. :) true = on in this case. > >> warnings as time allowed. The important thing is that even with deprecated >> methods, the old /behavior/ was preserved. It's a policy we should adhere >> to more in Tapestry. What users need /most/ from the framework is >> dependable behavior; in large part, they need that more than the few bytes >> of bandwidth saved by removing the id from the label component. > > Agreed. I guess most of the disrupting changes were just honest mistakes. > It's kinda hard to foresee of all the consequence of a change, specially when > most of the users (the developers using Tapestry) are not in your team. >
Fair enough. Robert > -- > 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: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
