| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" |
| "http://www.w3.org/TR/html4/loose.dtd"> |
| <html> |
| <head> |
| <meta |
| http-equiv="Content-Type" |
| content="text/html; charset=iso-8859-1"> |
| |
| <title>org.eclipse.wst.common.frameworks</title> |
| |
| <link |
| rel="stylesheet" |
| type="text/css" |
| href="../sources/formate.css"> |
| </head> |
| |
| <body> |
| |
| <h1 class="descriptions">org.eclipse.wst.common.frameworks</h1> |
| <p class="schema">Extension Points</p> |
| <table |
| width="90%" |
| border="0" |
| cellspacing="0"> |
| <tr> |
| <td width="30"> </td> |
| <td> |
| <ul> |
| <li>ExtendableOperation</li> |
| </ul> |
| <ul> |
| <li>OperationExtension</li> |
| </ul> |
| <ul> |
| <li>functionGroup</li> |
| </ul> |
| <p>A functionGroup provides a grouping of related function that can |
| be contributed to the tools. For example, a third party component |
| may want to contribute actions, editor pages, edit model resources, |
| and many other functions specific to a given product. By associating |
| all these functions with a group id, a mechanism is exposed for |
| users to selectively enable and disable baskets of function. |
| Extension points that allow for a "groupID" attribute generally will |
| hide those functions when the group id is disabled.</p> |
| <ul> |
| <li>WTPActivityBridgeHelper</li> |
| </ul> |
| <ul> |
| <li>validationSelectionHandler</li> |
| </ul> |
| <ul> |
| <li>DataModelProviderExtension</li> |
| </ul> |
| </td> |
| </tr> |
| </table> |
| <p class="schema">Used Extensions</p> |
| <table |
| width="90%" |
| border="0" |
| cellspacing="0"> |
| <tr> |
| <td width="30"> </td> |
| <td>org.eclipse.jem.util.uiContextSensitiveClass</td> |
| </tr> |
| </table> |
| <p class="schema">Dependencies (Required Plugins)</p> |
| <table |
| width="90%" |
| border="0" |
| cellspacing="0"> |
| <tr> |
| <td width="30"> </td> |
| <td>org.eclipse.core.resources<br> |
| org.eclipse.core.runtime<br> |
| org.eclipse.core.commands<br> |
| org.eclipse.jem.util</td> |
| </tr> |
| </table> |
| |
| |
| <p>Version 0.7.0</p> |
| <p class="ueberschrift">Validation Framework</p> |
| <ul> |
| <li>Component in WST |
| <ul> |
| <li>Validation</li> |
| </ul> |
| </li> |
| <li>Functional Overview |
| <ul> |
| <li>The framework provides a means for validators built using the |
| framework to validate resources in a project manually or |
| automatically.</li> |
| </ul> |
| </li> |
| <li>Links |
| <ul> |
| <li>http://www.eclipse.org/webtools/wst/components/validation/ValidationOverview.html |
| </li> |
| </ul> |
| </li> |
| <li>API |
| <ul> |
| <li>Currently there are no defined API in the framework and have |
| been defined as provisional internal API for WTP 0.7 release.</li> |
| <li>A fully defined API for the framework is planned for WTP 1.0</li> |
| </ul> |
| </li> |
| <li>Future Enhancements |
| <ul> |
| <li>The enhancements are geared towards performance improvements on |
| running validators built using the framework |
| <ul> |
| <li>Provide mechanism for individual validators to run |
| asynchronously</li> |
| <li>Change Global and Project level validation preferences to give |
| users more control to turn validators on and off on a build and |
| manual validation.</li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| <li>Test Scenarios |
| <ul> |
| <li>The overall framework test scenario can be found at</li> |
| <li><a |
| href="http://www.eclipse.org/webtools/wst/components/validation/scenarios/validation_framework_testplan.html ">http://www.eclipse.org/webtools/wst/components/validation/scenarios/validation_framework_testplan.html |
| </a></li> |
| </ul> |
| </li> |
| </ul> |
| <p class="ueberschrift">Datamodel Framework</p> |
| <ul> |
| <li>Mechanism for tracking related data for operations & wizards |
| (coming soon) |
| <ul> |
| <li>Properties |
| <ul> |
| <li>get/set</li> |
| <li>default/valid values</li> |
| <li>validation/enablement</li> |
| </ul> |
| </li> |
| <li>Know how to run themselves using operations</li> |
| <li>Nesting/Extendable</li> |
| <li>Wizards (coming soon) |
| <ul> |
| <li>DataModels know how to build their wizards</li> |
| <li>Easy to build wizards on top of wizards</li> |
| <li>Extendable</li> |
| </ul> |
| </li> |
| </ul> |
| </li> |
| </ul> |
| <p class="ueberschrift">Enviroment Framework</p> |
| <ul> |
| <li>For writing components for multiple environments. Eg: |
| <ul> |
| <li>Eclipse GUI</li> |
| <li>Eclipse headless</li> |
| <li>Java command line</li> |
| <li>Ant task / JUnit / Batch</li> |
| <li>Web service</li> |
| </ul> |
| </li> |
| <li>Aspects |
| <ul> |
| <li>Progress monitoring</li> |
| <li>Status handling</li> |
| <li>URI-based resource access</li> |
| <li>Command stack management</li> |
| </ul> |
| </li> |
| <li>Integrates with ?the? command framework (today there are three!)</li> |
| <li>Eclipse GUI Environment |
| <ul> |
| <li>Dynamic Wizard Framework for highly non-deterministic wizards</li> |
| <li>Complete separation from command-pattern based engine code</li> |
| </ul> |
| </li> |
| <li>Convergence TBD with DataModel, IUndoableOperation, etc.</li> |
| </ul> |
| <br> |
| <br> |
| </body> |
| </html> |
