Re: tapestry critique

>Typically, you'll create a standard Border component for 
your application,
>and configure the Calendar just once, inside your app-
specific Border.
>Every page that uses the Border gets the Calendar as well, 
configured
>identically.
>

that is yet another version of the wrapper component approach 
which was already suggested several times. I cannot say I am 
really happy with it. My suggestion (*just* a suggestion) was 
to let component configurations be defined at different 
levels within the application, such that these can be 
referenced from any nested context. That way, I could 
configure in my *.application file:

<component id="MyCalendar" type="bla.bla.Bla">
  <binding name="displayOption" 
expression="engine.calendarOptions"/>
</component>

and reference this from any page or component HTML file:

<span jwcid="application:MyCalendar"/>

(syntax arbitrary) without having to re-configure it in each 
and every .page or .jwc file, or having to create a wrapper 
component which has to be referenced from every file.

This is the same problem as with the border component in the 
workbench and tutorial examples, whose configurations are 
also "needlessly" repeated in every page file. In the 
workbench, re-configuration is partly avoided by pulling 
parameters from a properties file - which in essence means 
that the configuration is spread over different file types.

regards,
Christian


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/