A markupcontainer? a panel is a markup container.. pretty much all are.
I think you mean.. the listview must be added to a container where he is the only child??
to require that looks stupid to me.
Maybe we could some do "see" it as one object by generating an markup id for every listview html component...
"listview1", "listview2" and then target that as one thing. But that is more a thing for igor i guess.
johan
On 5/17/06, Bruno Borges <[EMAIL PROTECTED]> wrote:
Sure, I know about that, but the way we code for other things like Label or TextField, it works, right? So, for ListView it should work too. It's a component just like other.
Maybe a change at the API so ListView can't be added directly to (Some)MarkupContainer? And require the developer to add it into some parent like Panel or anything else dummy.
I know this would break _all_ projects working with ListView. But I think it's necessary.On 5/17/06, Johan Compagner < [EMAIL PROTECTED]> wrote:as far as i know you need to wrap it in a span or something (no need for a panel)
and target that to set visible and so on. Because in html you need to target one thing (id)On 5/17/06, Bruno Borges <[EMAIL PROTECTED]> wrote:Looks like setting visible false at a ListView instance isn't working properly.
The html printed out by wicket is something like this:<tr wicket:id="listView">
<td> ...
</tr>
<tr wicket:id="listView">
<td> ...
</tr>
<tr wicket:id="listView">
<td> ...
</tr>
And that's the reason Ajax can't set visible(false) at the listView component.
You guys will probably say that I should put my ListView into a Panel (or a fragment maybe? new stuff...) but conceptually the use of ListView and how we should making it invisible at an Ajax request, it's correct I think.
Thanks--
Bruno Borges
Summa Technologies
--
Bruno Borges
Summa Technologies
