Hi Lance, That really is looking like the only plausible solution that hides away boilerplate mark-up/config. All these kinds of components are very similar in nature. (Bung some things into other named things under a thing). It would be cool to be able to mangle (read: modify) the parameter tag to allow this sort of flexibility and avoid creating another component but perhaps the difference is just 'icing', a couple of files here or there.
Thanks for the response. I guess I'll go in this direction unless a blinding strike of lightning (or someone else) hits me in the face later on! :) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Component-Utilizing-PropertyOverrides-Adding-Override-Blocks-Dynamically-tp5719973p5719978.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
