A Simple Plugin - Revision history

Ut2102: /* Application Layout */

2013-07-16T16:08:59Z

‎Application Layout

2013-07-16T16:08:22Z

‎Application Layout

2010-04-25T23:47:32Z

‎Configuration

2010-04-25T23:46:46Z

‎Configuration

2010-04-25T23:42:53Z

‎Configuration

2006-02-10T18:01:25Z

Introduction For Developers moved to A Simple Plugin

2006-02-09T22:55:02Z

2005-12-07T15:48:22Z

‎Introduction

2005-12-06T22:03:59Z

2005-12-06T22:01:51Z

@@ Line 29: / Line 29: @@
 === Visual Area ===
-[[Image:VisualArea.png]]
+[[Image:VisualArea.png|{{ImageMaxWidth}}]]
 This area contains visualization components for the data set currently selected. Large, self-contained components will also likely appear in this area.
@@ Line 35: / Line 35: @@
 === Command Area ===
-[[Image:CommandArea.png]]
+[[Image:CommandArea.png|{{ImageMaxWidth}}]]
 Analysis components and other miscellaneous components are found in the Command Area. Many of these anlyses result in the creation of ancillary data sets which appear in the Project Panel.

@@ Line 13: / Line 13: @@
 There are four main ''areas'' in geWorkbench:
-[[Image:VisualAreas.png]]
+[[Image:VisualAreas.png|{{ImageMaxWidth}}]]
 === Project Area ===

@@ Line 217: / Line 217: @@
 </pre>
 * The <tt>id</tt> attribute is just a unique identifier for the component.
 * The <tt>name</tt> attribute is the name that appears in the interface (if visual).

@@ Line 205: / Line 205: @@
 == Configuration ==
-Configuration of the application is controlled by XML files, including one main xml file and one xml file for each plugin component. The main xml file can be specified as a command-line argument to geWorkbench, or a default XML file will be chosen if none is specified. A schema for this configuration file is available. See <tt>geWorkbench/src/org/geworkbench/engine/config</tt> for some example configuration files.
+Configuration of the application is controlled by XML files, including one configuration xml file and one xml file for each plugin component. The main xml file can be specified as a command-line argument to geWorkbench, or a default XML file will be chosen if none is specified. Each component's configuration file should be in the same directory of the java class and has the name matching the java class except for the extension .cwb.xml. The schema for the main configuration file and the components' configuration files are available. See <tt>geWorkbench/src/org/geworkbench/engine/config</tt> for some example configuration files.
 A typical configuration directive for the above exmaple component is as follows:

@@ Line 205: / Line 205: @@
 == Configuration ==
-Configuration of the application is controlled by an XML file. This file can be specified as a command-line argument to geWorkbench, or a default XML file will be chosen if none is specified. A schema for this configuration file is available. See <tt>geWorkbench/src/org/geworkbench/engine/config</tt> for some example configuration files.
+Configuration of the application is controlled by XML files, including one main xml file and one xml file for each plugin component. The main xml file can be specified as a command-line argument to geWorkbench, or a default XML file will be chosen if none is specified. A schema for this configuration file is available. See <tt>geWorkbench/src/org/geworkbench/engine/config</tt> for some example configuration files.
 A typical configuration directive for the above exmaple component is as follows:

← Older revision	Revision as of 18:01, 10 February 2006
(No difference)

← Older revision		Revision as of 22:55, 9 February 2006
Line 1:		Line 1:
		+	{{DevelopersTopNav}}
		+
	This introduction introduces the basic concepts for geWorkbench developers. It also walks through the creation of a simple component.		This introduction introduces the basic concepts for geWorkbench developers. It also walks through the creation of a simple component.

@@ Line 3: / Line 3: @@
 == Introduction ==
-geWorkbench is a component-based application framework. All functionality of software is provided by components which can be added, removed and configured in a flexible way. All the visual plugins, analysis tools and even file filters are implemented as components.
+geWorkbench is a component-based application framework. All functionality of the software is provided by components which can be added, removed and configured in a flexible way. All the visual plugins, analysis tools and even file filters are implemented as components.
 == Application Layout ==

@@ Line 135: / Line 135: @@
 </pre>
-Methods annotated with <code>@Subscribe</code> are called by geWorkbench when an object of the appropriate type is published. In this case, the method will be called by the engine when another component publishes an object of type <code>ProjectEvent</code>. The second parameter to the method is the publishing compoent itself, although this should rarely be needed. A method annotated with Code>@Subscribe</code> that does not take exactly two parameters will cause an error.
+Methods annotated with <code>@Subscribe</code> are called by geWorkbench when an object of the appropriate type is published. In this case, the method will be called by the engine when another component publishes an object of type <code>ProjectEvent</code>. The second parameter to the method is the publishing compoent itself, although this should rarely be needed. A method annotated with <code>@Subscribe</code> that does not take exactly two parameters will cause an error.
 The <code>ProjectEvent</code> is published by the Project Panel. It is published upon the selection of a data set. Almost all components will subscribe to this kind of event.

← Older revision		Revision as of 22:01, 6 December 2005
Line 214:		Line 214:
	</plugin>		</plugin>
	</pre>		</pre>
		+
		+	* Components are made available to the application via the <tt><plugin></tt> element.
		+	* The <tt>id</tt> attribute is just a unique identifier for the component.
		+	* The <tt>name</tt> attribute is the name that appears in the interface (if visual).
		+	* The <tt>class</tt> attribute is the full class name of the component.
		+	* The <tt>source</tt> attribute is the resource directory where the component can be found.
		+	* The <tt><gui-area></tt> element is used to define how the component should be displayed. It is for visual components only. In this case, we put the component in to the main visual area of the application.