.GEAR files - Revision history

Zji at 16:11, 23 March 2010

2010-03-23T16:11:14Z

2006-10-13T21:25:39Z

2006-02-09T22:52:40Z

2006-01-31T17:31:11Z

‎Overview

2006-01-31T17:11:38Z

‎Creating a .GEAR file

2005-12-06T20:09:06Z

2005-12-06T20:08:42Z

‎Viewing loaded versions of components

2005-12-06T20:08:22Z

‎Viewing loaded versions of components

2005-12-06T20:07:33Z

2005-12-06T20:03:47Z

@@ Line 5: / Line 5: @@
 == Overview ==
-.GEAR files are essentially zipped versions of geWorkBench visual plugins. They make it easy to distribute reasonably sized upgrades to specific parts of the application. They are the geWorkbench analogue of .WAR files for web applications.
+.GEAR files are essentially zipped versions of geWorkBench component plugins. They make it easy to distribute reasonably sized upgrades to specific parts of the application. They are the geWorkbench analogue of .WAR files for web applications.
 == Creating a .GEAR file ==
@@ Line 13: / Line 13: @@
 == Viewing loaded versions of components ==
-The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.
+The menu item "Tools->Component Configuration" will list all the loaded versions of component plugins. The subdirectories and gear files under the component directory are loaded similarly.

@@ Line 1: / Line 1: @@
 == Overview ==
-.GEAR files are essentially zipped versions of geWorkBench visual plugins. They make it easy to distribute reasonably sized upgrades to specific parts of the application.
+.GEAR files are essentially zipped versions of geWorkBench visual plugins. They make it easy to distribute reasonably sized upgrades to specific parts of the application. They are the geWorkbench analogue of .WAR files for web applications.
 == Creating a .GEAR file ==

@@ Line 5: / Line 5: @@
 == Creating a .GEAR file ==
-There is an ant task that will create a .GEAR file automatically. Run ant with something like “ant –Dcomponent=alignment” which will create a .gear file from the alignment component directory. Then put the resulting alignment.gear in a directory called “gears” and the next time the program is run it’ll load the component out of that file.
+There is an ant task that will create a .GEAR file automatically. Run ant with “ant –Dcomponent=NAME” which will create a .gear file from the specified component directory. You can also run the Windows batch file “makeGear NAME” instead. Put the resulting .gear file in the components directory of a geWorkbench installation and it will be loaded by the application.
 == Viewing loaded versions of components ==

← Older revision		Revision as of 20:09, 6 December 2005
Line 11:		Line 11:
	The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.		The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.

−	[[Image:VersionDialog.~~jpg~~\|\|Example version screen.]]	+	[[Image:VersionDialog.png\|\|Example version screen.]]

← Older revision		Revision as of 20:08, 6 December 2005
Line 11:		Line 11:
	The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.		The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.

−	[[Image:VersionDialog.jpg]]	+	[[Image:VersionDialog.jpg\|\|Example version screen.]]

← Older revision		Revision as of 20:07, 6 December 2005
Line 9:		Line 9:
	== Viewing loaded versions of components ==		== Viewing loaded versions of components ==

−	The	+	The version menu item, under help will list all the loaded versions of plugins, and will indicate which ones are loading from .GEAR files, an example is below.
		+
		+	[[Image:versionDialog.jpg]]

← Older revision		Revision as of 20:03, 6 December 2005
Line 4:		Line 4:

	== Creating a .GEAR file ==		== Creating a .GEAR file ==
		+
		+	There is an ant task that will create a .GEAR file automatically. Run ant with something like “ant –Dcomponent=alignment” which will create a .gear file from the alignment component directory. Then put the resulting alignment.gear in a directory called “gears” and the next time the program is run it’ll load the component out of that file.
		+
		+	== Viewing loaded versions of components ==
		+
		+	The