watirgrid 0.0.7 → 0.0.8.pre

data/.document

@@ -1,5 +1,5 @@
-README.rdoc
-lib/**/*.rb
-bin/*
-features/**/*.feature
-LICENSE
+README.rdoc
+lib/**/*.rb
+bin/*
+features/**/*.feature
+LICENSE

data/.gitignore

@@ -1,22 +1,22 @@
-## MAC OS
-.DS_Store
-
-## TEXTMATE
-*.tmproj
-tmtags
-
-## EMACS
-*~
-\#*
-.\#*
-
-## VIM
-*.swp
-
-## PROJECT::GENERAL
-coverage
-rdoc
-doc
-pkg
-
-## PROJECT::SPECIFIC
+## MAC OS
+.DS_Store
+
+## TEXTMATE
+*.tmproj
+tmtags
+
+## EMACS
+*~
+\#*
+.\#*
+
+## VIM
+*.swp
+
+## PROJECT::GENERAL
+coverage
+rdoc
+doc
+pkg
+
+## PROJECT::SPECIFIC

data/EXAMPLES.rdoc

@@ -1,132 +1,132 @@
-= Common Examples
-
-== Starting a Controller
-A controller has the following startup options:
-  controller --help
-  Usage: controller [options]
-  Specific options:
-      -H, --drb-server-host HOST       Specify DRb Server interface to host on
-      -d, --drb-server-port PORT       Specify DRb Server port to listen on
-      -h, --ring-server-host HOST      Specify Ring Server interface to host on
-      -r, --ring-server-port PORT      Specify Ring Server port to listen on
-      -a, --access-control-list ACLS   Specify a comma separated Access Control List
-      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
-          --help                       Show this message
-
-=== Default
-To start a controller with default settings:
-  $ controller
-
-This will bind the controller to your external facing interface and register the ring server to listen on port 12358
-e.g.
-  DRb server started on : druby://143.238.105.61:11235
-  Ring server started on: druby://143.238.105.61:12358
-  
-=== Start on specific interface or ports
-To start a controller on specific interfaces or ports:
-  $  controller -H 127.0.0.1 -h 127.0.0.1 -d 12345 -r 54321
-
-This will bind the controller to the localhost (127.0.0.1) with the DRb server listening on port 12345 and the ring server listening on port 54321
-e.g.
-  DRb server started on : druby://127.0.0.1:12345
-  Ring server started on: druby://127.0.0.1:54321
-  
-
-=== Start with access control list
-To start a controller with an access control list:
-  $  controller -a deny,all,allow,127.0.0.1 -H 127.0.0.1 -h 127.0.0.1
-
-This will bind the controller to the localhost (127.0.0.1) and deny all access to the controller by default, whilst allowing access from localhost only. The ACL constructor takes an array of strings. The first string of a pair is always “allow” or “deny”, and it’s followed by the address or addresses to allow or deny access.
-
-== Starting a Provider
-A provider has similar startup options:
-  provider --help
-  # Usage: provider [options]
-  # Specific options:
-  #     -H, --drb-server-host HOST       Specify DRb Server interface to host on
-  #     -d, --drb-server-port PORT       Specify DRb Server port to listen on
-  #     -h, --ring-server-host HOST      Specify Ring Server host to connect to
-  #     -r, --ring-server-port PORT      Specify Ring Server port to broadcast on
-  #     -b, --browser-type TYPE          Specify browser type to register {ie|firefox|safari}
-  #     -a, --access-control-list ACLS   Specify a comma separated Access Control List
-  #     -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
-  #         --help                       Show this message
-
-=== Default
-To start a controller with default settings:
-  $ provider
-
-This will bind the provider to your external facing interface attempt to find the ring server on the default port of 12358
-e.g.
-  DRb server started on : druby://143.238.105.61:11236
-  Ring server found on  : druby://143.238.105.61:12358
-  New tuple registered  : druby://143.238.105.61:12358
-
-=== Start on specific interface or ports
-To start a provider on specific interfaces or ports:
-  $  provider -r 12358 -h 143.238.105.61
-
-This will attempt to find the ring server on the port and hostname specifed
-e.g.
-  DRb server started on : druby://143.238.105.61:11236
-  Ring server found on  : druby://143.238.105.61:12358
-  New tuple registered  : druby://143.238.105.61:12358
-
-=== Start with access control list
-To start a controller with an access control list:
-  $  provider -a deny,all,allow,127.0.0.1
-
-This will deny all access by default and allow access to this provider on localhost only.
-
-=== Start with a specific browser supported
-By default, the provider will try to instantiate a browser object based on availability with your operating system e.g. Internet Explorer, Firefox or Safari. You can force provision of a set browser type as follows:
-  $  provider -b safari
-  
-This will provide a Safari browser object. Other options are:
-  $  provider -b ie
-  $  provider -b firefox
-
-== Consuming Browser Objects on the Grid
-Watir has been extended with a Grid class that can be used as follows:
-  require 'rubygems'
-  require 'watirgrid'
-
-  grid = Watir::Grid.new(:ring_server_port => 12358)
-  grid.start(:quantity => 1, :read_all => true, :browser_type => 'ie')
-  threads = []
-  grid.browsers.each do |browser|
-    threads << Thread.new do 
-      b = browser[:object].new_browser
-      b.goto("http://www.google.com")
-      b.text_field(:name, 'q').set("watirgrid")
-      b.button(:name, "btnI").click
-    end
-  end
-  threads.each {|thread| thread.join}
-
-Stepping through this example we first instantiate a browsers object, specifying which ring server port to broadcast on when looking for available providers:
-  grid = Watir::Grid.new(:ring_server_port => 12358)
-
-You may also need to tell the code which host the ring server is on:
-  grid = Watir::Grid.new(:ring_server_port => 12358, :ring_server_host => 143.238.105.61)
-
-Next we start up the grid, specifying the number of browsers we wish to use, and the method of accessing the tuple space:
-  grid.start(:quantity => 1, :read_all => true)
-  
-There are two methods for accessing the tuple space. 
-  :read_all => true
-  :take_all => true
-*Read* *All* will read all browsers in the tuple space provided by the providers. This leaves the tuple open to other clients. 
-
-*Take* *All* will take all browsers in the tuple space in a destructive manner. That is, once a tuple has been taken, no other clients will be able to re-use that tuple. This is useful if you do not want concurrent access to the same host, for example, multiple browsers running on the one machine.
-
-The quantity attribute will determine how many browsers are accessed.
-  :quantity => 10
-Will attempt to access 10 tuples if they are available.
-
-Other attributes include:
-  :hostnames => { "localhost" => "127.0.0.1"}
-Will determine which providers identified by a hash of hostnames that should be accessed. Useful if trying to limit the test to run from specific hostnames or IP addresses.
-
-  :browser_type => 'firefox'
+= Common Examples
+
+== Starting a Controller
+A controller has the following startup options:
+  controller --help
+  Usage: controller [options]
+  Specific options:
+      -H, --drb-server-host HOST       Specify DRb Server interface to host on
+      -d, --drb-server-port PORT       Specify DRb Server port to listen on
+      -h, --ring-server-host HOST      Specify Ring Server interface to host on
+      -r, --ring-server-port PORT      Specify Ring Server port to listen on
+      -a, --access-control-list ACLS   Specify a comma separated Access Control List
+      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
+          --help                       Show this message
+
+=== Default
+To start a controller with default settings:
+  $ controller
+
+This will bind the controller to your external facing interface and register the ring server to listen on port 12358
+e.g.
+  DRb server started on : druby://143.238.105.61:11235
+  Ring server started on: druby://143.238.105.61:12358
+  
+=== Start on specific interface or ports
+To start a controller on specific interfaces or ports:
+  $  controller -H 127.0.0.1 -h 127.0.0.1 -d 12345 -r 54321
+
+This will bind the controller to the localhost (127.0.0.1) with the DRb server listening on port 12345 and the ring server listening on port 54321
+e.g.
+  DRb server started on : druby://127.0.0.1:12345
+  Ring server started on: druby://127.0.0.1:54321
+  
+
+=== Start with access control list
+To start a controller with an access control list:
+  $  controller -a deny,all,allow,127.0.0.1 -H 127.0.0.1 -h 127.0.0.1
+
+This will bind the controller to the localhost (127.0.0.1) and deny all access to the controller by default, whilst allowing access from localhost only. The ACL constructor takes an array of strings. The first string of a pair is always “allow” or “deny”, and it’s followed by the address or addresses to allow or deny access.
+
+== Starting a Provider
+A provider has similar startup options:
+  provider --help
+  # Usage: provider [options]
+  # Specific options:
+  #     -H, --drb-server-host HOST       Specify DRb Server interface to host on
+  #     -d, --drb-server-port PORT       Specify DRb Server port to listen on
+  #     -h, --ring-server-host HOST      Specify Ring Server host to connect to
+  #     -r, --ring-server-port PORT      Specify Ring Server port to broadcast on
+  #     -b, --browser-type TYPE          Specify browser type to register {ie|firefox|safari}
+  #     -a, --access-control-list ACLS   Specify a comma separated Access Control List
+  #     -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
+  #         --help                       Show this message
+
+=== Default
+To start a controller with default settings:
+  $ provider
+
+This will bind the provider to your external facing interface attempt to find the ring server on the default port of 12358
+e.g.
+  DRb server started on : druby://143.238.105.61:11236
+  Ring server found on  : druby://143.238.105.61:12358
+  New tuple registered  : druby://143.238.105.61:12358
+
+=== Start on specific interface or ports
+To start a provider on specific interfaces or ports:
+  $  provider -r 12358 -h 143.238.105.61
+
+This will attempt to find the ring server on the port and hostname specifed
+e.g.
+  DRb server started on : druby://143.238.105.61:11236
+  Ring server found on  : druby://143.238.105.61:12358
+  New tuple registered  : druby://143.238.105.61:12358
+
+=== Start with access control list
+To start a controller with an access control list:
+  $  provider -a deny,all,allow,127.0.0.1
+
+This will deny all access by default and allow access to this provider on localhost only.
+
+=== Start with a specific browser supported
+By default, the provider will try to instantiate a browser object based on availability with your operating system e.g. Internet Explorer, Firefox or Safari. You can force provision of a set browser type as follows:
+  $  provider -b safari
+  
+This will provide a Safari browser object. Other options are:
+  $  provider -b ie
+  $  provider -b firefox
+
+== Consuming Browser Objects on the Grid
+Watir has been extended with a Grid class that can be used as follows:
+  require 'rubygems'
+  require 'watirgrid'
+
+  grid = Watir::Grid.new(:ring_server_port => 12358)
+  grid.start(:quantity => 1, :read_all => true, :browser_type => 'ie')
+  threads = []
+  grid.browsers.each do |browser|
+    threads << Thread.new do 
+      b = browser[:object].new_browser
+      b.goto("http://www.google.com")
+      b.text_field(:name, 'q').set("watirgrid")
+      b.button(:name, "btnI").click
+    end
+  end
+  threads.each {|thread| thread.join}
+
+Stepping through this example we first instantiate a browsers object, specifying which ring server port to broadcast on when looking for available providers:
+  grid = Watir::Grid.new(:ring_server_port => 12358)
+
+You may also need to tell the code which host the ring server is on:
+  grid = Watir::Grid.new(:ring_server_port => 12358, :ring_server_host => 143.238.105.61)
+
+Next we start up the grid, specifying the number of browsers we wish to use, and the method of accessing the tuple space:
+  grid.start(:quantity => 1, :read_all => true)
+  
+There are two methods for accessing the tuple space. 
+  :read_all => true
+  :take_all => true
+*Read* *All* will read all browsers in the tuple space provided by the providers. This leaves the tuple open to other clients. 
+
+*Take* *All* will take all browsers in the tuple space in a destructive manner. That is, once a tuple has been taken, no other clients will be able to re-use that tuple. This is useful if you do not want concurrent access to the same host, for example, multiple browsers running on the one machine.
+
+The quantity attribute will determine how many browsers are accessed.
+  :quantity => 10
+Will attempt to access 10 tuples if they are available.
+
+Other attributes include:
+  :hostnames => { "localhost" => "127.0.0.1"}
+Will determine which providers identified by a hash of hostnames that should be accessed. Useful if trying to limit the test to run from specific hostnames or IP addresses.
+
+  :browser_type => 'firefox'
 Will determine which providers identified by a browser type should be accessed. Useful if trying to to test with specific browser types.

