Community
Participate
Working Groups
It would be really nice to have a tree view of packages and of classes in the java browsing view. I thought this was one of the coolest features of the VAJ view -- it made it easy to hide things that wasn't working on so I could focus in on the context I was involved with. Any idea how difficult this would be to implement?
By tree view you mean showing org.eclipse.jdt as: org eclipse jdt This is doable but we don't plan to do it for 2.0.
I understand that this may not be a top priority for 2.0 Out of curiosity, is it more difficult than replacing a list view with a tree view ? Obviously there is some more interesting things going on since each package would have to be split on the "." and either shadow packages added for non-existant packages or some nodes would be collapsed (e.g. if there was the package org.eclispe.jdt, the packages org and org.eclipse may not have any classes in them. The tree view would either be as indicated above - org |--- eclipse |--- jdt The alternative would be to collapse the tree for these packages, so it would look like the following: - org.eclipse.jdt but if another package were added (org.eclipse.jdt.core) it would look like: - org.eclipse.jdt |--- core VAJ for java did it the first way. Packages that didn't exist were grayed out.
This is a duplicate of bug 6454, I believe. Jon
*** Bug 21873 has been marked as a duplicate of this bug. ***
*** Bug 21285 has been marked as a duplicate of this bug. ***
reopen to mark as duplicate
*** This bug has been marked as a duplicate of 6454 ***