| sse.ui.extendedconfiguration [message #62575] |
Thu, 06 January 2005 23:40  |
Eclipse User |
|
|
|
Is there any documentation available for the WTP extension points, in
particular:
org.eclipse.wst.sse.ui.extendedconfiguration ?
I have created a multipage editor with an embedded StructuredTextEditorXML.
My editor opens fine on my file , but features like the outline view,
validation etc aren't there. I'm guessing that the above may have something
to do with it, although another possibility is that I need to register the
source editor (but I don't want it showing up as an Open With.. option.
Thanks for any tips.
- Richard
|
|
|
|
| Re: sse.ui.extendedconfiguration [message #63479 is a reply to message #62624] |
Sat, 08 January 2005 11:52  |
| Eclipse User |
|
|
|
Thanks. That was very helpful. Forwarding getAdaptor() enabled both the
outline view and the incremental validation (not sure why, in the latter
case), and the tip about the extension point schema and PDE Tools->Preview
Reference Document is great.
- Richard
"Nitin Dahyabhai" <nitind@us.ibm.com> wrote in message
news:crl80n$7uq$1@www.eclipse.org...
> Richard Rodseth wrote:
>> Is there any documentation available for the WTP extension points, in
>> particular:
>>
>> org.eclipse.wst.sse.ui.extendedconfiguration ?
>
> Many of our extension points have PDE schema files created for them with
> our goal to have complete coverage for 1.0. The PDE schema file for this
> extension point should be found in the SDK at
> eclipse/plugins/org.eclipse.wst.source_1.0.0/src/org.eclipse .wst.sse.ui_1.0.0/schema/extendedconfiguration.exsd
> and you can use the PDE to generate an HTML view of it.
>
> This extension point is used to make contributions reusable by more than
> just the editors known at development time. Typically when contributing
> to an editor you do so by using its declared editor ID. This means,
> however, to have all of the functionality with the same classes but a
> different ID you might have to duplicate large portions of a plugin.xml.
> Instead you'll see that org.eclipse.wst.xml.ui/plugin.xml specifies the
> text viewer configuration and other classes using the document's content
> type. The supporting code in the editor will always check the content type
> for these extensions, so regardless of where the StructuredTextEditorXML
> is used--standalone or embedded in any number of different multi page
> editors--you should see identical outline view behavior and etc. for XML
> files. The editor actually searches through an ordered list of IDs
> generated by
> org.eclipse.wst.sse.ui.extensions.ConfigurationPointCalculat or (including
> your editor's ID), so it's possible to override anything we've defined.
>
> The more likely cause for you not having an outline view at all is that
> your MultiPageEditorPart isn't forwarding it's getAdapter() requests to
> the StructuredTextEditorXML instance. The workbench will ask your
> MultiPageEditorPart instance for an IContentOutlinePage adapter to fill
> the Outline view and you should feel free to forward that and any other
> adapters you're not implementing yourself to the StructuredTextEditorXML
> class.
>
> If you *are* intending to use this extension point, though, be aware that
> it's been substantially altered in the upcoming WTP 1.0M3.
>
> --
> - Nitin
|
|
|
Powered by
FUDForum. Page generated in 0.06404 seconds
Home