standup.utils
Class CommandLineArguments
java.lang.Object
standup.utils.CommandLineArguments
public class CommandLineArguments
- extends Object
This class handles command line arguments passed to the STANDUP system.
Here is the documentation on available command line parameters:
Command line arguments:
=======================
(Last updated: 19 Mar 2007)
The STANDUP JAR now takes the following command-line parameters:
-width
-height: By default, STANDUP (starting v1.2.12 upwards) detects the
current screen resolution and uses the whole screen. However,
this can be overriden by specifying the -width and -height
parameters. It is recommended that they be overriden in tandem.
Additionally, the STANDUP graphic elements have been designed to
work on a 4:3 screen ratio, e.g. resolutions of 640x480, 800x600,
1024x768, etc.
[DEFAULT: uses current screen resolution]
-fullscreen: By default, STANDUP runs without any window 'decorations', e.g.
titlebar, borders. This can be overriden with -fullscreen=no,
which results in STANDUP running in a normal Windows window.
This should probably be specified in conjunction with -width
and -height. STANDUP currently does not support window resizing
very well.
[DEFAULT: -fullscreen=yes]
-translucent: Specifying -translucent=yes forces STANDUP to use Java's alpha
channel-based java.awt.Transparency.TRANSLUCENT transparency
rendering mode. This results in nicer rendering of the graphic
elements, e.g. shadows, but runs much slower on some machines.
The default is to use the faster (but less pretty)
java.awt.Transparency.BITMASK transparency rendering mode.
[DEFAULT: -translucent=no]
-datafolder: By default, STANDUP will look for (and in the absence of one,
create) a /standupdata subfolder where the standup_v*.jar is.
However, this can be overriden using this parameter, e.g.
-datafolder=c:\mydir will use c:\mydir as the STANDUP data
folder, creating it if it does not already exist. To specify
pathnames containing the space (' ') character, enclose the
pathname in double quotes, e.g.
-datafolder="C:\My Documents\Ruli\My STANDUP Data".
[DEFAULT: -datafolder=./standupdata]
*NOTE*: make sure that when running the options authoring tool
the appropriate datafolder is specified as well.
-enabledb: By default, STANDUP, attempts to establish a connection to the
PostgreSQL server to access the STANDUP lexical database.
This can be overriden by specifying -enabledb=no, which results
in the launching of the Demo version of STANDUP.
[DEFAULT: Full version: -enabledb=yes
Demo version: -enabledb=no]
-pgdb
-pguser
-pgpwd: By default, STANDUP uses the details specified in the
installation webpage, i.e. the database is 'standup_v1.X', the
user is 'standup', and the password is 'pgsuper!'. This can be
overriden by using these parameters.
[DEFAULT: -pgdb=standup_v1.X -pguser=standup -pgpwd=pgsuper!]
-oldcache: By default, STANDUP (starting v1.2.12 upwards) uses the demo joke
cache, i.e. a collection of 985 jokes roughly distributed evenly
across the different FLevels and schemas. If -oldcache=yes is
specified, it will use the joke cache used during the Corseford
evaluations, i.e. a collection of jokes selected for quality(!).
[DEFAULT: -oldcache=no]
-fclass: By default, STANDUP creates default lexical resources for, i.e.
'default.topic' and 'default.lexicon' for FClass FC5.
If -fclass=fc<n> (where n=1..5) is specified, it creates
different FClass resources.
-emptylex: By default, STANDUP creates an empty 'default.lexicon'.
If -emptylex=no is specified, it uses the 'topic-complement'
custom lexicon for the specified fclass.
[DEFAULT: -emptylex=yes]
-autocomp: By default, STANDUP uses a 3rd-party AutoCompletion class (see
http://www.orbital-computer.de/JComboBox for details),
which provides autocompletion (and additionally,
handles insertions, cursor key movements, etc, elegantly), to
provide 'predictive' text when entering a word ('Spell It'
when textinput is enabled). It allows the user to enter words
that are *not* in the current working lexicon. An alternative
method is to use a custom-made method (which was used in versions
prior to v1.4.1).
If -autocomp=no is specified, it uses this custom-made method.
[DEFAULT: -autocomp=yes]
Examples:
java standup.clouds.CloudFrontend -width=800 -height=600
-fullscreen=no -translucent=yes
This would launch the full version of STANDUP in an 800x600 window with
standard Windows XP 'decorations', and uses the slow-but-pretty translucent
rendering.
java standup.clouds.CloudFrontend -datafolder="h:/network drive/lab apps/standup"
-enabledb=no
This would launch the demo version of STANDUP using the STANDUP data folder
in h:/network drive/lab apps/standup
- Author:
- Ruli Manurung
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
KEY_WIDTH
public static String KEY_WIDTH
KEY_HEIGHT
public static String KEY_HEIGHT
KEY_DATAFOLDER
public static String KEY_DATAFOLDER
KEY_ENABLEDATABASE
public static String KEY_ENABLEDATABASE
KEY_POSTGRES_DB
public static String KEY_POSTGRES_DB
KEY_POSTGRES_USER
public static String KEY_POSTGRES_USER
KEY_POSTGRES_PASSWORD
public static String KEY_POSTGRES_PASSWORD
KEY_FULLSCREEN
public static String KEY_FULLSCREEN
KEY_OLDCACHE
public static String KEY_OLDCACHE
KEY_TRANSLUCENT
public static String KEY_TRANSLUCENT
KEY_FCLASS
public static String KEY_FCLASS
KEY_EMPTYLEX
public static String KEY_EMPTYLEX
KEY_AUTOCOMP
public static String KEY_AUTOCOMP
VALUE_AFFIRMATIVE
public static String VALUE_AFFIRMATIVE
arguments
private static Hashtable<String,String> arguments
validArgKeys
private static String[] validArgKeys
CommandLineArguments
public CommandLineArguments()
get
public static String get(String key)
hasKey
public static boolean hasKey(String key)
isValidKey
private static boolean isValidKey(String key)
parseCommandLineArguments
public static void parseCommandLineArguments(String[] args)
- Takes the
String[] arguments passed by Java's main method
and instantiates the command line arguments hashtable.
- Parameters:
args -