Release Notes for Orakit Products Distribution for V6.0.32
For SunOS 4.1.1 on Sun4/Sparc
April 15, 1992


1.  CONTENTS

  This tape contains new versions of the following products:

  SQL*Forms V3.0.16/Character Mode & OpenLook
  SQL*Menu V5.0.11/Character Mode & OpenLook
  Oracle*Terminal V1.0.9/Character Mode


  IMPORTANT NOTE:
 
  ************************************************************************
  ************************************************************************
  
   THIS PATCH REQUIRES LINKING THE OPENLOOK VERSION OF SQLFORMS30/
   SQLMENU50 WITH THE OPENWINDOWS 3.0 LIBRARIES CONTAINING PATCH 
   100451-09 FROM SUN MICROSYSTEMS. Note that the OpenLook versions of 
   the orakit, forms30 and menu5 libraries provided in this patch will 
   NOT work with the OpenWindows 2.0/2.5 libraries.

   We do not provide the libX11.a, libXt.a, libXol.a libraries anymore
   under the $ORACLE_HOME/olprodins directory.
   
  ************************************************************************
  ************************************************************************ 

2.  REQUIREMENTS
 
  *************************************************************************
  *************************************************************************
  It is assumed that users are familiar with the features of SUN 
  Microsytems' Open Windows with its OPEN LOOK GUI.  If questions arise 
  about the use of SQL*Forms 3.0 or SQL*Menu 5.0 built with the Open Look 
  Interface Toolkit, please first consult the Open Windows and Open Look 
  manuals before calling Oracle, unless it is an obvious Oracle product 
  problem.
  *************************************************************************
  *************************************************************************

  This tape was meant to be installed on top of the 6.0.32 core release.
  The 6.0.32 core tapes are to have been installed in the normal manner 
  as described by the relevant documentation.  The products on this tape 
  are to be installed following the installation of the 6.0.32 database.  
  Do NOT attempt to install the products on this tape in any other manner 
  than what is described in the next section, "Installing the Tape".  
  Do NOT attempt to install the products by going to the install directory 
  of each product and running the individual install scripts. 
  

3.  INSTALLING THE TAPE

  Make sure you have at least 54 Megabytes of disk space available to
  load this tape.

  To install the tape, follow these steps:

  a)	Login under the "oracle" OS account with "dba" as the group.

  b)	Move to the ORACLE_HOME directory:

	  $ cd $ORACLE_HOME

  c)	Execute the "tar" command to get the "olprod.setup" file from the tape:

	  $ tar xvf /dev/<tape device name> -C ./olprodins/install olprod.setup

  d)	Shutdown the database.

	  $ sqldba shutdown

  e)	Move to the olprodins install directory:

	  $ cd $ORACLE_HOME/olprodins/install

  f)	Run "olprod.setup".  This is a shell script that renames existing 
	executables and directories so that they will not be destroyed when
	the tape is loaded.

  g)	Move to the ORACLE_HOME directory again:

	  $ cd $ORACLE_HOME

  h)	Use "tar" to load the entire tape:

	  $ tar xvf /dev/<tape device name>

  i)	Move to the olprodins install directory again:

	  $ cd $ORACLE_HOME/olprodins/install

  j)	Run "olprod.install".  This is a shell script that:

	-  installs Orakit.
	-  installs SQL*Forms 3.0 OpenLook and character mode.
	-  installs SQL*Menu 5.0 OpenLook and character mode.
	-  installs Oracle*Terminal character mode.

  *************************************************************************
  *************************************************************************
	IMPORTANT:
	IF YOU CHOOSE TO RELINK THE OPENLOOK VERSIONS OF SQL*FORMS30 OR 
	SQL*MENU50, MAKE SURE YOU DO SO WITH THE OLIT LIBRARIES PROVIDED
        BY OPENWINDOWS 3.0.   
  *************************************************************************
  *************************************************************************

4.  ERRATA

  Please carefully read the ERRATA file contained in this directory.  It 
  contains restrictions and workarounds that are useful to the user.


