Bug 50268

Summary:	[EditorMgmt] [RCP] Make EditorHistory API public.
Product:	[Eclipse Project] Platform	Reporter:	Eugene Ostroukhov <evgeniyos>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	api, helpwanted
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Eugene Ostroukhov

2004-01-20 09:38:07 EST

In the Eclipse 2.1.2 and 3.0M6 EditorHistory and supporting classes are in the 
internal package - this makes it harder to implement other presentation for 
the recent files. I.e. in our application I want to display recent files in a 
tree but to do this I have to work with internal framework classes.

Comment 1 Eugene Ostroukhov

2004-01-21 09:26:54 EST

Just one more issue - it uses IPath for the tasks like parsing the string - in 
my application my EditorInput is disconnected from the Eclipse resource 
framework - so such things just add unneeded dependency.

Comment 2 Nick Edgar

2004-01-21 09:42:02 EST

IPath comes from org.eclipse.core.runtime, not org.eclipse.core.resources.
org.eclipse.ui.workbench has no dependencies on org.eclipse.core.resources in 
3.0 (as of M5).

Note that the current presentation can be reused via 
ContributionItemFactory.REOPEN_EDITORS, but you're correct: if you want to roll 
your own presentation, new API would be needed.

These APIs are especially important for people building their own RCP apps.

Comment 3 Nick Edgar

2004-03-07 23:21:13 EST

Doesn't look like this is going to make the cut for 3.0.

Comment 4 Nick Edgar

2004-05-07 11:49:48 EDT

Not for 3.0.

Comment 5 Nick Edgar

2006-03-15 11:24:12 EST

Reassigning bugs in component areas that are changing ownership.

Comment 6 Boris Bokowski

2009-11-17 13:01:29 EST

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

Comment 7 Eclipse Webmaster

2019-09-06 16:04:16 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.