Difference between revisions of "Developers"
| Line 7: | Line 7: | ||
* <u>'''geWorkbench plugins'''</u>: this portion of the source tree contains the code for the various application plugin components (the [[Introduction_For_Developers | "Introduction for Developers"]] section provides sample code for creating a simple plugin). | * <u>'''geWorkbench plugins'''</u>: this portion of the source tree contains the code for the various application plugin components (the [[Introduction_For_Developers | "Introduction for Developers"]] section provides sample code for creating a simple plugin). | ||
| − | Contributing a new geWorkbench component is a straightforward process: you can either use the [[Devkit | geWorkbench software development kit] in your local development environment or you can request space in the project's CVS server (the latter means that you will be working against the development version of the geWorkbench core | + | Contributing a new geWorkbench component is a straightforward process: you can either use the [[Devkit | geWorkbench software development kit]] in your local development environment or you can request space in the project's CVS server (using the "Request to join" link from the gForge page). The latter means that you will be working 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. |
<br/><br/><br/> | <br/><br/><br/> | ||
Revision as of 12:24, 10 February 2006
|
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 releases as well as technical documenation, forums and mailing lists can be found at the project's gForge page, http://gforge.nci.nih.gov/projects/caworkbench. If you are interested in working with us you can follow the "Request to join" link from that page.
Development in geWorkbench takes place along 2 paralles 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 (the "Introduction for Developers" section provides sample code for creating a simple plugin).
Contributing a new geWorkbench component is a straightforward process: you can either use the geWorkbench software development kit in your local development environment or you can request space in the project's CVS server (using the "Request to join" link from the gForge page). The latter means that you will be working 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.
- Introduction For Developers
- Instructions for the Developer Kit
- Building geWorkbench
- Coding Standards Style Guide
- Javadocs
- CVS Repository
- Screenshots
- Information on .GEAR files, a method of distributing plugins.
- Plugin certification checklist
