Eelco Hillenius wrote: > >> It would be quite feasible to add support for multiple overridden >> sections using the above tag names while remaining backwards compatible >> with existing markup by continuing to support the old <child/extends> >> tags working the way they always have. > > It's kind of a predictable answer, but the best way to push new ideas > forward is to supply us with a patch, so that we can discuss some > working code. The current committers don't see much in the idea, but > that doesn't mean they wouldn't want to support at least the option of > plugging this in. And hey, maybe some working code convinces us :-) > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > >
Hi eelco, I'd love to do a proof of concept here. Admittedly, I don't know wicket's inner workings very well. But if I get some support, I'd try implementing this. I am currently looking through the code, but can't find where the transition between parent and child takes place (in other words: the line of code that recognizes the wicket:extend tag and takes the appropriate action). If somebody could point me to that line I would try to implement this possible new feature ... well, I'll first estimate the time necessary to do so and see if I can afford it ;) Regards ----- ------- Stefan Fußenegger http://talk-on-tech.blogspot.com // looking for a nicer domain ;) -- View this message in context: http://www.nabble.com/Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4738673.html#a13586814 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
