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 "STP/XEF XML Framework"
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* generation of test WS requests | * generation of test WS requests | ||
* editing XML-based configuration, descriptors | * editing XML-based configuration, descriptors | ||
| − | * etc | + | * administration of XML-based entities |
| + | * etc | ||
This proposal also will be very helpful to redesign Policy Editor regarding UI Walkthrough [[http://wiki.eclipse.org/10122008PolicyEditor Policy Editor UI Walkthrough]]. | This proposal also will be very helpful to redesign Policy Editor regarding UI Walkthrough [[http://wiki.eclipse.org/10122008PolicyEditor Policy Editor UI Walkthrough]]. | ||
<h1>Using of XEF Framework</h1> | <h1>Using of XEF Framework</h1> | ||
| − | XEF Framework provides well defined public | + | XEF Framework provides well defined public interfaces. |
| + | Interfaces are defined for the tree following tiers: | ||
| + | * Model (low) | ||
| + | * Rendering (middle) | ||
| + | * Editor (high) | ||
| + | Components and applications will use XEF Framework in different contexts and scenarios via these interfaces. | ||
| − | [[Image: | + | [[Image:Using_XEF_Framework-1.JPG]] |
| − | <h1> | + | <h1>Three tier interfaces</h1> |
| − | + | 1. Model API | |
| − | [[Image: | + | This is a lowest level to access XEF Framework. This interface provides access to XMLModelFactory and XMLInstanceElement XEF model classes. Interface is designed to build and control XEF model on the low level. |
| + | |||
| + | [[Image:XEF_Model_ClassDiagram.JPG]] | ||
| + | |||
| + | 2. Rendering API | ||
| + | |||
| + | The second level API (Rendering) allows to display and process GUI representation of XML schema on any composite. This API could be used for schema representation on views, dialogs, preference pages. | ||
| + | Draft proposal rendering API is represented bellow. The IXEFFramework is rendering interface of the framework. IXEFCallback should be implemented by framework consumer to receive notifications. | ||
| + | |||
| + | [[Image:XEF_Render_ClassDiagram-1.JPG]] | ||
| + | |||
| + | 3. Editor API | ||
| + | |||
| + | This API provides the possibility to use XEF as normal Eclipse Editor. Using extension point user can | ||
| + | open editor, load files, receive notifications. | ||
| + | |||
| + | Typical using of XEF Editor in this case is: | ||
| + | |||
| + | String XEF_ID = "org.eclipse.stp.ui.xef.editor.XefEditor"; | ||
| + | PolicyDetailEditorInput edInput = new PolicyDetailEditorInput(text, streamIn, project, callback); | ||
| + | IWorkbench workbench = PlatformUI.getWorkbench(); | ||
| + | IWorkbenchWindow activeWindow = workbench.getActiveWorkbenchWindow(); | ||
| + | IWorkbenchPage workbenchPage = activeWindow.getActivePage(); | ||
| + | IEditorPart part = IDE.openEditor(workbenchPage, edInput, XEF_ID); | ||
| + | |||
| + | <h1>XML Schemas</h1> | ||
| + | |||
| + | XML Schemas for XEF Framework can be provided by different ways: | ||
| + | * Explicitly as files | ||
| + | * Custom Schema Catalogs | ||
| + | * WTP Schema Catalog | ||
| + | |||
| + | In case of using WTP Schema Catalog it is possible to register it via extension point. After it all schemas will be automatically available in XEF Framework model. | ||
|} | |} | ||
Latest revision as of 18:17, 24 January 2009
ProposalThe main idea of this proposal is to expose XEF editor in more generic way: as XML framework. GUI representation of XML schema is very common task, required by the number of applications and Eclipse projects. So intention is to make XEF usable not only in context of policy editor, but also for many another scenarios like:
This proposal also will be very helpful to redesign Policy Editor regarding UI Walkthrough [Policy Editor UI Walkthrough]. Using of XEF FrameworkXEF Framework provides well defined public interfaces. Interfaces are defined for the tree following tiers:
Components and applications will use XEF Framework in different contexts and scenarios via these interfaces.
Three tier interfaces1. Model API This is a lowest level to access XEF Framework. This interface provides access to XMLModelFactory and XMLInstanceElement XEF model classes. Interface is designed to build and control XEF model on the low level.
2. Rendering API The second level API (Rendering) allows to display and process GUI representation of XML schema on any composite. This API could be used for schema representation on views, dialogs, preference pages. Draft proposal rendering API is represented bellow. The IXEFFramework is rendering interface of the framework. IXEFCallback should be implemented by framework consumer to receive notifications.
3. Editor API This API provides the possibility to use XEF as normal Eclipse Editor. Using extension point user can open editor, load files, receive notifications. Typical using of XEF Editor in this case is: String XEF_ID = "org.eclipse.stp.ui.xef.editor.XefEditor"; PolicyDetailEditorInput edInput = new PolicyDetailEditorInput(text, streamIn, project, callback); IWorkbench workbench = PlatformUI.getWorkbench(); IWorkbenchWindow activeWindow = workbench.getActiveWorkbenchWindow(); IWorkbenchPage workbenchPage = activeWindow.getActivePage(); IEditorPart part = IDE.openEditor(workbenchPage, edInput, XEF_ID); XML SchemasXML Schemas for XEF Framework can be provided by different ways:
In case of using WTP Schema Catalog it is possible to register it via extension point. After it all schemas will be automatically available in XEF Framework model. |
