Bug 161050 - [EFS] Need to handle external and bad editors when using FileStoreInput
Summary: [EFS] Need to handle external and bad editors when using FileStoreInput
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks: 154126
  Show dependency tree
 
Reported: 2006-10-16 09:48 EDT by Michael Valenta CLA
Modified: 2021-10-28 14:08 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2006-10-16 09:48:16 EDT
In Team, we open editors on IStorage instances that represent remote files. We've had to tailor our open logic to:

1) Avoid opening an external editor since external editors require that the contents be available in a local file.

2) Catch the PartInitException and open a basic text editor if the default editor failed. We did this because, at the time, there were several internal editors that only really worked if the input was an IFile.

I thought it was worth mentioning these since they may apply to IFileStore based editor inputs as well.
Comment 1 Tod Creasey CLA 2006-12-07 14:30:33 EST
Moving to Krzysztof
Comment 2 Markus Keller CLA 2007-03-27 10:48:27 EDT
See also bug 50287.
Comment 3 Tod Creasey CLA 2007-05-07 10:47:10 EDT
Not for 3.3
Comment 4 Tod Creasey CLA 2008-01-28 09:52:19 EST
I'm not really sure where to start with this one. Dani or Michael could you give me some details as to where you think this work needs to happen?
Comment 5 Dani Megert CLA 2008-01-28 10:32:23 EST
Normally one should only use FileStoreEditorInput if there's an EFS (e.g. local or for IFiles) that can handle it. Not sure why you'd use a file store editor input for IStorage. Not sure whether this is more a asking for the same as in bug 50287.
Comment 6 Susan McCourt CLA 2009-07-09 19:02:45 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:31:03 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.
Comment 8 Eclipse Webmaster CLA 2019-09-06 15:37:11 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.
Comment 9 Eclipse Genie CLA 2021-10-28 14:08:52 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.