data/HISTORY.rdoc

@@ -1,18 +1,18 @@
-== Release Notes
-=== 0.0.1
-Added access control lists for the controller and provider. This lets the user specify ACLs by way of simple white/blacklist security similar to that used by the Unix /etc/hosts.allow and /etc/hosts.deny files. The ACL constructor takes an array of strings. The first string of a pair is always “allow” or “deny”, and it’s followed by the address or addresses to allow or deny access.
-
-e.g. 
-  provider.rb -a deny,all,allow,127.0.0.1
-This would deny all access to this provider by default and allow access only from the localhost (127.0.0.1). This is the default setting if no ACLs are specified from the command line. This would affect all connectivity from the controller to the providers.
-
-e.g. 
-  controller -a deny,all,allow,192.168.1.*
-This would deny all access to the controller by default with access allowed from any host in the 192.168.1.* subnet. This would affect all connectivity from the providers to the controller.
-
-Added startup bin scripts for the provider and controller. Ruby Gems will automatically deploy these on installation.
-
----
-=== 0.0.2
-Allowed specification of remote host for ring server with -h option on provider.
-
+== Release Notes
+=== 0.0.1
+Added access control lists for the controller and provider. This lets the user specify ACLs by way of simple white/blacklist security similar to that used by the Unix /etc/hosts.allow and /etc/hosts.deny files. The ACL constructor takes an array of strings. The first string of a pair is always “allow” or “deny”, and it’s followed by the address or addresses to allow or deny access.
+
+e.g. 
+  provider.rb -a deny,all,allow,127.0.0.1
+This would deny all access to this provider by default and allow access only from the localhost (127.0.0.1). This is the default setting if no ACLs are specified from the command line. This would affect all connectivity from the controller to the providers.
+
+e.g. 
+  controller -a deny,all,allow,192.168.1.*
+This would deny all access to the controller by default with access allowed from any host in the 192.168.1.* subnet. This would affect all connectivity from the providers to the controller.
+
+Added startup bin scripts for the provider and controller. Ruby Gems will automatically deploy these on installation.
+
+---
+=== 0.0.2
+Allowed specification of remote host for ring server with -h option on provider.
+

