The problem, I think, you are going to run into with check-boxed tree-views is the expected behavior when multiple sub-item "views" are selected. It could be an [OR], [AND], [XOR] -- so what is the actual behavior when selecting multiple things? Are you [OR]ing the data views, or traveling down a tree of exceptions - for instance: All Fruit > Apples >> Only Grannysmith OR All Fruit > Apples >> McIntosh which would join those two sets?
Is this what you are asking? Functionally - tree views details pane is a design pattern you could use, but it's broken for this purpose. This kind of data really is best served with a dynamic visualization - thingk of building a semantically rich graph (data nodes/sets of data are visually represented, and not dumb graphics, but semantically meaningful so you can do analytics against them) so users can visualize the data sets and how their interactions include/exclude/change the outcome dataset. One other thing, is that you may end up - as I have - having to spend a decent amount of time working through all the set theory edge cases for how this works, what is displayed, and what the user expected to be displayed. Visualizing set theory is not an easy thing if your target is not quantitatively inclined. - Will . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=28087 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
