Developers - Revision history

Zji at 16:21, 13 November 2013

2013-11-13T16:21:30Z

Zji at 17:09, 23 February 2012

2012-02-23T17:09:46Z

Zji at 15:00, 23 October 2010

2010-10-23T15:00:00Z

Zji at 14:06, 29 June 2010

2010-06-29T14:06:28Z

Zji at 00:03, 26 April 2010

2010-04-26T00:03:32Z

Zji at 16:17, 22 March 2010

2010-03-22T16:17:42Z

Zji at 15:53, 22 March 2010

2010-03-22T15:53:36Z

Keshav at 17:15, 20 March 2009

2009-03-20T17:15:10Z

Smith at 20:25, 16 March 2009

2009-03-16T20:25:45Z

Floratos at 16:11, 29 September 2008

2008-09-29T16:11:32Z

@@ Line 1: / Line 1: @@
 {{DevelopersTopNav}}
-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/trunk/geworkbench/. Anonymous read access is supported for all the 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
@@ Line 13: / Line 15: @@
 # ''util'', all the utility libraries
 # ''analysis'', a small number of classes providing abstract for analyses and savable parameter settings. This group used to be called "others" to include miscellaneous; ''analysis'' is the only one left now. This probably will be re-organized in the future.
-* <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 plugin components'''</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.

@@ Line 12: / Line 12: @@
 # ''events'', event classes used by communication between all components and the core
 # ''util'', all the utility libraries
-# ''others'', including package "analysis" providing abstract for analyses and package "algorithm" used by some classification algorithm. Both contains a small number of classes.
+# ''analysis'', a small number of classes providing abstract for analyses and savable parameter settings. This group used to be called "others" to include miscellaneous; ''analysis'' is the only one left now. This probably will be re-organized in the future.
 * <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.

@@ Line 4: / Line 4: @@
-Development in geWorkbench takes place along 2 parallel axes:
+Development in geWorkbench takes place along 2 lines:
 * <u>'''geWorkbench core'''</u>: this portion of the code includes mainly 7 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)
 # ''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.
 # ''builtin'', supporting the internal execution and coordination of the core process, especially the project panel
-# ''components'', parsers and supports for input data format
+# ''parsers'', parsing supports for input data format
 # ''events'', event classes used by communication between all components and the core
 # ''util'', all the utility libraries
 * <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.

← Older revision		Revision as of 14:06, 29 June 2010
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 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.	+	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/trunk/geworkbench/. Anonymous read access is supported for all the code.

@@ Line 5: / Line 5: @@
 Development in geWorkbench takes place along 2 parallel 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 7 groups of packages:
-* <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]]).
+# ''engine'', which implements services related to the geWorkbench component architecture framework (e.g., plugin instantiation and visual layout, message delivery, component registry management, etc)
 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.

← Older revision		Revision as of 16:17, 22 March 2010
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]]).

−	~~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.	+	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.

← Older revision		Revision as of 15:53, 22 March 2010
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 ~~releases as well as technical documentation~~ can be found at ~~the project~~'s ~~gForge page~~, ~~http~~://~~gforge~~.nci.nih.gov/~~projects~~/geworkbench. ~~There are two ways to~~ access ~~the project's 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.
−	* Individuals interested in participating in the development process can click on the '''''"Request to join"''''' link at the bottom of the project page to acquire an account on the geWorkbench CVS code repository. Once this account is ~~issued it is be possible to check code in and out of~~ the ~~repository.~~
−	* Read-only code ~~access is also possible, please see the [[FAQ#download_geworkbench_code \| FAQ section of the site for details]]~~.

← Older revision		Revision as of 17:15, 20 March 2009
Line 11:		Line 11:

	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.		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.
−
−	~~The [[Software Development Kit \| geWorkbench software development kit]] is not currently supported.~~

← Older revision		Revision as of 20:25, 16 March 2009
Line 10:		Line 10:
	* <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]]).

−	Contributing a new geWorkbench component is a straightforward process: you ~~can either use the [[Software Development Kit \| 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.	+	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.
		+
		+	The [[Software Development Kit \| geWorkbench software development kit]] is not currently supported.