Difference between revisions of "Extension Guide"
| Line 48: | Line 48: | ||
* UI Constants | * UI Constants | ||
** [[UIMenuConstants]] | ** [[UIMenuConstants]] | ||
| + | * [[RPCService]] | ||
* [[Widget library]] | * [[Widget library]] | ||
* Best practice | * Best practice | ||
Revision as of 11:44, 8 December 2010
OpenKM plugin extensions makes more easilly to extends OpenKM end user interface encapsulating plugin code and making it rehusable between OpenKM versions.
The OpenKM plugin extension architecture is based on:
- Extensions
- Events
- Handlers
- Comunicators
Extensions are available widget definitions that allows to make extensible panels and widgets ( for example adding new tab panel on tab document )
Events are a collection of events that OpenKM UI fires each time any changes happens ( for example when is added new keyword in tab document is fired event HasDocumentEvent.KEYWORD_ADDED)
Handlers are a collection of metods called internally by OpenKM. Handlers must be implemented into your extensions in order to collecting OpenKM fired events. With each extension you make can have one or several handlers, that are automatically registered by OpenKM on loading process. OpenKM internally fire events to each declared handler.
Comunicators are a collection of methods avaliable as OpenKM Comunitate API to accessing transparently with some internal UI values. There are several Comunitators, for example with GeneralComunicator can accessing to some general actions like refreshing UI as GeneralComunicator.refreshUI(). OpenKM Communicators API has read and write methods to interact with internal OpenKM UI objects.
 |
Create OpenKM plugin extension it's easy but you need some java knowledge and pay special attention at Google Web ToolKit API that's used to build OpenKM UI. http://code.google.com/webtoolkit/ |
- HelloWorld Example
- Enable example extensions
- Extension
- Handlers
- Comunicators
- UI Constants
- RPCService
- Widget library
- Best practice
