[ tapestry-Feature Requests-657997 ] reusable component configurations

Feature Requests item #657997, was opened at 2002-12-23 21:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=657997&group_id=4754

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Christian Sell (csell)
Assigned to: Nobody/Anonymous (nobody)
Summary: reusable component configurations

Initial Comment:
add the capability of sharing component configurations
between pages and/or components inside the same
application. 

Often times, a component is embedded in several pages
with the exact same parameters. This may be the case
e.g.for a menu component. Instead of having to
re-specify the parameters inside the <component>
element in every .page file, the current
component-alias element in the application file could
be expanded:
 
 <component-alias type="Border1"
specification-path="somewhere/Border.jwc">
   <binding name="menuitems" expression='{"Item1",
"Item2", "Item3"}/>
 </component-alias>
 
 <component-alias type="Border2"
specification-path="somewhere/Border.jwc">
   <binding name="menuitems" expression='{"Item3",
"Item4", "Item5"}/>
 </component-alias>

pages/components could then reference these
"pre-configured" components. They should also be able
to override the configured parameters with their own
settings.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=354754&aid=657997&group_id=4754


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf