Bug 88969

Summary:	[EditorMgmt] Can assign the icon to different kind of files
Product:	[Eclipse Project] Platform	Reporter:	Liu Feifei <liuff>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse
Version:	3.0.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Liu Feifei

2005-03-24 03:16:27 EST

Now Eclipse can only show icons according file types(like *.java, *.xml),
but when I developing Struts, I need to identify xxxAction, xxxVO, xxxPO....
these files are all *.java and are assigned the same icon. So It is different 
to tell which is the one I really want, especially when I open more than 4 file 
and the Editor's Tab title only shows the first few characters while they are 
same, such as EmployeeVO, EmployeeAction, EmployeePO.
So, I think it will be a good feature to be able to assing different icon 
assording to file name, e.g. I can assign icon_1 to *Action.java, assign icon_2 
to *Form.java, and so on.

Comment 1 Douglas Pollock

2005-03-28 11:03:18 EST

Is this now possible?

Comment 2 Kim Horne

2005-03-28 11:13:32 EST

There is no easy way to do this.  There are two heavy weight programatic ways
that I can think of, however...

You could subtype the java content type for each criteria, and then create new
editors (that are really just java editors) bound to each content type.  Each
would have it's own icon.  

You could create a decorator that checks the file for certain methods and
decorates the label appropriately.

The second solution would be easiest.

Comment 3 Michael Van Meekeren

2006-04-21 13:18:59 EDT

Moving Dougs bugs

Comment 4 Susan McCourt

2009-07-09 19:07:02 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 5 Boris Bokowski

2009-11-17 13:05:38 EST

Remy is now responsible for watching the [EditorMgmt] component area.

Comment 6 Eclipse Webmaster

2019-09-06 16:12:04 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.