| Summary: | RFE: tree view for java packages in Java browsing view [package explorer] [browsing] | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | David Buttler <buttler1> |
| Component: | UI | Assignee: | Erich Gamma <erich_gamma> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | mlq.eclipse, public, udekel |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
David Buttler
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. *** 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 |