On Tue, Nov 06, 2007 at 10:23:26PM +1100, Chris Colman wrote: > > In the panel example you give you must still provide all of the > structural markup surrounding your panel tags in EVERY page's markup in > your system and if you decide to make a system wide change of this > structural markup you must edit every page's markup to reflect that > change. In an OO markup world you provide the structural markup in as
Huh? Why wouldn't the structural markup be inherited by child pages? To my mind, wicket:extend/wicket:child is just a convenience feature, to save us from having to create child pages as page/panel pairs. jk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
