I've made more Trees, but they are not publicly avaibable. Also, they
don't differ that much.
Actually, I've been hoping all the time that more people would show up
to use the tree to get clear what the usuages would be. One thing that I
did anticipate though, is that the node definitions would have to be
flexible. For this I introduced method 'newNodePanel', which you can
override and have it return any Panel you like. So, providing your panel
with checkboxes on them should work too.
Please play with it, and try to accomplish what you want. If you run
into troubles, please let us know, and we'll check it.
I have been thinking about creating a more elaborate Tree example too
(inluding more elements, and a more row-like tree), but can't find the
time for it. One other thing on my list for 1.1 is to create a
javascript enabled tree, that would only generate roundtrips when you
select nodes, but not when you expand/ collaps nodes.
Eelco
Now i will be moving on to try my own implementation of you're Tree component.
Since i need a selection tree with checkboxes. I saw the "nested" example and
that looks like something i could use to begin with. Do you know if it is
possible to add a checkbox for all nodes ?
ala prepend html as in treeview.net ?
or do there already exsists a implementation of Tree besides MyTree.java ?
You're help is greatly appreciated :)
Best regards,
Frank,
Kastell
On Monday 11 July 2005 21:42, Eelco Hillenius wrote:
Yep. I'd like to stress though, that you can also work with more than
one model in a form. You can set a model on a form (e.g. by passing it
to super) for convenience. That way, constructs like:
add(new Label("myField"))
will automatically look up 'myField' in the model that was set on the
form. However, a construct like this is also valid:
class MyForm extends Form
{
final IModel model1;
final IModel model2;
public MyForm(String id, IModel model1, IModel model2)
{
this.model1 = model1;
this.model2 = model2;
add(new TextField("field1", new PropertyModel(model1,
"myFirstField")));
add(new TextField("field2", new PropertyModel(model2,
"otherFieldOnOtherModel")));
}
public void onSubmit()
{
Customer c = (Customer)model1.getObject(this);
Other o = (Other)model2.getObject(this);
}
}
and so on...
So, while form components (and a lot of components like Label etc) make
use of their models directly, this is not true for all components. Forms
do not use their models directly (same for Page, Panel, Border, etc),
and thus you can use as many models as you like.
Eelco
frank bengtsson wrote:
This is nice, does this means that both models are automatically updated
?
So "onsubmit" all i have do is something like this ?
customerDAO.saveOrUpdate(((Map) getModelObject()).get("customer"));
Thanx in advance !
/Frank
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar
happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest
in dual core and dual graphics technology at this free one hour event
hosted by HP, AMD, and NVIDIA. To register visit
http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
