Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "FAQ How do I make an editor that contains another editor?"
| Line 1: | Line 1: | ||
| − | In its most abstract sense, an editor is simply a container for arbitrary SWT | + | In its most abstract sense, an editor is simply a container for arbitrary SWT controls. As such, an editor can contain views, editors, wizards, and any other visual control. In practice, many of these types of controls don't make sense in the context of an editor. However, an editor is commonly composed of several pages, some of which may also be used as stand-alone editors. The most common example is an editor that provides a rendered WYSIWYG (what you see is what you get) page and a source page that shows raw text. The PDE plug-in Manifest Editor, implemented by the <tt>ManifestEditor</tt> class in the PDE UI plug-in, is such an editor. The platform provides infrastructure for this common editor type in the <tt>MultiPageEditorPart</tt> class. |
| − | controls. As such, an editor can contain views, editors, wizards, | + | |
| − | and any other visual control. In practice, many of these types of controls | + | |
| − | don | + | |
| − | editor is commonly composed of several pages, some of which may also be | + | |
| − | used as stand-alone editors. The most common example is an editor that | + | |
| − | provides a rendered WYSIWYG (what you see is what you get) page | + | |
| − | and a source page that shows raw text. The PDE plug-in | + | |
| − | Manifest Editor, implemented by the <tt>ManifestEditor</tt> class | + | |
| − | in the PDE UI plug-in, is such an editor. | + | |
| − | The platform provides infrastructure for this common editor type | + | |
| − | in the <tt>MultiPageEditorPart</tt> class. | + | |
| + | Creating a subclass of <tt>MultiPageEditorPart</tt> requires that you implement many of the same methods as you would for a standard editor. The main difference is that instead of implementing <tt>createPartControl</tt>, you must implement <tt>createPages</tt>. In this method, you must create the controls for each page within the editor. These pages can be either standard editor parts or arbitrary SWT controls. The nested editors don’t need to know anything about their container; from their point of view they are simply standard editors. | ||
| − | + | Your subclass of <tt>MultiPageEditorPart</tt> isn’t required to do much beyond creating the initial set of pages. The superclass will take care of implementing the presentation for displaying the pages and for allowing the user to switch pages. If necessary, you can programmatically add or remove pages at any time by calling <tt>addPage</tt> or <tt>removePage</tt>. You can also programmatically switch pages by using <tt>setActivePage</tt> and respond to page changes by overriding <tt>pageChange</tt>. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | can | + | |
| − | + | ||
| − | + | ||
| − | + | The simplest way to get going with a multi-page editor is to edit your <tt>plugin.xml</tt> with the Manifest Editor. Select the '''Extensions''' tab, click on '''Add...''', select '''org.eclipse.ui.editors''' in the extension point list, and choose '''Multi-page Editor''' from the list of available templates. This will add all the required pieces for a basic multi-page editor to your plug-in. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | The simplest way to get going with a multi-page editor is to edit | + | |
| − | your <tt>plugin.xml</tt> with the Manifest Editor. Select the '''Extensions''' | + | |
| − | tab, click on '''Add...''', select '''org.eclipse.ui.editors''' | + | |
| − | in the extension point list, and choose '''Multi-page Editor''' | + | |
| − | from the list of available templates. This will add all the required pieces | + | |
| − | for a basic multi-page editor to your plug-in. | + | |
== See Also: == | == See Also: == | ||
| − | + | *[[FAQ How do I create a form-based editor, such as the plug-in Manifest Editor?]] | |
| − | [[ | + | |
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | <hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | ||
Latest revision as of 21:50, 8 May 2007
In its most abstract sense, an editor is simply a container for arbitrary SWT controls. As such, an editor can contain views, editors, wizards, and any other visual control. In practice, many of these types of controls don't make sense in the context of an editor. However, an editor is commonly composed of several pages, some of which may also be used as stand-alone editors. The most common example is an editor that provides a rendered WYSIWYG (what you see is what you get) page and a source page that shows raw text. The PDE plug-in Manifest Editor, implemented by the ManifestEditor class in the PDE UI plug-in, is such an editor. The platform provides infrastructure for this common editor type in the MultiPageEditorPart class.
Creating a subclass of MultiPageEditorPart requires that you implement many of the same methods as you would for a standard editor. The main difference is that instead of implementing createPartControl, you must implement createPages. In this method, you must create the controls for each page within the editor. These pages can be either standard editor parts or arbitrary SWT controls. The nested editors don’t need to know anything about their container; from their point of view they are simply standard editors.
Your subclass of MultiPageEditorPart isn’t required to do much beyond creating the initial set of pages. The superclass will take care of implementing the presentation for displaying the pages and for allowing the user to switch pages. If necessary, you can programmatically add or remove pages at any time by calling addPage or removePage. You can also programmatically switch pages by using setActivePage and respond to page changes by overriding pageChange.
The simplest way to get going with a multi-page editor is to edit your plugin.xml with the Manifest Editor. Select the Extensions tab, click on Add..., select org.eclipse.ui.editors in the extension point list, and choose Multi-page Editor from the list of available templates. This will add all the required pieces for a basic multi-page editor to your plug-in.
See Also:
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.