Package oracle.jdeveloper.uieditor

Contains classes that allow addins access to the UIEditor integration objects.

See:
Description

Interface Summary

ModelFactory

ModelFactory describes the API by which an integrator may extend the UIEditor to provide custom design surfaces, known as UIEditorCanvas, which may be used by the user to manipulate an associated custom CmtModel implementation.

Class Summary

AbstractCanvas	AbstractCanvas provides an implementation of UIEditorCanvas based upon Explorer which provides a default implementation for all UIEditorCanvas behavior.
AbstractCanvasController	AbstractCanvasController provides an implementation of Controller based upon BaseController.
AbstractFactory	AbstractFactory provides an implementation of ModelFactory.
CanvasKeyStrokeContext	CanvasKeyStrokeContext is a KeyStrokeContext based upon XmlKeyStrokeContext and customized for ModelFactory implementations.
UIEditor	Editor implementation whose visuals depict the GUI declared in a JavaSourceNode instance.
UIEditorCanvas	UIEditorCanvas represents a design canvas for hosting within the UIEditor.
UIEditorHookHandler	Process the uieditor element which may be part of a JDeveloper extension manifest .
UIEditorLogPage	A LogPage implementation specialized for display of CmtMessage instances from one or more CmtComponent objects.
UIEditorOptions	UIEditorOptions describes the customizations made available to the user.
UIEditorPrintFactory	DocumentPrintFactory for use by the UIEditor.
UIManager	The UIManager provides the API necessary for the UIEditor to work in cooperation with integrator extensions.

Package oracle.jdeveloper.uieditor Description

Contains classes that allow addins access to the UIEditor integration objects.

The UIEditor subsystem involves four types of entities: editors, canvases, factories and a manager. An editor is the host (see the UIEditor class) in which a canvas (see UIEditorCanvas) is displayed. The canvas is produced by a factory (see ModelFactory) and depicts a graphical representation of a factory specific model based upon the source file being edited.

For example; a factory might be registered that generates a model of only the non menu GUI objects of a source file and can produce on demand a canvas capable of displaying that model. Additionally, a second factory might be registered that generates a model of only the menu GUI objects of that same source file and can produce a canvas capable of displaying that model. The user may then toggle between the two canvases within a single editor based upon which model they wish to view. Addin writers may register their factory implementations with the manager (see UIManager).