Workspace Manager(OLWM) Features:
---------------------------------
---------------------------------

Init file
---------

If you wish to "auto-start" applications when you start QNX
Windows, you can create an executable shell file called
"olwm.init" in the appropriate windows configuration
directory. Both "$home/windows/olwm.init"(personal file) and
"/windows/apps/Olwm/olwm.init"(system file) are
automatically executed. For example, it could contain:

	/windows/apps/Olfm/olfm &
	sleep 1
	/windows/apps/wterm &


A "sleep" command should be placed between each program to
give each application time to start up cleanly.  Also, make
sure the "olwm.init" file is executable.

Properties
----------
Selecting "Properties..." in the Workspace Menu, lets you
specify the following program properties:

	- the initial state of a window (i.e. whether it
	  is a Window, Icon, or Full). 
	- the initial location of a window.
	- the initial size of the window.
	- the initial location of an icon.
   
To make the changes permanent, select "Apply". The *next*
time the application starts it will use these values to
determine how the application window should start up. 

Also, if you click MENU on the "Category" button and select
"System Colors", you can define the 16 colors any way you
like. You can also select new colors by name using the
"Color Names" list under the "Properties..." button.

Select "Apply" to make your changes permanent. 

Customizing the File Manager 
----------------------------
----------------------------

The File Manager is a fast, graphical means of starting QNX
Windows applications and loading data files into them. For
example, to start an application, you can just double-click
on a symbol representing one of its data files and the
application will automatically load onto the workspace.

Data files are bound with their respective applications by
associating a pattern specification with a program. These
bindings are defined in the File Manager configuration file,
olfm.cfg. A maximum of 30 bindings can be defined.

When the File Manager starts up, it looks in two places for
olfm.cfg files. It first looks for the system-level
configuration file:

/windows/apps/olfm/olfm.cfg

Then it looks for a user-level file:

$home/windows/olfm.cfg

The binding definitions contained in both these files are
merged. Note that in the case of duplicate definitions for
bindings, the user definition will override the system
definition.


The syntax of a binding statement is:

x=pattern command


The pattern option specifies the file pattern you wish to
bind. For example:

x=*.*      match all files
x=*.h      match all header files
x=*.[ch]   match all files ending in .c or .h
x=*.pict   match all files ending in .pict

Do NOT insert spaces in the pattern.

You use "command" to specify the full pathname of the
command you wish to invoke when a file matching pattern is
double-clicked. 

The name of the matched file is passed to "command" through
the substitution of the @ symbol. For example:

/windows/apps/sedit @ &

To enable text-based applications such as ed to work 
under QNX Windows, you must open a Shell Window for the application. 
In such cases, command would look like this:

/windows/apps/wterm c="ed @" &

Examples of Bindings
--------------------

To enable the editor to work under QNX Windows and to edit 
file groups ending in .c or .h:

x=*.[ch] /windows/apps/wterm c="ed @" &+

To create a binding for the Symbol Editor:

x=*.pict /windows/apps/sedit @ &

To create a binding for the make utility:

x=[mM]akefile /windows/apps/wterm c="make f=@" &

Selecting an Editor

QNX Windows is configured for a default text editor, ed.  If
you wish to use a different editor, you can create a binding
with the following syntax:

e=/windows/apps/wterm c="editor @" &+   (for a text-based editor)

e=editor &+                             (for a QNX Windows-based editor)

where "editor" is the name of the edit utility you're defining.


Selecting a Browse Utility

QNX Windows is configured for a default browse utility,
"more". If you wish to use a different browse utility, you

can create a binding with the following syntax:

b=/windows/apps/wterm c="browse @" &+    (for a text-based browser)

b=browser &+                             (for a QNX Windows-based browser)

where "browser" is the name of the browse utility you're 
defining.


Configuring Printers
--------------------

To print files from QNX Windows, you must configure printer
definitions in the File Manager printer configuration file,
olfm.print. You may specify up to 10 printer definitions.

The File Manager searches for olfm.print files in the 
following order:

/home/fred/windows/olfm.print

/windows/apps/Olfm/olfm.print

The definitions found in these files are "combined" in consecutive 
order (i.e. user definitions will appear before system definitions).

The syntax of a printer definition consists of two
successive lines of text. The first line gives the printer's
meaningful name. This is the name that is displayed when you
select the Print option from the File menu in the File
Manager.

The second line is the print command that sends data to the
printer. The file selected for printing is substituted for
the @ symbol.

Here's an example of a printer definition:

Postscript for Accounting
lp -d hp4.ps @
Text for Accounting
lp -d hp4.txt @

Since the File Manager automatically runs printer commands
in the background, you don't need to specify the ampersand
(&) with printer commands.

