From my understanding the proposal works like this that you have a
partially code controlled hierarchy of components when you need it for
functional reasons (security, AJAX refresh, visibility, etc). You can
define the parent of a component but technical you allow child
components being nested at will in the HTML markup (below that code
controlled parent). So if you do parent.add(component) you say that the
component must be either added as a direct or indirect child to this
parent => if you do parent.setVisible(false) all childs will still be
invisible no matter how they are nested among themselves.
So you give the HTML designer a bit more freedom in layouting components
below a given code controlled parent. I think that would be a reasonable
approach.
On 09.11.2010 17:05, Carl-Eric Menzel wrote:
On Tue, 9 Nov 2010 17:46:13 +0200
Martin Makundi<martin.maku...@koodaripalvelut.com> wrote:
@Carl-Erik
Reason why I haven't commented your "enabledInHierarchy" comment is
because it would not afect it in any way.
I hope the proposition will be clear when we have it ready. We are
working on Igor's proposal.
It will be interesting to see how you propose not affecting something
that depends on the hierarchy when you remove the hierarchy.
Carl-Eric
www.wicketbuch.de
---------------------------------------------------------------------
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