5.  NOTES

  - Mouseless Support/Widget Traversal:

  Please consult the "OPEN LOOK GUI User's Guide" for information about 
  how to use mouseless support/widget traversal.  

  The file, ".xmodmaprc", located in $ORACLE_HOME/olprodins, is moved to 
  $ORACLE_HOME by the install script.
  This file enables  "Meta_L", "Meta_R", and "Alt_L" (Meta left,
  Meta right, and Alt left keys, respectively).  It is put into
  use by typing "xmodmap .xmodmaprc" in $ORACLE_HOME.  It is recommended that
  ".xmodmaprc" be put in each user's home directory and the command 
  "xmodmap .xmodmaprc" be put in each user's .login, .profile, or .cshrc file.
  See the next Section, "VARIANCES FROM OpenLook STYLE GUIDE" for more 
  information.

  - OpenLook version executables (see $ORACLE_HOME/bin) all begin with
  the "ol" character (e.g. olsqlforms30).

  - Font Sizes, Types, and Geometry Management:

  Font sizes (set in OlOrakit and oloraterm.r files) should not exceed 12 
  point.  This is because SQL*Forms V3.0 and SQL*Menu V5.0 does not scale 
  its objects to the font used.  Fonts larger than 12 point will cause text 
  to disappear in text fields and other unpredictable results.

  Font types should also be chosen carefully.  The Normal attribute (both in
  oloraterm.r and OlOrakit) should be left as it is, a fixed length font.  
  SQL*Forms V3.0 and SQL*Menu V5.0 scales everything off of this font.  Using
  a proportional space font will cause problems such as abnormally large 
  windows and non-aligned text.  SQL*Forms V3.0 and SQL*Menu V5.0 assumes 
  fixed width fonts and calculates positions, sizes, locations based on that
  assumption.  Because we are using OLIT widgets, which do their own 
  geometry management, we are able to use proportional spaced fonts in many
  places, but the restrictions outlined here still remain.

  - Modality:

  Modality is the grabbing of the input focus by a particular object and not
  relinquishing it until a desired action is performed.  There are 2 main types
  of modality, 1) System modality and 2) Application modality.  In System 
  modality, nothing can be done in any other window on the screen until the
  desired action is performed.  With Application modality, nothing can be done
  in any other window belonging to the application that owns the modal window.
  The user can move the focus to another application.  Sun/Open Look has 
  chosen Application Modality for this version.

  - There is no National Language support in the version of the OPEN LOOK
  INTERFACE TOOLKIT (OLIT) contained in this release.


6.  VARIANCES FROM OpenLook STYLE GUIDE

  The user interface for SQL*Forms 3.0/OpenLook and SQL*Menu 5.0/OpenLook has
  been, wherever possible, made to conform with the OpenLook Style Guide.
  The following are the known variances from the guidelines:

  1) The up and down arrow keys don't have their expected meaning in a 
     multiline text field that is part of a spread table or definer form 
     window. Instead of moving the insertion cursor up or down a line in the 
     text field, they act as [Previous Record] and [Next Record] keys.

  2) Mouseless Support/Widget Traversal:

     OpenLook's Mouseless Support/Widget Traversal was designed to allow 
     users to move through widgets and select them with only the keyboard.
     However, at this stage of OpenLook (version 2.5), it is still immature
     and buggy.  Please carefully read the ERRATA file contained in this 
     directory for a list of problems you will encounter.  The following is 
     a list of variances from the OpenLook's Mouseless Support/Widget Traversal
     that were made so that the user would not be confused and that SQL*Forms
     V3.0 and SQL*Menu V5.0 would function correctly and as users of these
     products are used to.

     - The 'tab' key is used for the 'next field function' in SQL*Forms 3.0 and
     SQL*Menu 5.0.  The tab key is normally used to move from widget to widget
     IN OpenLook applications.  Where necessary, the widget to widget traversal
     has been disabled, so as not to confuse the user.  Where possible, it 
     has been left intact for the user's convenience.

     - Mouseless support has been turned off in the top menu bars.  The 'tab'
     key, which is the 'next field' function in SQL*Forms, is overridden by 
     OpenLook's mouseless support and if enabled in the top menus, would cause
     the focus to leave the text fields and go up to the top menu.  Thus the 
     user would have to tab forward through all the top menu items to return
     to the screen text fields.  Disabling the mouseless support has a side 
     effect discussed the ERRATA file. 

     ** This can be turned on again by removing the following 2 lines in the 
	OlOrakit file:
	
	OlOrakit*topmenu*traversalManager:  False
	OlOrakit*topmenu*traversalOn:       False

     *** CAUTION!! Do so with extreme care because now the next field function
         of SQL*Forms will not function as it was meant to!!!!

  3) The Open Look Clipboard

     SQL*Forms and SQL*Menu designer - The user can use the clipboard to 
     to cut and paste to and from shelltool/commandtool windows amd the 
     designer.  Selecting text and then dragging it with the mouse
     does not work.  Both the clipboard and dragging selected text works 
     within the designer.  An "Edit" top menu item that functions just like
     the Clipboard within SQL*Forms and SQL*Menu is provided.

     Runform - Because Forms must process the data within its fields for
     validation purposes, and must trap events so that triggers may be fired,
     neither the Clipboard nor dragging selected text works. However, an 
     "Edit" top menu item that functions just like the Clipboard within 
     SQL*Forms and SQL*Menu is provided. 


