Graphical Modeling Framework Runtime - Eclipse Modeling Project: A Domain-Specific Language Toolkit - page 454

providers that editors can use. DocumentProviders must implement the inter-
face org.eclipse.gmf.runtime.diagram.ui.editor.IDocumentPro-
vider . Editor inputs must be an instance of org.eclipse.ui.IEditor
Input .
Configuration markup:
<!ELEMENT extension (provider*)>
<!ELEMENT provider EMPTY>
<!ATTLIST provider
extensions CDATA #IMPLIED
inputTypes CDATA #IMPLIED
class CDATA #REQUIRED
id CDATA #REQUIRED
documentType CDATA
"org.eclipse.gmf.runtime.diagram.ui.editor.IDocument">
extensions —A comma-separated list of file extensions.
inputTypes —A comma-separated list of qualified editor input class names
that must implement org.eclipse.ui.IEditorInput .
class —The qualified name of the document provider class that must imple-
ment the interface org.eclipse.ui.texteditor.IDocumentProvider .
id —The unique ID of this provider.
documentType — org.eclipse.gmf.runtime.diagram.ui.editor.
IDocument
Examples:
This example registers org.eclipse.ui.examples.javaeditor.
JavaDocumentProvider as the default provider for files with the extension
.jav :
<extension
point="org.eclipse.gmf.runtime.diagram.ui.resources.
editor.documentProviders">
<provider
extensions=".jav"
class="org.eclipse.ui.examples.javaeditor.JavaDocumentProvider"
id="org.eclipse.ui.examples.javaeditor.JavaDocumentProvider">
</provider>
</extension>
This example registers org.eclipse.gmf.runtime.diagram.ui.
resources.editor.FileDocumentProvider as the default provider for all
editor inputs that are an instance of org.eclipse.ui.IStorageEditor
Input .