On Tue, Nov 9, 2010 at 4:39 PM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:

> Hi!
>
> Has this been attempted before? Would it be a good idea to go at it?
> Sure would help removing some boilerplate webmarkupcontainer code.
> Existing jira issue for this?
>
At least I haven't seen one.

>
> **
> Martin
>
> 2010/11/9 Martin Makundi <martin.maku...@koodaripalvelut.com>:
> > Hi!
> >
> > Does <wicket:enclosure> have capability to
> "setOutputMarkupPlaceholderTag" ?
> >
> > What I mean is that when I have:
> > <wicket:enclosure child="optional-field">
> > <tr>
> >   <td>optional content</td>
> >    <td><input type="text" wicket:id="optional-field"/></td>
> > </tr>
> > </wicket>
> >
> > If I set it invisible via ajax I cannot set it visible again.
> >
> > Instead, is there a way to do something like:
> >
> >
> > <tr wicket:enclosure="child:optional-field">
> >   <td>optional content</td>
> >    <td><input type="text" wicket:id="optional-field"/></td>
> > </tr>
> >
> > So that it would automatically handle visible/hidden
> > "setOutputMarkupPlaceholderTag" flavour so that I can repaint a hidden
> > element via ajax?
> >
> > @See
> http://jawher.wordpress.com/2009/09/17/wicket-enclosures-and-ajax-no-no/
> >
> >
> > **
> > Martin
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Reply via email to