If you have markup like this:
<div wicket:id="c"></div>
You can put any panel (named "c") in using the add-method and later switch it 
to any panel (named "c") using the replace-method. You could create lots of 
tiny reusable panels and compose them into various structures. In my mind, 
Wicket is just as flexible as desktop programming because markup is limiting 
only where you want it to be limiting. When a panel needs lots of flexibility 
it tends to be small and when it doesn't it tends to be large.



----- Original Message -----
From: Dmitry Grigoriev
Sent: 11/10/10 05:41 AM
To: users@wicket.apache.org
Subject: Are there any cases when I can rearrange component tree?

Hello all,I'm new to Wicket. Just wonder about subj (theoretical interest). On 
onehand, stateful component model has no architectural limitations on itsown 
preventing me from reattaching component to different parent, justlike I can do 
with desktop applications or with any self-contained treestructure. On another 
hand, Wicket's component tree structure is boundto hard-coded markup, making 
such change-of-parent impossible.Is thereany opportunity to do this? (No matter 
how sophisticated.)The reason for my interest is that I'm collecting ideas for 
statelesscomponents support in my web framework. Stateless component 
hierarchywould likely be immutable (hard-coded into application logic rather 
thanstate) which looks like a significant limitation at first sight,compared to 
"do-anything-you-want" desktop programming. But I don't yethave much experience 
with web component frameworks and don't know isthis limitation really annoying 
or not. For now it seems to me thatWicket has this lim
 itation too but does not suffer a lot from it. Am Iright?Thanks.-- 
Cheers,dimgel---------------------------------------------------------------------To
 unsubscribe, e-mail: users-unsubscr...@wicket.apache.orgfor 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

Reply via email to