data/LICENSE

@@ -1,20 +1,20 @@
-Copyright (c) 2009 Tim Koopmans
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
-NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
-LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
-OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
-WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+Copyright (c) 2009 Tim Koopmans
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -1,82 +1,82 @@
-= WatirGrid
-
-WatirGrid allows for distributed testing across a grid network using Watir.
-
-== Getting Started
-This gem is hosted on Gemcutter. Gemcutter is the next generation of gem hosting for the Ruby community. To get started:
-  gem install gemcutter
-  gem tumble
-  
-Then to install WatirGrid:
-  gem install watirgrid
-
-=== The Basics
-WatirGrid is built on Rinda which implements the Linda distributed computing paradigm in Ruby. According to Wikipedia: “Linda is a model of coordination and communication among several parallel processes operating upon objects stored in and retrieved from shared, virtual, associative memory.”
-
-In other words, WatirGrid allows multiple parallel processes to *_provide_* remote Watir objects in the form of tuple spaces across a grid network. This grid network is *_controlled_* by a ring server.
-
-==== Key Terminology
-The *controller* implements a repository of tuples (tuple space) that can be accessed concurrently. The controller hosts the *ring* *server* which advertises these tuples across a grid network. Typically you will host one controller on a central machine.
-
-The *providers* make remote Watir objects available to the tuple space hosted by the *ring* *server*. Typically you will host one or many providers on your grid network, for example, each PC may become a single provider of a Watir tuple in the form of an Internet Explorer, Firefox or Safari browser object.
-
-=== Simple Example
-
-Pick a server to host the 'controller' for the ring server and execute the following:
-  $ controller
-
-This should find your external facing IP and start the corresponding DRb and Ring Servers:
-  DRb server started on : druby://143.238.105.61:11235
-  Ring server started on: druby://143.238.105.61:12358
-
-On each client PC, host the 'provider' for the distributed (DRb) Watir objects
-  $  provider
-
-This should find the recently started Ring Server and register a tuple for the Watir object:
-  DRb server started on : druby://143.238.105.61:11236
-  Ring server found on  : druby://143.238.105.61:12358
-  New tuple registered  : druby://143.238.105.61:12358
-
-You will now be able to execute commands across remote browsers on your grid network.
-
-e.g.
-  grid = Watir::Grid.new(:ring_server_port => 12358)
-  grid.start(:quantity => 1, :read_all => true)
-  threads = []
-  grid.browsers.each do |browser|
-    threads << Thread.new do 
-      b = browser[:object].new_browser
-      b.goto("http://www.google.com")
-      b.text_field(:name, 'q').set("watirgrid")
-      b.button(:name, "btnI").click
-    end
-  end
-  threads.each {|thread| thread.join}
-
-You may wish to host the controller and providers on different machines in a real scenario. You can specify things like server hostnames, ports and access control lists for each of the different types of servers. For more help see:
-  $  controller --help
-  Usage: controller [options]
-  Specific options:
-      -H, --drb-server-host HOST       Specify DRb Server interface to host on
-      -d, --drb-server-port PORT       Specify DRb Server port to listen on
-      -h, --ring-server-host HOST      Specify Ring Server interface to host on
-      -r, --ring-server-port PORT      Specify Ring Server port to listen on
-      -a, --access-control-list ACLS   Specify a comma separated Access Control List
-      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
-          --help                       Show this message
-
-  $  provider --help
-  Usage: provider [options]
-  Specific options:
-      -H, --drb-server-host HOST       Specify DRb Server interface to host on
-      -d, --drb-server-port PORT       Specify DRb Server port to listen on
-      -h, --ring-server-host HOST      Specify Ring Server host to connect to
-      -r, --ring-server-port PORT      Specify Ring Server port to broadcast on
-      -b, --browser-type TYPE          Specify browser type to register {ie|firefox|safari}
-      -a, --access-control-list ACLS   Specify a comma separated Access Control List
-      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
-          --help                       Show this message                  
-
-== Copyright
-
-Copyright (c) 2009 Tim Koopmans. See LICENSE for details.
+= WatirGrid
+
+WatirGrid allows for distributed testing across a grid network using Watir.
+
+== Getting Started
+This gem is hosted on Gemcutter. Gemcutter is the next generation of gem hosting for the Ruby community. To get started:
+  gem install gemcutter
+  gem tumble
+  
+Then to install WatirGrid:
+  gem install watirgrid
+
+=== The Basics
+WatirGrid is built on Rinda which implements the Linda distributed computing paradigm in Ruby. According to Wikipedia: “Linda is a model of coordination and communication among several parallel processes operating upon objects stored in and retrieved from shared, virtual, associative memory.”
+
+In other words, WatirGrid allows multiple parallel processes to *_provide_* remote Watir objects in the form of tuple spaces across a grid network. This grid network is *_controlled_* by a ring server.
+
+==== Key Terminology
+The *controller* implements a repository of tuples (tuple space) that can be accessed concurrently. The controller hosts the *ring* *server* which advertises these tuples across a grid network. Typically you will host one controller on a central machine.
+
+The *providers* make remote Watir objects available to the tuple space hosted by the *ring* *server*. Typically you will host one or many providers on your grid network, for example, each PC may become a single provider of a Watir tuple in the form of an Internet Explorer, Firefox or Safari browser object.
+
+=== Simple Example
+
+Pick a server to host the 'controller' for the ring server and execute the following:
+  $ controller
+
+This should find your external facing IP and start the corresponding DRb and Ring Servers:
+  DRb server started on : druby://143.238.105.61:11235
+  Ring server started on: druby://143.238.105.61:12358
+
+On each client PC, host the 'provider' for the distributed (DRb) Watir objects
+  $  provider
+
+This should find the recently started Ring Server and register a tuple for the Watir object:
+  DRb server started on : druby://143.238.105.61:11236
+  Ring server found on  : druby://143.238.105.61:12358
+  New tuple registered  : druby://143.238.105.61:12358
+
+You will now be able to execute commands across remote browsers on your grid network.
+
+e.g.
+  grid = Watir::Grid.new(:ring_server_port => 12358)
+  grid.start(:quantity => 1, :read_all => true)
+  threads = []
+  grid.browsers.each do |browser|
+    threads << Thread.new do 
+      b = browser[:object].new_browser
+      b.goto("http://www.google.com")
+      b.text_field(:name, 'q').set("watirgrid")
+      b.button(:name, "btnI").click
+    end
+  end
+  threads.each {|thread| thread.join}
+
+You may wish to host the controller and providers on different machines in a real scenario. You can specify things like server hostnames, ports and access control lists for each of the different types of servers. For more help see:
+  $  controller --help
+  Usage: controller [options]
+  Specific options:
+      -H, --drb-server-host HOST       Specify DRb Server interface to host on
+      -d, --drb-server-port PORT       Specify DRb Server port to listen on
+      -h, --ring-server-host HOST      Specify Ring Server interface to host on
+      -r, --ring-server-port PORT      Specify Ring Server port to listen on
+      -a, --access-control-list ACLS   Specify a comma separated Access Control List
+      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
+          --help                       Show this message
+
+  $  provider --help
+  Usage: provider [options]
+  Specific options:
+      -H, --drb-server-host HOST       Specify DRb Server interface to host on
+      -d, --drb-server-port PORT       Specify DRb Server port to listen on
+      -h, --ring-server-host HOST      Specify Ring Server host to connect to
+      -r, --ring-server-port PORT      Specify Ring Server port to broadcast on
+      -b, --browser-type TYPE          Specify browser type to register {ie|firefox|safari}
+      -a, --access-control-list ACLS   Specify a comma separated Access Control List
+      -l, --log-level LEVEL            Specify log level {DEBUG|INFO|ERROR}
+          --help                       Show this message                  
+
+== Copyright
+
+Copyright (c) 2009 Tim Koopmans. See LICENSE for details.