Hi,
Jeremy Thomerson-5 wrote:
I agree 100% - that's the only clean solution I see.
To let you all know - Igor has provided a quick solution and committed it to
a trunk. Now there is overridible Component#renderPlaceholderTag method.
Regards,
Adam
--
View this message in context:
placeholder for tr component causing invalid
markup
I agree 100% - that's the only clean solution I see.
On Mon, Jan 26, 2009 at 9:25 AM, the_adam
adam.parchimow...@gmail.comwrote:
Jeremy Thomerson-5 wrote:
The problem you're facing is clear - and you're right -
wicket:enclosure
won't work
Phooey wrote:
I'm unclear of what you actually want here...
Actually what I want has been already provided as stated in my previous post
:)
Phooey wrote:
Surely if you use the wicket:enclosure around a tr (something I have
done in the past) then surely all you need is a little ajax to
Hi,
I'm pretty sure what you need is wicket:enclosure [1] instead
[1] http://cwiki.apache.org/WICKET/wickets-xhtml-tags.html
the_adam wrote:
If we have a component with a corresponding markup tag tr and want to hide
it and display placeholder tag via Component#setOutputMarkupPlaceholderTag
Pills wrote:
I'm pretty sure what you need is wicket:enclosure [1] instead
That would be the case if I've wanted to hide certain rows forever, unless
I'm largely mistaken. I want to be able to switch the visibility of certain
table rows and since Wicket's AJAX works by replacing given DOM
the_adam wrote:
Pills wrote:
I'm pretty sure what you need is wicket:enclosure [1] instead
That would be the case if I've wanted to hide certain rows forever, unless
I'm largely mistaken. I want to be able to switch the visibility of certain
table rows and since Wicket's AJAX works by
Thies Edeling-2 wrote:
That's exactly what wicket:enclosure does; otherwise you'd have to wrap
the
row in a WebMarkupContainer to keep a reference in the DOM.
I know the benefits of wicket:enclosure. What I need, however is a
placeholder, which is what wicket:enclosure doesn't provide
The problem you're facing is clear - and you're right - wicket:enclosure
won't work for you. Unfortunately, that closed-tag code for the placeholder
is hard-coded in Component.
Hmmm Could you instead have a wrapping component inside of your TR and
use that for the visibility swap? That's
Jeremy Thomerson-5 wrote:
The problem you're facing is clear - and you're right - wicket:enclosure
won't work for you. Unfortunately, that closed-tag code for the
placeholder
is hard-coded in Component.
Thanks for understanding :) Also, I've looked already in the Component
source and I
I agree 100% - that's the only clean solution I see.
On Mon, Jan 26, 2009 at 9:25 AM, the_adam adam.parchimow...@gmail.comwrote:
Jeremy Thomerson-5 wrote:
The problem you're facing is clear - and you're right - wicket:enclosure
won't work for you. Unfortunately, that closed-tag code
10 matches
Mail list logo