Eclipse Community Forums: Rich Client Platform (RCP) » using an existing plugin in an rcp app

Home » Eclipse Projects » Rich Client Platform (RCP) » using an existing plugin in an rcp app

using an existing plugin in an rcp app [message #393921]

Mon, 15 November 2004 13:04

Eclipse User

Hi,
I have a newbie rcp question. I am writing an rcp app for editing a
specific type of file that we have called a .ped file. with this file we
have .xml file assoicated with it too. we would like to edit that also
with an all ready existing open source xml plugin. It is possible to fire
that plugin when the user clicks on an xml? does this have to be done
programmically or through plugin settings?

-Tony

Re: using an existing plugin in an rcp app [message #396461 is a reply to message #393921]

Fri, 26 November 2004 16:23

Eclipse User

The org.eclipse.ui.editors extension point allows you to specify the
file extensions relevant for that editor.
See
http://help.eclipse.org/help30/topic/org.eclipse.platform.do c.isv/guide/workbench_basicext_editors.htm

However, there's currently no way of adding file extensions to an
existing editor.

Is this what you mean? If so, please enter a feature request against
Platform UI.
https://bugs.eclipse.org/bugs/

Anthony Perritano wrote:
> Hi,
> I have a newbie rcp question. I am writing an rcp app for editing a
> specific type of file that we have called a .ped file. with this file we
> have .xml file assoicated with it too. we would like to edit that also
> with an all ready existing open source xml plugin. It is possible to
> fire that plugin when the user clicks on an xml? does this have to be
> done programmically or through plugin settings?
>
> -Tony
>

Re: using an existing plugin in an rcp app [message #397912 is a reply to message #396461]

Thu, 02 December 2004 12:12

Eclipse User

Nick Edgar wrote:
> However, there's currently no way of adding file extensions to an
> existing editor.

Correction, there is no *public* way (I didn't say that:))

Modification of the Editor Registry is not exposed through interfaces
but *is publicly exposed* through implementations. Hope, this was not
done intentionally against the open source nature of the Eclipse.

I'd definitely file an RFE *Editor Registry: expose the following from
the internal implementation classes through the corresponding public
interfaces (with signature republicization:))*:

from package org.eclipse.ui.internal.registry:
- EditorRegistry.setFileEditorMappings(FileEditorMapping[])
- FileEditorMapping.addEditor(EditorDescriptor)
- new FileEditorMapping(String)

into package org.eclipse.ui.registry:
- IEditorRegistry.setFileEditorMappings(IFileEditorMapping[])
- IFileEditorMapping.addEditor(IEditorDescriptor)
- IFileEditorMapping.F.newMapping(String)

--
10x,
Sam Mesh

Previous Topic:	PopUp Menu
Next Topic:	Error: Unable to recreate perspective

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Nov 08 05:44:05 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter