Hi Greg, thanks for all your answers ... currently I'm looking at all features I'll need if they are already implemented of it they are planned (also the range selection on trees could help in this new component) ... no problem to add these for a future release.
No I'll add some ticket in JIRA, and if/when I'll have something that works I'll post for review. > expandAll and collapseAll are not implemented because it's not hard to do in > application code. A simple tree traversal with calls to setExpanded() would > do the trick. With only operating on the selection, it's even easier, > because you just iterate over the selected paths (getSelectedPaths()). Ok, I've looked at the code and this is right (no doubt :-) ), but i think that some common operations like these should be handled ... if not in the component in a utility class. I can make them, what do you think ? A last thing: for the background coloring of each row, do you think it's better to fire a dedicated event (by default not intercepted) and leave the custom code to do the logic, or the same but set as a (style) property, without firing events ? This (future and optional feature) could be applied to many elements, like i said in a previous mail (Tables, Lists, Trees, TreeTables, etc) ... If you think could be useful, I'll post also this as a reminder for future releases ... Comments ? Thanks for the moment. Bye, Sandro