7.  VARIANCES FROM CHARACTER MODE SQL*FORMS AND SQL*MENU

  1) Menu items

     The top menu bar layout in SQL*Forms 3.0/OpenLook (Design) and in 
     SQL*Menu 5.0/OpenLook (Design) has been modified. The following issues 
     were addressed:

  1.1) File menu

     The leftmost pulldown menu on the top menu bar is labeled "File" rather 
     than "Action", for consistency with other OpenLook applications. The 
     last item on this menu is labeled "Exit" rather than "Quit", for the same
     reason.

  1.2) Menu bar buttons

     Most applications' top menu bars contain menubuttons with pulldown menus, 
     not buttons. Thus, the "Trigger" and "Procedure" items, which are buttons 
     in character mode SQL*Forms 3.0, have been placed under a new menu called 
     "Code". The "Options" menu item is under its own pulldown menu, called 
     "Options".

     The online help system windows have been completely redesigned so that the
     "Exit", "Index", "History", etc. buttons are separated, rather than
     being part of a top menu bar.

  1.3) Help menu

     The "Help" pulldown menu is always the rightmost item in the top menu bar.

  1.4) New pulldown menus

     For the sake of convenience as well as consistency with OpenLook
     look-and-feel, two new items have been added to the top menu bar. The 
     "Edit" menu provides cut, copy and paste functions for editing text, as 
     well as for moving objects about in the screen painter. The "View" menu 
     provides functions for switching between a definer form view of a form, 
     page, block, field, trigger or procedure, and the corresponding spread 
     table view.

  2) Navigation

  2.1) Between fields

     In SQL*Forms 3.0 Character Mode, the primary means of navigating from one
     field to another in a form or spread table are the <Return> and <Tab> 
     keys, which are almost interchangeable. In OpenLook, the <Return> key 
     often has different meanings; for instance, in a push button or check box,
     hitting the <Return> key has the same action as clicking the mouse on
     the button or check box. It is better to use the <Tab> key exclusively for
     moving from one field to the next.  Also see the sections in the ERRATA 
     and README files on Mouseless Support/Widget Traversal.

     It is often easier to use the mouse to move to a field, button or checkbox
     directly; simply place the mouse pointer over the object where you want to
     be, and click the left mouse button. Triggers such as Pre-Field and 
     Post-Field should work as expected, as if you had used the <Tab> key to 
     leave one field and enter the next.

  2.2) In the top menu bar

     OpenLook provides two different methods for gaining access to menus using
     the keyboard only: mnemonics, and the mouseless key.

  2.2.1) Mnemonics

     A menu cannot be pulled down using mnemonics.  To pull down a menu use the
     right mouse button or use mouseless support.  Using a mnemonic to select 
     a top menu button invokes the default pulldown menu option -- it is the 
     same as pressing the left mouse button.  To use a mnemonic on a top menu 
     item, hold down the <Meta> key (shaped like a diamond, to the left of the 
     spacebar) and then press the character underlined in the item name.

     Once a pulldown menu is displayed, you can select an item from it by 
     typing the letter that is underlined in the item name. (This time, the 
     <Meta> key is not required).

     IT IS RECOMMENDED THAT THE USER USE THE RIGHT MOUSE BUTTON TO POP DOWN 
     MENUS.

  2.2.2) Mouseless Support

     Mouseless support is turned off for the top menu items at this point to 
     avoid confusion with the 'nextfield' function in forms and menu.  The tab 
     key is used by mouseless support to move from widget to widget.  Thus a 
     user would press the tab key until the focus is on a top menu button, 
     then press <Alt-Spacebar> to pull the menu down.  Then a user can tab or 
     arrow key up or down the menu to get to the desired item.  An item is then
     selected by hitting the spacebar.  The pulldown menus DO have mouseless 
     support turned on.  If a user really desires the use of mouseless support 
     in the top menu and is willing to put up with the confusion with forms' 
     'nextfield' (tab key also), see the README and ERRATA files for a 
     description of how to do so.

     IT IS RECOMMENDED THAT THE USER USE THE RIGHT MOUSE BUTTON TO POP DOWN 
     MENUS.

  2.3) Scrolling

     The preferred method for scrolling hidden data into view is to use the
     scrollbars. Consult the "OpenLook GUI User's Guide" if you are unfamiliar 
     with the way scrollbars operate in OpenLook. Whenever the documentation 
     refers to using the [Scroll Up] and [Scroll Down] keys to move between 
     pages of data, remember that you can get the same result (often much 
     faster) by using the mouse to manipulate the scrollbars.

  3) Selection

     In SQL*Forms character mode, selection of items in a list is done by using
     the arrow keys to move up and down the list, and pressing the [Select]
     function key to mark items selected or unselected. OpenLook supports a 
     similar capability; first hit the tab until the top item has the focus, 
     then use the arrow keys to move up or down the list and use the Spacebar 
     to select or unselect and item. However, selection can usually be done 
     much more efficiently using the mouse, simply by clicking on the items to 
     be selected.

  4) Text fields and editing

     In SQL*Forms (Design) and SQL*Menu (Design), replace or overstrike mode is
     not currently supported. In Runform and Runmenu, it is; you can toggle
     between insert and replace mode with the [Insert/Replace] function key,
     as in character mode.

     All OpenLook text fields support a feature called "pending delete": you 
     may select a block of text by holding down the left mouse button and 
     "dragging" the mouse over the desired area. If you then begin typing, the
     selected text disappears and your new text replaces it.

     To insert new text, simply place the mouse pointer at the desired 
     insertion point, click the left mouse button, and begin typing.

     Cut, copy and paste operations are now supported, using either the 
     pulldown "Edit" menu, or function keys. Note, however, that you cannot 
     cut text from (or paste text into) an inactive field. "Inactive" in this 
     context refers to any field not on the currently active row in a spread 
     table, or any field other than the current one in Runform/Runmenu.

     See the Sections on the OpenLook Clipboard in the README and ERRATA files 
     for rules on using the Clipboard in the Designer and Runform.

  5) Messages

     In the OpenLook applications, warnings and error messages that require
     acknowledgement are displayed in separate windows called alert boxes. To
     proceed with the application, you must click the mouse on the "OK" button
     in the alert box.

  6) Help system

     As with character mode, SQL*Forms/OpenLook (Design) and SQL*Menu/OpenLook 
     (Design) provide a hypertext-based online help system. Each screen of 
     help information contains a number of highlighted keywords. To get more 
     information about a particular keyword or topic, simply click on the 
     keyword with the mouse.

  7) Show Keys

     In the character mode applications, [Show Keys] pops up a window which is
     both context-sensitive and modal: that is, it only shows the keymappings
     for functions that are applicable to the current context, and it requires
     that you acknowledge (and thereby remove) the window in order to proceed.

     In the OpenLook products, there are two versions of the Show Keys window.
     One appears when you press [Show Keys] or select the "Help/Show Keys" main
     menu item from a primary application window. This window need not be
     acknowledged or hidden; thus it can be kept on the screen for handy 
     reference.

     The other type of Show Keys window is useful when you are in a dialog or
     list-of-values window that requires acknowledgement (a "modal" window).
     In this situation, all your other application windows, including the
     "modeless" Show Keys window, are "frozen out"; even the scrollbars are
     insensitive to mouse or keyboard input. If you press [Show Keys] in this
     case, a new "modal" Show Keys window pops up. This window must be
     acknowledged ( by unpinning it) before the user can proceed.


     Both kinds of Show Keys windows display all the keymappings for your
     application. Mappings for keys that were inapplicable ***at the time
     you popped up the window*** are greyed out, but not made completely
     invisible. At any time, you may press [Show Keys]to update the contents 
     of a modeless Show Keys window; this will grey out any mappings that have 
     become inapplicable, and un-grey those which are now relevant.

  8) Screen painter

     The screen painter in SQL*Forms 3.0/OpenLook is similar to the character 
     mode version, with the addition of mouse navigation. Fields, boilerplate 
     text and graphics are aligned on a character-cell grid, so that the forms 
     you design with SQL*Forms 3.0/OpenLook can be run on character terminals 
     with only slight modifications.

     Note that, in the screen painter, the mouse only substitutes for the
     navigation keys; you still need to use the [Select] function key to
     mark the corners of an area to cut out and paste somewhere else, or to
     draw a box. For example, this is how you would draw a box:

	1. Move the mouse pointer to the upper-left corner, click there, and
	   press the [Select] key.
	2. Move to the lower-right corner, click, and press [Select].
	3. Press the [Draw Box/Line] key.


     Also note that, in the screen painter, boilerplate text is laid out on a
     strict one-character-per-cell basis. This means that, if you use a 
     proportional font for boilerplate text, it will look "funny" in the 
     screen painter. Use a fixed-width font if you find this bothersome. In 
     any case, the text will appear normal when you actually run the form.

  9) Pop-up windows

     In character mode, pop up windows can easily be placed where a user would 
     like them to be placed.  Since there is only one window, pop-ups can be 
     very effective in creating a virtual form from a number of pop-ups.

     In OpenLook (and any of the bitmapped versions), pop-ups appear as 
     separate windows and appear with window manager wrappers around them. 
     The dimensions of the pop-up window can be customized using the Page Size
     characteristics.  Unfortunately, the initial window will also appear
     together with the pop-up window.  Also, the pop-up window cannot be 
     guaranteed precise placement, as the window manager has the final say in 
     where windows are placed.  Thus, the effect that is achieved in character 
     mode is not done very well in the bitmapped version.  The users are 
     encouraged NOT to use this option.  This is one of the few changes that 
     will have to be made to applications developed in character mode in order 
     to have them run properly in a bitmapped environment.


