Bug 134317 - [RCP] Add OLE Editor support to RCP
Summary: [RCP] Add OLE Editor support to RCP
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2006-03-31 15:50 EST by Eddie Galvez CLA
Modified: 2019-09-06 16:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eddie Galvez CLA 2006-03-31 15:50:07 EST
I think I got the Component right (since I see that the OLE Editor class is org.eclipse.swt.ole.win32.OLE)...

I would like to submit a feature request to see the OLE editor extracted away from the ui.ide plugin and appear as a supported RCP component.

What troubles me is that RCP has a lot of ole code and checks that go very deep before bailing out due to not having the ui.ide bundle loaded. This results in RCP apps that will display "no in-place editor support" even though the IEditorRegistry will return true to isSystemInPlaceEditorAvailable(String), it seems.
Comment 1 Eric Moffatt CLA 2006-04-04 10:19:57 EDT
Boris, I'm actually more concerned that we may be reporting the editor as 'available' when it won't (might not?) work...
Comment 2 Kevin McGuire CLA 2007-06-22 10:24:17 EDT
Is this still a problem in 3.3 RC4?

I have a little RCP app that has IResources but does not include an IDE plugins.  I am able to open a Word file in-place (OLE).  My app *does* have some code copied from the IDE WorkbenchAdvisor but that's it.

Mind you I thought I saw the "no in-place editor support" error recently but wasn't sure how it came about.
Comment 3 Boris Bokowski CLA 2009-11-26 16:15:26 EST
Prakash is now responsible for watching bugs in the [RCP] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:12:41 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.