Well, the tags are not new, as they do the perfectly same as extend and child. Basically, the patch only introduces an id attribute to those tags in order to make linking of markup more flexible. The new names were only introduced to keep functionality of the patch separated from the existing (and as the names child/extend are not very well chosen, as they aren't naturally related)
I see that it was a bad idea to rename the tags for the prototype. Obviously, everybody fears new tags and therefore dismisses the whole idea only for that reason. Evan Chooly wrote: > > In our app we have a ListView into which we can dump panels for, in > our case, various different filtering options depending on the page. > The base page keeps a List and that's used as the model for the > ListView. If the subclass doesn't add anything, nothing shows up. > But the pages that need them can add them. These panels show up in > the base page's markup area (outside the <wicket:child/> area) with no > hackery needed. > > I think the proposed patch is an overly complicated solution to > "problem" that has many different simple solutions. I agree with the > earlier comments about the proliferation of tags in wicket. I'd > rather not see new tags added just for this. It fuglifies the markup > for no real gain. > > On Nov 6, 2007 11:30 AM, Stefan Fußenegger <[EMAIL PROTECTED]> > wrote: >> >> I posted a new message in Wicket - Dev: >> http://www.nabble.com/Patch%3A-Multiple-%3Cwicket%3Achild--%3E-tags-on-a-single-base-page--tf4759260.html >> >> It contains a patch that demonstrates the discussed enhancement. Please >> comment! >> >> -- stefan >> >> >> Stefan Fußenegger wrote: >> > >> > Hi folks, >> > >> > I just stumbled on a situation where it would be useful to have two or >> > more <wicket:child /> tags in a base page. Just consider a layout that >> > consists of the usual footer, header, navigation, and content parts. >> But >> > now, the content should be arranged in two columns, e.g. two different >> > <div />s. >> > >> > To give a short example, the BasePage.html cloud look like this >> > >> > -------- >> > <body> >> > >> > <!-- some layout markup --> >> > >> > <div class="content_left"> >> > <wicket:child /> >> > </div> >> > >> > <!-- more layout markup --> >> > >> > <div class="content_rigt"> >> > <wicket:child /> >> > </div> >> > >> > <!-- even more layout markup --> >> > </body> >> > -------- >> > >> > And the Child.html markup would look like this: >> > >> > -------- >> > <body> >> > >> > <div class="content_left"> >> > <wicket:extend> >> > <!-- content of left column (first child) goes here --> >> > </wicket:extend> >> > </div> >> > >> > <div class="content_rigt"> >> > <wicket:extend> >> > <!-- content of right column (second child) goes here --> >> > </wicket:extend> >> > </div> >> > </body> >> > -------- >> > >> > Wouldn't that be a desirable feature? I tried to run the above example >> > expecting to get an exception. The second wicket:child/wicket:extend >> pair >> > was happily ignored though. >> > >> > Best regards, Stefan >> > >> >> >> ----- >> ------- >> 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#a13610287 >> >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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] > > > ----- ------- 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#a13623106 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