8.  ORAKIT APPLICATION RESOURCE FILE FOR OPENLOOK WIDGETS

  During the installation, depending on your monitor type, the Orakit 
  application resource file, either "OlOrakit.color" or "OlOrakit.mono",
  is copied from $ORACLE_HOME/orakit/install to $ORACLE_HOME as "OlOrakit".  

  This file is of the same format as your .Xdefaults file and is necessary for
  the proper look of SQL*Forms 3.0 and SQL*Menu 5.0.  This file is fully 
  commented and we urge the user to read this file before using SQL*Forms or
  SQL*Menu.  

  It can be used in any of 5 ways:

  1.) load it into the X resource database by typing:

      % xrdb -merge OlOrakit (or complete path to the OlOrakit file).

  2.) Copying OlOrakit to each users home directory.

  3.) Copying OlOrakit to the /usr/lib/X11/app-defaults directory.

  4.) Have each user set XAPPLRESDIR to the directory where the OlOrakit file
      is located.

  5.) Have each user set XENVIRONMENT to the full path name of the OlOrakit 
      file, including the file name.   


9.  TERMINAL DEFINITION RESOURCE FILES

********
  IMPORTANT NOTE: The default oracle resource file read by SQL*Forms30 and 
  SQL*Menu50 is "oloraterm.r", located in $ORACLE_HOME/forms30/admin/resource.
  In order for SQL*Menu to find this file, the environmental variable 
  MENU5PATH must be set to this directory. Oracle*Terminal must have the
  environmental variable ORATERMPATH also set to 
  $ORACLE_HOME/forms30/admin/resource in order to find the resource files
  listed below.
