Hi Guilherme,

sorry for the late answer.
1. I see that it needs to configure the model before setting it to the tree (configureTriState). That is going to be a problem when adding new items to the model. The user will have to remember to configure each item before adding it to the tree. It can lead to some items being configured and others don't.

Maybe a solution could be configureItem as a delegate function, to centralize that.
I have done the setting on the model, because the Tree shows only the open nodes. So the model would be inconsistent for items which are not shown. Therefore it is not possible to set the checked state with the tree.

2. I don't know how the checkboxes in the tree could be useful the way it is. But if we could use the checkboxes to determine the selection of the tree, then it could be used in forms. Is there an easy way to bind the checkbox to the selection? I tried some things but all was based on subclass-ing (almost) all classes involved. Maybe there is a easier way, or should exist.

(from what I see looking at other frameworks, the checkboxes are indeed used to select items in the widget (ExtJS, ajax.org <http://ajax.org> UI).
At the moment the Tree only supports single selection. Therefore it is not possible to bind the selection with the checkboxes. I think when the multi selection is implemented a binding between the selection and the checkboxes should be possible and 3. is then not needed.

3. If 2. is considered, maybe the selection code in VirtualTree could be in a Selection Manager class. And maybe, another selection manager class (different from the default one) could handle checkboxes as selection widgets. Imagine being able to do so:

tree.setSelectionManager(new qx.ui.tree.selection.CheckboxSelectionManager());

and it all would be handled by that class.

Cheers,
Chris

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to