On Tue, Nov 9, 2010 at 8:10 AM, Carl-Eric Menzel <cmen...@wicketbuch.de> wrote:

sadly there are valid usecases for having the hierarchy purely for design purposes. an easy example is:

<tr wicket:id="repeater"><td><span wicket:id="first"/> <span wicket:id="last"/></td></tr>

now the designer wants tds to have a css class based on some condition. you now have to add a webmarkupcontainer to represent the td and renest first and last labels into it. the container is there purely for the design aspect.

with queuing you can queue first and last under the repeater item. when you need to add css to td you simply queue the webmarkupcontainer under the repeater item as well and wicket will properly nest the labels in it for you.

another usecase is introducing an arbitrary webmarkupcontainer just to have a div to repaint via ajax. it is hard to do this when refactoring a complex page because you have to find all the components that now need to be re-nested into the new container.

hopefully queuing can eliminate some of this noise and make it easier.

-igor