Just to clarify, I hope that by "true" you mean that id generation is turned 
/on/ by default. :) At least for 5.2.4. It could be off by default in 5.3. But 
these sorts of seemingly innocuous but actually disruptive changes (and yes: 
nixing the id of an element is a disruptive change!) should happen 
incrementally.  Eg: 5.2 introduces the ability to turn off id generation in the 
label component, leaves ID generation ON by default, and warns in the upgrade 
notes that the next version of tapestry will turn ID generation in labels /off/ 
by default.  Then 5.3 turns it off.  And /maybe/ in 5.4, we remove the flag... 
maybe.  This is the basic model that the cayenne team has used to migrate the 
cayenne api and it has worked very well.  Upgrades are painless.  I've never 
had a cayenne upgrade require more than about 20 minutes of my time, even when 
I upgraded an app that made fairly advanced use of cayenne from 2.x to 3.x.  
There were deprecation warnings, to be sure.  But I could still deploy a 
perfectly functional application, and get to the deprecation 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.

Robert

On Dec 17, 2010, at 12/1711:57 AM , Thiago H. de Paula Figueiredo wrote:

> On Fri, 17 Dec 2010 15:40:13 -0200, Andreas Andreou <andy...@di.uoa.gr> wrote:
> 
>> i wouldn't worry about that js performance and i do believe that the
>> current is the
>> correct default behavior but i do understand that this change breaks
>> existing running apps.
>> 
>> I see three options:
>> - bring the ids back (framework change)
>> - implement some kind of postprocessor that adds an id to all labels
>> (application change,
>> but the code could eventually live in the framework)
>> - modify application js
> 
> One more option:
> * Add a configuration symbol turn on or off the id generation. Default value: 
> true.
> 
> -- 
> 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

Reply via email to