New answers tagged tree
How about just showing the user the controls and details of the item they are working on with a 'breadcrumb' trail near the top. This is another common way to represent hierarchical information. For example the user might see the following at the top level (the 'Trunk'): If they select a branch, they might see the following: Of course this could be ...
So, I could be misunderstanding, but it seems to me that important part of the problem is the relationship between the branches and the trees. Putting them into two distinct boxes might not be the best approach to help the user visualize the hierarchy here. Have you considered using a tree view? Depending on the need, you could implement a limited tree ...
This is a true hierarchical model, so let's keep the mental model user have of a hierarchy. If your target audience are Apple users, implement the model Finder uses. And if they are Microsoft users, follow the design guidelines of Explorer. Make sure that your users don't have to think when they use your app. Splitting the hierarchy in two different views ...
I agree with Jonathan Strate. Adding a small edit icon or link will help. It will also use less real-estate. How about something like this? Reference: http://dropdown-check-list.googlecode.com/svn/trunk/doc/dropdownchecklist.html
Top 50 recent answers are included