Ramnivas,Did you get the DOJO-based tree working? If so, I'd be very interested in it.SteveOn 3/29/06, Ramnivas Laddad
[EMAIL PROTECTED] wrote:Hi,I am continuing my attempt to create a DOJO-based tree (Thanks Igor for
the urlFor() tip).Currently, I am facing a problem of extra markup emitted in a
And so am I :)
Eelco
On 4/4/06, Steve Knight [EMAIL PROTECTED] wrote:
Ramnivas,
Did you get the DOJO-based tree working? If so, I'd be very interested in
it.
Steve
On 3/29/06, Ramnivas Laddad [EMAIL PROTECTED] wrote:
Hi,
I am continuing my attempt to create a DOJO-based tree
Hi,
I am continuing my attempt to create a DOJO-based tree (Thanks Igor for
the urlFor() tip).
Currently, I am facing a problem of extra markup emitted in a listview.
I think there is something wrong with my code, but can't quite figure
out what. I am using 1.2-beta2.
Here is a short
Change the markup to:divdiv wicket:id=listspan wicket:id=item/span/div/divand your listview:populateItem(Item item) {
item.add(new Label(item).setRenderBodyOnly(true));}Names may have been changed, due to negligence of my memory.MartijnOn 3/30/06,
Ramnivas Laddad [EMAIL PROTECTED] wrote:
Hi,I am
That sort of worked (rendered "wicket:id="list" tags, but not
wicket:id="item" tags). However in case of the DOJO-based tree, since
tags for each node (along with a bunch of attribute) need to be
written, I needed the opposite.
HOWEVER, your suggestion gave me an idea for a variation and it
most times you do want the listitem's markuplike li wicket:id=listview.or tr wicket:id=listview-Igor
On 3/29/06, Ramnivas Laddad [EMAIL PROTECTED] wrote:
That sort of worked (rendered wicket:id=list tags, but not
wicket:id=item tags). However in case of the DOJO-based tree, since
