There are not much to talk about. It's just a "Category field" where the user has to select categories that will be related to the record being edited. It's a List Field with hierarchical branches.
I can think in a lot of use cases for that. Another example: imagine that you create a form expecting the user to select the folder where he wants to save a file (just like docs.google.com upload). You're better using a tree field. Or a bookmark manager, image gallery, etc. On Tue, May 4, 2010 at 3:19 AM, MartinWittemann <[email protected]>wrote: > > Hi, > I am not sure what the reason was we left the tree out of the form items. I > think the main reason was I could not figure out why a tree should be a > form > item at all. But as you said, you have a valid use case. Could you share > your thought on that use case with us? > Regards, > Martin > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/qx-ui-tree-Tree-as-IForm-request-tp5000467p5001910.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
