Bug 63805 - [EditorMgmt] Link with Editor filters
Summary: [EditorMgmt] Link with Editor filters
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement with 4 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-25 05:39 EDT by Gabriele Garuglieri CLA
Modified: 2013-12-13 09:54 EST (History)
1 user (show)

See Also:


Attachments
Screen shot of expanded package explorer. (22.55 KB, image/gif)
2006-12-17 01:18 EST, Dan Phifer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriele Garuglieri CLA 2004-05-25 05:39:34 EDT
Sometimes it may be usefull to peek at the source of some classes from a jar,
just think to rt.jar), using Ctrl-click.
The problem is that if "Link with editor" option is selected, the whole jar is
exploded in "Package Explorer", and that is annoying when you you just wanted to
have a rapid look and you are not interested to the class context.

"Link with editor" should implement a filter to selectively enable it on source
folders, excluding all the jars, or enabling them selectively with something
similar to "Step filters" of Debug view.
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:18 EDT
Moving Dougs bugs
Comment 2 Jason Bennett CLA 2006-07-24 20:22:27 EDT
This would be a very nice feature when debugging; I find it very annoying to have the entire JRE class list expand because I stepped into java.lang.
Comment 3 Dan Phifer CLA 2006-12-17 01:18:57 EST
Created attachment 55828 [details]
Screen shot of expanded package explorer.

The only package that should be expanded is java.lang
Comment 4 Dan Phifer CLA 2006-12-17 01:21:23 EST
I agree.  When rt.jar gets put into the context, the tree is exapanded so that all packages (but not their contents) are visible.  Not only does this take time, but there are probably more packages in rt.jar than there are classes in any one of my plug-ins, which means mylar is, in this case, making use of the project explorer more difficult.  I'm now in the habit of turning off "Focus on Active Task" on the Package Explorer (but whenever I activate a new task or restart eclipse it comes back on, which I will file as a bug if it isn't already).

Also, this problem occurs when "Focus on Active Task" is selected, whether or not "Link with Editor" is selected.

I can think of two solutions:
1) Use the Resource Monitoring Exclusions (or another list defined in the same way) to exclude packages from view in the Package Explorer
2) When I view java.lang.Object (with Hierarchical Presentation), the full package tree is shown, rather than just java -> lang -> Object.  Limiting this to only the parent packages of the selected class would greatly reduce the amount of clutter
Comment 5 Dan Phifer CLA 2006-12-20 05:04:59 EST
Sorry to confuse the issue.  I think the situation I described in comment 3 and 4 is actually fixed in Bug 148759.  I'm not sure if that fix applies to this bug as well, but it seems like the two might be related -- the choice of the word "exploding" in the initial post makes me think its the same issue.  
Comment 6 Susan McCourt CLA 2009-07-09 19:05:01 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 7 Boris Bokowski CLA 2009-11-17 13:00:17 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 8 Sharon Dagan CLA 2013-12-09 17:21:04 EST
+1
I too find it useful to have a filter associated with the "Link with editor" feature, as per the original description of this bug.