********

  The following is a list of terminal definition resource files that are used
  when invoking the products included in this tape.

******************************* Oracle*Terminal *******************************

	Product: 	Oracle*Terminal
	Mode:		Character Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermsun.r
	Invoke Command:	% oraterm -c xtermsun:otsun

	Product: 	Oracle*Terminal
	Mode:		Character Mode
	Environment:	xterm window on an NCD vt220 Ultrix configured
			X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% oraterm -c xtermncd:ncd220

	Product: 	Oracle*Terminal
	Mode:		Character Mode
	Environment:	xterm window on an NCD N101 configured X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% oraterm -c xtermncd:ncd101

******************************** SQL*Menu50 ***********************************

	Product: 	SQL*Menu50
	Mode:		Character Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermsun.r
	Invoke Command:	% sqlmenu50 -c xtermsun:sun


	Product: 	SQL*Menu50
	Mode:		Character Mode
	Environment:	xterm window on a Sun-4 machine using Universal
                        Terminal Definition.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/sunu.r
	Invoke Command:	% sqlmenu50 -c sunu:UTD

	Product: 	SQL*Menu50
	Mode:		Character Mode
	Environment:	xterm window on an NCD vt220 Ultrix configured
			X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% sqlmenu50 -c xtermncd:ncd220

	Product: 	SQL*Menu50
	Mode:		Character Mode
	Environment:	xterm window on an NCD N101 configured X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% sqlmenu50 -c xtermncd:ncd101

	Product: 	SQL*Menu50
	Mode:		OpenLook Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/oloraterm.r
	Invoke Command:	% olsqlmenu50

