It seems like the interaction you're talking about is "adding items
to a tree", and "displaying the tree" is a sub-component of that.
It's hard to know what to recommend without knowing what benefit they
get from seeing the whole tree while they're adding to it, but
here's what I assumed from your premise:
Folks (your users) are compiling an organized collection of items
from manually-entered records (say, compiling a database of phone
records, organized by country, state, city, and zip, for instance).
OR, they're searching for documents, and "building a tree" from
the results, into a taxonomy for later use by themselves or others.
In the above scenario, viewing the entire tree seems less important
to the data-entry folks - as just knowing that their record was added
to the tree, and where it was added (so they know it was added to the
right place).
In that case, for these people, it seems like you can omit most of
the child-records from the tree-view, and just display the nodes
above the records, to represent where they are, where they will be
adding records, and where their record was just added, as in:
Root Node
Node1(300 items)
Node2(5200 items)
[New Record]
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=35117
________________________________________________________________
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
