Bruno, your problem is more of an issue with code beauty and design? I
agree that it's a bit misleading to have an setVisible method that
does nothing... As adding a fairly synthetic AjaxComponent subclass to
Component for using as a parent for every ajax-enabled component
doesn't seem justified,
setVisible doesn't work?It should work fine listview will not get rendered when you set it to none visible.And yes (talking to igor) i think it is a bit stupid that we do generate the items when the listview is not visible..
johanOn 5/18/06, Alvar Lumberg [EMAIL PROTECTED] wrote:
Bruno, your
yea, my bad. I was thinking about ajax side of things, sorry.
On 5/18/06, Johan Compagner [EMAIL PROTECTED] wrote:
setVisible doesn't work?
It should work fine listview will not get rendered when you set it to none
visible.
And yes (talking to igor) i think it is a bit stupid that we do
One thing at a time:1) setVisible works, when not doing through Ajax components like AjaxLink;2) ListView outputs one different id for each repeated line.3) when calling ListView.setVisible(false) from some onClick(AjaxRequestTarget), it does
not works.So pay attention to 3': setVisible can be
Bruno Borges wrote:
One thing at a time:
1) setVisible works, when not doing through Ajax components like AjaxLink;
2) ListView outputs one different id for each repeated line.
3) when calling ListView.setVisible(false) from some
onClick(AjaxRequestTarget), it does not works.
So pay
But why? Of course setVisible works on listview, why wouldn't it? Theproblem is that you are adding the list view to target. You should add a
component that contains the listview.Matej, ListView is a component conceptually equal to Label, TextField or whatever. The code I sent doesn't work. And
Bruno Borges wrote:
But why? Of course setVisible works on listview, why wouldn't it? The
problem is that you are adding the list view to target. You should
add a
component that contains the listview.
Matej, ListView is a component conceptually equal to Label, TextField or
you have to understand how ajax works.ajax updates the regiout between the component's html tags and the tags themselves.take Labelin markup it is span wicket:id=labelsome text/span
if you update the text and add it to the target you get this html sent throughspan wicket:id=labelsome other
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 ...
/trtr wicket:id=listView
td ...
/trtr wicket:id=listView
td ...
/trAnd that's the reason Ajax can't set visible(false) at the
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
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
and that parent would be??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
Well, that's the problem. ListView generates an incremental id for every row and this is the problem. How to set it invisible through ajax? And if ListView keeps outputting the 'id' attribute different from the 'wicket:id', I think that as a bug. This behavior is different from other components.
Bruno Borges schrieb:
ListView is considered one single component, with multiple
childs (ListItem).
That's true, but the *markup* associated with the ListView is repeated
with every child, so a there is no single HTML tag that represents the
ListView.
What you want is something like this:
i disagree,wicket's primary usecase is not ajax, but regular rendering. ajax is a very nice bonus and does not always work as smoothly as we would like.now the ajax solution for the listview is quiet easy, put it into a webmarkupcontainer and update that container instead of the listview via ajax
15 matches
Mail list logo
