I could, but I always get the heebie-geebies when I drive stakes
through component encapsulation like that, it kind of feels like I'm
defeating the purpose of using a component based framework at all.> -----Original Message----- > From: Richard Clark [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 02, 2005 9:58 AM > To: Tapestry users > Subject: Pat vs. the toolbar (was Re: "Why I Like Annotations") > > Maybe I'm missing something, but you can define a parameter as > optional and give it a default value. Why not declare "listener" as > optional and default it to the listener in your root page class? > > I realize this doesn't make your toolbar class 100% reusable across > all projects, unless you document it as "calls listener > listenToTheMusic(allTheTime...), unless overridden by a listener=... > parameter". > > ...Richard > > > On Nov 2, 2005, at 9:30, Patrick Casey wrote: > > > > > My latest "I want" is a bit different from my earlier "I wants": > > > > I want to reduce the number of little pieces parts I have to change > > to alter the product. Lets say, for example, I want to add a new > > toolbar > > button to one of my forms: > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
