Re: component definitions

Christian Sell wrote:

>Hello,
>
>I would like to bring up again the point about component 
>configurations. As far as I remember there was no final 
>answer.
>
>In Tapestry component configurations have to be repeated for 
>every page and component which embeds the component. 
>Moreover, all components have to be assigned type aliases in 
>the application file (I am not familiar with the workings of 
>libraries yet).
>
>  
>
I think the slight awkwardness of specifying the small bits of XML to 
hook a component into a page is needed to allow multiple numbers of the 
same component on a single page. Remember, as part of specifying the 
component, you need to specify a unique id - partly this is a standard 
XML restriction for the ID attribute type, but also so that Tapestry can 
identify uniquely which component is being referred to.

Richard.




-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now!  Before the Holidays pass you by.
T H I N K G E E K . C O M      http://www.thinkgeek.com/sf/