Difference between revisions of "Developers"
| Line 5: | Line 5: | ||
Development in geWorkbench takes place along 2 paralles axes: | Development in geWorkbench takes place along 2 paralles axes: | ||
* <u>'''geWorkbench core'''</u>: 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'' ('''B'''iomedical '''I'''nformatics '''S'''tructured '''ON'''tology) which contains the definition of the bioinformatics data types which form the basis of communication between the geWorkbench plugins. | * <u>'''geWorkbench core'''</u>: 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'' ('''B'''iomedical '''I'''nformatics '''S'''tructured '''ON'''tology) which contains the definition of the bioinformatics data types which form the basis of communication between the geWorkbench plugins. | ||
| − | * <u>'''geWorkbench plugins'''</u>: this portion of the source tree contains the code for the various application plugin components. The [[Introduction for Developers | + | * <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 logistically straightforward process and (logistically) can be accomplished in either of two ways: downloading the geWorkbench software development kit, setting up a local development environment and at the end of the development effort deliver to us a .gear archive file | Contributing a new geWorkbench component is a logistically straightforward process and (logistically) can be accomplished in either of two ways: downloading the geWorkbench software development kit, setting up a local development environment and at the end of the development effort deliver to us a .gear archive file | ||
Revision as of 11:56, 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 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 | "Introduction for Developers"] section provides sample code for creating a simple plugin.
Contributing a new geWorkbench component is a logistically straightforward process and (logistically) can be accomplished in either of two ways: downloading the geWorkbench software development kit, setting up a local development environment and at the end of the development effort deliver to us a .gear archive file
- 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
