>New Component (Tapestry pre 2.4): >--------------------------------- >1 x defining a new component > 5 lines + 'component configuration', 1 line template, 1 line alias > >N x using the new component > 1 line in page definition, 1 line in template > >New Component (Tapestry 2.4): >----------------------------- >1 x defining a new component > 5 lines + 'component configuration', 1 line template, 1 line alias > >N x using the new component > 1 line in template > >Suggested solution: >------------------- >1 x defining a 'configured component' > ? lines + 'component configuration' > >N x using the 'configured component' > 1 line in template >
huh? Sorry I really cannot follow. What are those 5 lines? What is "? lines + 'component configuration'"? Heres my arithmetics for Tapestry 2.3, per component: 1. define type alias in .application file (1 line) 2. define component configuration in every page or component that embed the component (N lines each) 3. reference the component in the HTML template per jwcid my suggestion: 1. make type aliases optional (tapestry 2.4?) 2. define component configuration at a level so that provides the highest reuse so that nested levels can make use of it as is, or override/extend it. 3. reference the component in the HTML template per jwcid This can possibly save dozens of re-configurations (several lines each), if a CC (Component Configuration) is reused across several pages. The "new component approach" is yet more verbose, and is IMO not the least bit more powerful than the approach described above (they dont preclude eachother, however). regards, Christian -- [EMAIL PROTECTED] ------------------------------------------------------- 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/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
