> Say you have two forms on one panel (don't know if this is the best
> example or not, but here goes). You want to move a field from one
> panel to another. You'd have to do that in code with the traditional
> approach. With the "queued" approach, you'd just queue all your
> components to the parent container and it would auto-add them to the
> correct subcomponent as it finds them in the markup.
>
> With this, the order does matter, though. Suppose you had two
> components you wanted to queue with the same id, completely different
> components. If you reverse their order, then they're auto-added in a
> different order.
Yeah ids must be unique per each level and ofcourse if you have markup like:
<div wicket:id="a"><div wicket:id="a"></div></div>
If you have code like:
panel {
queue(a("a"));
a.queue(a("a"));
}
It is pretty evident what goes into where but not very good naming convention ;)
**
Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
