Community
Participate
Working Groups
latest from HEAD The API classes in org.eclipse.ui.views.properties.tabbed should specify whether they are designed to be subclassed or not. Likewise, interfaces should specify whether clients may implement them. For example, IWorkbenchPart specifies: * This interface may be implemented directly. For convenience, a base * implementation is defined in <code>WorkbenchPart</code>. WorkbenchPart specifies: * <p> * This class is not intended to be subclassed by clients outside this * package; clients should instead subclass <code>ViewPart</code> or * <code>EditorPart</code>. * </p> EditorPart specifies: * This class should be subclassed by clients wishing to define new editors. and other details like: * Subclasses must implement the following methods: * <ul> * <li><code>IEditorPart.init</code> - to initialize editor when assigned its site</li> * <li><code>IWorkbenchPart.createPartControl</code> - to create the editor's controls </li> * <li><code>IWorkbenchPart.setFocus</code> - to accept focus</li> * <li><code>IEditorPart.isDirty</code> - to decide whether a significant change has * occurred</li> * <li><code>IEditorPart.doSave</code> - to save contents of editor</li> * <li><code>IEditorPart.doSaveAs</code> - to save contents of editor</li> * <li><code>IEditorPart.isSaveAsAllowed</code> - to control Save As</li> * </ul> * </p> * <p> * Subclasses may extend or reimplement the following methods as required: * <ul> * <li><code>IExecutableExtension.setInitializationData</code> - extend to provide additional * initialization when editor extension is instantiated</li> * <li><code>IWorkbenchPart.dispose</code> - extend to provide additional cleanup</li> * <li><code>IAdaptable.getAdapter</code> - reimplement to make the editor * adaptable</li> * </ul> If no restrictions are specified, then it implies that the client may use the type in any way (call, extend, implement), which may restrict the kinds of API changes that can be made in the future.
Added the appropriate comments where required.