Render cycle and allocated ids

[Scott Russell <sc...@hotmail.com>]

I find there is a lot of confusion and functional overlap in how unique ids 
are allocated to components during the render cycle. Personally I have found 
it to be a complete pain when designing my own components, especially for 
components that refer to other components (like FieldLabel). You have to 
ensure that the referred-to component has been pre-rendered, usually only so 
that the unique id has been generated.

On top of that, there are a number of component properties that are used in 
different places for the same effect - id, clientId, name.

Can I suggest that if the render/rewind cycle is refactored, that you:

a) Have a step before the render cycle that allocates unique ids to all 
components (and nested components) in the page,
b) Have 1 property that is the unique component id and deprecate the others. 

I think that would go a long way towards removing a lot of the difficulty in 
writing moderately complex components.

regards,
Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org