******************************** SQL*Forms30 **********************************

	Product: 	SQL*Forms30
	Mode:		Character Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermsun.r
	Invoke Command:	% sqlforms30 -c xtermsun:sun

	Product: 	SQL*Forms30
	Mode:		Character Mode
	Environment:	xterm window on a Sun-4 machine using Universal
                        Terminal Definition.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/sunu.r
	Invoke Command:	% sqlforms30 -c sunu:UTD

	Product: 	SQL*Forms30
	Mode:		Character Mode
	Environment:	xterm window on an NCD vt220 Ultrix configured
			X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% sqlforms30 -c xtermncd:ncd220

	Product: 	SQL*Forms30
	Mode:		Character Mode
	Environment:	xterm window on an NCD N101 configured X-terminal.
	Resource file:	$ORACLE_HOME/forms30/admin/resource/xtermncd.r
	Invoke Command:	% sqlforms30 -c xtermncd:ncd101

	Product: 	SQL*Forms30
	Mode:		OpenLook Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/oloraterm.r
	Invoke Command:	% olsqlforms30


  The following is a list of sample scripts found in the 
  $ORACLE_HOME/orakit/install directory that can be used to invoke the 
  character mode versions of the included products.  Each script creates its 
  own xterm window and brings up the product in that window.  They are ONLY 
  SAMPLE SCRIPTS and are only meant as convenient guidelines.  Feel free to 
  edit and use them BUT THEY ARE NOT SUPPORTED.

	iapsun	 - runs runform30
	iapsunu	 - runs runform30 using Universal Terminal Definition

	iadsun	 - runs sqlforms30
	iadsunu	 - runs sqlforms30 using Universal Terminal Definition

	menusun	 - runs sqlmenu50 
	menusunu - runs sqlmenu50 using Universal Terminal Definition

	otsun	 - runs oraterm


10. ORACLE*TERMINAL AND BITMAPPED RESOURCE FILES

  The version of Oracle*Terminal included in this tape is character mode.  It 
  is intended to be used to edit character mode resource files only.  However,
  a specially edited resource file for the OpenLook bitmapped products is 
  included that can be edited using the character mode version of 
  Oracle*Terminal.  The resource file that can be edited is oloraterm.r, 
  the default resource file for all OpenLook bitmapped products on this tape.

  Before you change the keymappings for the OpenLook products, however, you 
  should read the section of the release notes regarding "Customizing 
  Keymappings". There are a number of restrictions which apply to keymappings 
  for OpenLook; failure to obey them may render your application unusable.

  It is strongly advised that anyone editing these files make backup copies
  beforehand!

  DISCLAIMER:  THIS IS NOT SUPPORTED!!! IT IS ONLY INTENDED AS A CONVENIENCE
  FOR USERS UNTIL A BITMAPPED VERSION OF ORACLE*TERMINAL IS AVAILABLE.  DO NOT
  CALL WORLDWIDE SUPPORT TO SUBMIT BUGS OR TO ASK FOR HELP USING THIS OPTION.
