Interesting problem.
It helped me visualize the issue when I tried to suggest:
myPage() {
add(new Thing(this,...)); // 'this' doesn't exist yet
}
I think building component hierarchy from constructors feels natural and
it's going to be a hard sell to change to support this use case where some
components might need to know their parents.
I thought I was keeping pretty much up-to-speed on 1.5 changes, but I'm kind
of surprised this is the first I'm noticing this fairly substantial API
change.
Sorry if something like this has already been shot down - I didn't look -
but just off the top of my head, seems like there could be a way to have the
framework (as it is about to add a page to it's map or at some other
convenient early point) go back down thru the hierarchy and visit all the
components to offer them a parent reference? Maybe guarantee it would
happen before the first onBeforeRender or something like that?
Then, we could let these visitors 'vote' on when the hierarchy is finished
changing - (i.e. components could use this information to make additional
changes to the hierarchy) by returning a value. Perhaps call this new
component visitor something like int onParentChanged(Component parent) -
return flags that would let the framework interrupt and restart, repeat
after finish, or just continue visiting (or maybe just return boolean repeat
flag).
-- Jim Pinkham
TogetherAuction.com
On Tue, Mar 8, 2011 at 8:33 AM, Zoltán Nagy <zberke...@gmail.com> wrote:
> Hi!
>
> My idea is this: Somewhere in the future (for example in wicket 1.6)
> adding copmonents from the constructor will be prohibited, but till
> than it should be allowed.
>
> --
> Zoltán Nagy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
