Community
Participate
Working Groups
- As you drill down you have no indication of the context that you are in. - Forward and back don't make sense, its really up or down since its a tree - We could borrow from the MS file explorer's where you get a dropdown viewer at the top that show your parent tree. This allows you to pick a spot in your parent tree to go back up to. NOTES:
PRODUCT VERSION: 045
There are no plans to change the current behavior
Reopened for investigation
A drop down on the toolbar to skip frames would be useful. Forward and back *does* make sense since you navigate in the frame history. Back could mean down in the tree if you used up. Note that the tooltip on the navigation buttons shows the location you would get to so there is some context.
Reassigning to Nick since he is taking ownership of Navigator
Q: Do we even need "Go Into" style navigation any more? Almost everyone is now familiar with forward/back arrows in the context of browsing the web, and our use of them (in the main coolbar) matches peoples expectations (including having historical context in a drop down). These, plus the pop up based navigation mechanisms (Open Type, Quick Type Hierarchy, Quick Outline, etc.), have made navigating around in a large data space relatively easy in Eclipse. The only other value of the "Go Into" support was to make only a subset of the content viewable. The working set support in Eclipse can also be used to do this. Setting a working set that matches the content is both more flexible than "Go Into", and shows the "parent nodes" in the tree, which gives you the context you were looking for. Unfortunately, the workflow around setting/clearing working sets is still somewhat clunky. If we could fix *that*, I would argue that it's time to remove "Go Into" and the associated arrows.
Even when the workflow becomes less clunky having the "Go Into" feature is a great feature that is used constantly in our seismic processing application. We would miss it.
Thanks for the note, David. Can you describe a bit more about how it fits into your normal workflows?
We use the resource plugin to manage our seismic project files. Users work on various projects, sharing 100,000+ files, a terabyte of data per project and decades of CPU time. A project is broken down into segments that are represented by an IFolder. Each user works on an IFolder. They use the navigator "go into" feature to isolate themselves from others work. Extremely large projects could involve a few thousand IFolders and take 12 to 18 months to complete. Anything that helps reduce the number of files in the navigator view is greatly appreciated by our users. I would love to see the working sets API improved so our user community would use it more but even with that the "go into" is still a fast/easy way to isolate an IFolder. The "go into" feature is the Robertson screwdriver in our growing kit of resource management tools.
