ULCUI starts the user interface engine of ULC.

SYNOPSIS

ULCUI [-url URL] [-indirectUrl URL]
[-server (portNumber | URL)] [-genServerUrlFile fileName]
[-locale ISOlanguage_ISOCountry] [-look Look&Feel_class]
[-m] [-ipaddr] [-applet] [-doublebuffering] [-debug]
[-enablelog] [-logfilename fileName] [-userParameter String]
[-autoReconnect] [fileName]

DESCRIPTION

The ULCUI program starts the UI engine. The engine can be started with different parameters and/or with a ULC Monitor if desired.

OPTIONS

-url URL
Starts the UI Engine in client mode, that is, the UI Engine tries to connect to an application server with the given URL. The URL should conform to the standard syntax:

A typical example for the default ULC protocol using sockets would be:

Another example for using the CORBA IIOP protocol could look like the following (the servant's stringified IOR in the reference part of the URL):

-indirectUrl URL
Makes the UI engine read the server's URL indirectly from the URL specified.
Example: ulcui.exe -indirectUrl file:///c:\browser.ior

-server (portNumber | URL)
Starts the UI engine as a server either with the default ulc protocol
on the specified port or using the specified URL to extract the
necessary information (eg. which protocol to use).

-genServerUrlFile fileName
In server mode, makes the UI engine generate a URL representing the server in the specified file. Clients can then use that URL to connect to the UI engine.

-locale
Overrides the default locale of the UI Engine. The format is Language_Country. where language and country are the two character ISO abbreviations.
eg: -locale en_US

-look Look&Feel class name
Specifies the class name for the desired look and feel.If not specified the default look and feel for the platform is used. Possible values are: 

com.sun.java.swing.plaf.windows.WindowsLookAndFeel
com.sun.java.swing.plaf.jlf.JLFLookAndFeel
com.sun.java.swing.plaf.motif.MotifLookAndFeel
com.sun.java.swing.plaf.metal.MetalLookAndFeel

-m
Starts the ULC Monitor.

-ipaddr
If present this option makes the system use IP addresses instead of DNS names (internally).

-doublebuffering
Toggles the double buffering. Default is on.

-applet
Tells the UI engine that it is running as an applet.

-debug
Enables the writing of debug output on the console.

-enablelog
Enables the writing of log information into the configured logfile.(Default is ulcui.log)
See ULC Monitor

-logfilename fileName
Specifies the file name into which all logging information (if enabled) should be written.

-userParameter String
Specifies the optional user parameter which can be queried by the application using the getUserParameter API.

-autoReconnect
The UI started in client mode will retry to connect to the server for each connection which went down. This will normally start a new context except for ULC Smalltalk applications with enabled Client reconnect feature

fileName
If only a single parameter is passed to the UI Engine and if that parameter does not start with a - then it is treated as a fileName whose first line will be read and interpreted as the parameters to start the UI Engine. This allows creating shortcuts on the desktop (Windows platform only) that can be used to launch the UI Engine and make a connection to a running ULC server.(See: Running the UI Engine as a helper)

CAVEATS

The UlcUI program expects the directory and file structure it is embedded in (the UIEngine directory of the ULC distribution). In addition the ULCJREROOT environment variable should point to the root directory of the JRE installation. (Eg. set ulcjreroot=c:/ULC/R1.5/UIEngine/jre). If this environment variable is not specified the default JRE installation on the client machine is used. The system path and classpath must point to the JRE installation in this case. In addition the ULCUIHOME and ULCSWINGHOME environment variables should also be set. See Setting up the UI Engine.