Difference between revisions of "Developers"
| Line 1: | Line 1: | ||
{{DevelopersTopNav}} | {{DevelopersTopNav}} | ||
| − | geWorkbench is an open source Java-based platform and contributions by members of the community are welcome and encouraged. The latest code | + | 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. |
| − | |||
| − | |||
Revision as of 10:53, 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).
Contributing a new geWorkbench component is a straightforward process: First you would request space in the project's CVS server (using the "Request to join" link from the gForge page). This allows you to work against the development version of the geWorkbench core. There are no restrictions on who can develop and submit a new component. On the other hand contributions to the geWorkbench core packages are controlled in order to avoid changes that may adversely affect large numbers of plugins.
