Chris
Ive been following this thread with interest - what is the use case that
drives your need to add components dynamically - why can't you just add a
SytemPanel in the panel constructor - is your HTML markup being generated
outside of your Wicket app?
N
On Nov 24, 2012 1:26 AM, Chris Colman
Chris
Ive been following this thread with interest - what is the use case
that
drives your need to add components dynamically - why can't you just add
a
SytemPanel in the panel constructor - is your HTML markup being
generated
outside of your Wicket app?
Our use case is as follows:
We have a
historically the components you add from auto resolvers are added via
the autoAdd() method, not using add(). these components only exist
during render of the page (in detach() phase all auto-added components
are removed). the thinking here is that auto resolved components are
not normal
I had a thought - is there an interface implemented that provides the
parsing of markup? If there was then I could somehow hook into that or
provide another implementation and avoid double parsing of the markup -
or would that be happening too late in the lifecycle to work?
-Original
See IMarkupFilter implementations.
On Fri, Nov 23, 2012 at 12:08 PM, Chris Colman chr...@stepaheadsoftware.com
wrote:
I had a thought - is there an interface implemented that provides the
parsing of markup? If there was then I could somehow hook into that or
provide another implementation
Wow! That was a bit too easy!
Here's how to override onInitialize to dynamically add components to a
page that are specified in the markup:
protected void onInitialize()
{
super.onInitialize();
IMarkupFragment markupElements = getMarkup();
historically the components you add from auto resolvers are added via
the autoAdd() method, not using add(). these components only exist
during render of the page (in detach() phase all auto-added components
are removed). the thinking here is that auto resolved components are
not normal
The markup is parsed already, see Component#getMarkup().
Sven
On 11/23/2012 08:33 AM, Chris Colman wrote:
starting with wicket 1.5, however, components are able to resole their
markup earlier in their lifecycle. the reason auto resolved components
are added so late and treated specially was
Hi,
On Fri, Nov 23, 2012 at 9:33 AM, Chris Colman
chr...@stepaheadsoftware.comwrote:
starting with wicket 1.5, however, components are able to resole their
markup earlier in their lifecycle. the reason auto resolved components
are added so late and treated specially was because the markup
