Difference between revisions of "Developers"
| Line 8: | Line 8: | ||
* <u>'''geWorkbench plugins'''</u>: this portion of the source tree contains the code for the various application plugin components (sample code for creating a simple plugin can be found [[A_Simple_Plugin |here]]). | * <u>'''geWorkbench plugins'''</u>: this portion of the source tree contains the code for the various application plugin components (sample code for creating a simple plugin can be found [[A_Simple_Plugin |here]]). | ||
| − | + | There are no restrictions on who can develop a new component for geWorkbench. You can work against the development version or a release version of the geWorkbench core. To contribute your component to geWorkbench code, you need write access to the subversion server. Please contact us for the procedure. | |
| + | Contributions to the geWorkbench core packages are more controlled in order to avoid changes that may adversely affect large numbers of plugins. | ||
Revision as of 11:17, 22 March 2010
|
Developers Home | A Simple Plugin | geWorkbench Archive Files | Collaborative Development | Design Documentation | Javadocs | gForge Page | Report Defects |
geWorkbench is an open source Java-based platform and contributions by members of the community are welcome and encouraged. The latest code under development can be found at NCI's subversion server, https://ncisvn.nci.nih.gov/svn/geworkbench/. Anonymous read access is supported for all the code.
Development in geWorkbench takes place along 2 parallel axes:
- geWorkbench core: this portion of the code includes mainly 2 groups of packages: engine, which implements services related to the geWorkbench component architecture framework (e.g., plugin instantiation and visual layout, message delivery, component registry management, etc); and, bison (Biomedical Informatics Structured ONtology) which contains the definition of the bioinformatics data types which form the basis of communication between the geWorkbench plugins.
- geWorkbench plugins: this portion of the source tree contains the code for the various application plugin components (sample code for creating a simple plugin can be found here).
There are no restrictions on who can develop a new component for geWorkbench. You can work against the development version or a release version of the geWorkbench core. To contribute your component to geWorkbench code, you need write access to the subversion server. Please contact us for the procedure. Contributions to the geWorkbench core packages are more controlled in order to avoid changes that may adversely affect large numbers of plugins.
