From Optflux
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 128: | Line 128: | ||
#* A plugin can use the classes from other plugin only if a dependency from the first to the second has been defined. | #* A plugin can use the classes from other plugin only if a dependency from the first to the second has been defined. | ||
#* AIBench contains two basic plugins: the '''CORE''' and the '''WORKBENCH''', communicated internally by an extension point (the top one in the last figure), but this is out of the scope of this document. | #* AIBench contains two basic plugins: the '''CORE''' and the '''WORKBENCH''', communicated internally by an extension point (the top one in the last figure), but this is out of the scope of this document. | ||
| − | # Also the CORE implements the extensible AIBench Operation Model by the definition of an extension point called | + | ---- |
| + | # Also the CORE implements the extensible AIBench Operation Model by the definition of an extension point called “AIBench.core.operation-definition”. | ||
#*'''To add Operations to AIBench/OptFlux''', you have to put them in a plugin and connect it to this extension point. There is not any required interface to implement. | #*'''To add Operations to AIBench/OptFlux''', you have to put them in a plugin and connect it to this extension point. There is not any required interface to implement. | ||
| − | # The WORKBENCH implements the Workbench user interface and also defines an extension point called | + | ---- |
| + | # The WORKBENCH implements the Workbench user interface and also defines an extension point called “AIBench.core.workbench.view”. To register a view component associated with a Data-type, you have to put your component in a plugin and connect it to this extension point. There is not any required interface to implement. | ||
#*The user Datatypes have to be placed inside a plugin, but this plugin doesn't need to be connected to any extension point. (Please note that if some of your Operations use these Datatypes and reside in other plugins, they must depend on this plugin). | #*The user Datatypes have to be placed inside a plugin, but this plugin doesn't need to be connected to any extension point. (Please note that if some of your Operations use these Datatypes and reside in other plugins, they must depend on this plugin). | ||
| + | ---- | ||
# You can put your Operations, Views and Datatypes in one, two or more separated plug-ins, based on your own design decision. The only rules that have to be followed are: | # You can put your Operations, Views and Datatypes in one, two or more separated plug-ins, based on your own design decision. The only rules that have to be followed are: | ||
#* If there are Operations and/or Views in a plugin, this plugin must be connected to the properly extension points as it was explained before. | #* If there are Operations and/or Views in a plugin, this plugin must be connected to the properly extension points as it was explained before. | ||