Yes. .. That's what we did in Tacos. ;) Howard already has the infrastructure in place to do it in T5. This just sounds like a great test of that infrastructure. (though I'm not sure if the ability to "claim" an attribute is there, but if not I'd personally like to see it for some other items as well - like UI "behaviour"s such as a google rounded corner / drop shadow image service. )
On 1/16/07, andyhot <[EMAIL PROTECTED]> wrote:
Nick Westgate wrote: > Mind Bridge wrote: >> With respect to Nick's suggestion for "renderif": I think this is >> actually a larger issue -- the ability to add something like a >> plug-in for selection of the components. This is something like AOP >> for the web. > > Yeah, I've always considered the Any component to be like the root of > the Tapestry component hierarchy. To be able to plug in (mixin as Yunhua > mentioned) functionality and have it "inherited" down would be great. > Sounds like a biggie, though. > > Perhaps I should have mentioned my idea a year or so ago when Jesse was > starting 4.1, but a new parameter for all components risked heresy. ;-) I know people have done exactly this in T4.0 with a custom enhancement worker. > > Cheers, > Nick. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
