Small fixes in the javadoc:
1) "Add this point in time "
shouldn't that be "At this point in time" ?
2) "all parents must be have been added to their parents"
=> I would remove the "be"
Maarten
On Fri, Apr 2, 2010 at 11:09 PM, Igor Vaynberg wrote:
> from Component.java in 1.5 (trunk)
>
>
being thrown at runtime.
++
_
From: mbrictson [mailto:m...@55minutes.com]
To: users@wicket.apache.org
Sent: Sat, 03 Apr 2010 01:49:49 +0200
Subject: Re: What about an onInitialRender method ?
Good example. Thanks for clarifying.
igor.vaynberg wrote:
>
> one usecase
Good example. Thanks for clarifying.
igor.vaynberg wrote:
>
> one usecase is when you want the user to be able to change which
> components will be created.
>
> this is bad:
>
> class mycomponent extends panel {
> public mycomponent(string id) { add(newCounter("counter")); }
> protected C
one usecase is when you want the user to be able to change which
components will be created.
this is bad:
class mycomponent extends panel {
public mycomponent(string id) { add(newCounter("counter")); }
protected Component newCounter(String id) { return new Label(id, ); }
}
because you ar
Joseph,
Could you elaborate on why adding components in onBeforeRender is "safe" and
a "wicket good practice"? I haven't come across this very often in my
projects. Under what circumstances would you recommend this approach?
josephpachod wrote:
>
> hi
>
> The other day, I was busy creating re
10 23:09:27 +0200
Subject: Re: What about an onInitialRender method ?
from Component.java in 1.5 (trunk)
/**
* Callback method invoked after the component was added to its
parent AND you can walk up the
* hierarchy up until the Page. That is, all parents must be have
been added to
from Component.java in 1.5 (trunk)
/**
* Callback method invoked after the component was added to its
parent AND you can walk up the
* hierarchy up until the Page. That is, all parents must be have
been added to their parents as
* well. Add this point in time {..
