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 & Motif
  SQL*Menu V5.0.11/Character Mode & Motif
  Oracle*Terminal V1.0.9/Character Mode

  There are a couple of bug fixes that are not generally available yet that
  we found necessary to include in the X and Motif libraries.

  IMPORTANT NOTE:

  ************************************************************************
  ************************************************************************  
    
    We do NOT provide the libX11.a, libXt.a, libXm.a libraries anymore
    under the $ORACLE_HOME/mprodins directory.
    
    You should link the Motif executables of sqlforms30/sqlmenu50 with
    the Openwindows 3.0 libraries from SUN Microsystems in order to get 
    the libX11.a and libXt.a libraries (directory pointed by OPENWINHOME
    in the sqlforms30.mk and sqlmenu5.mk files).
    
    You should also have a copy of the libXm.a library under the directory
    pointed by the MOTIFHOME environment variable. We advise you to use 
    the /usr/lib directory.
    
    Before applying the patch and relinking the Motif products, make sure 
    that there is a copy of libXm.a that contains the fix for OSF bug P2628.
    This bug is fixed in Motif 1.1.2.
  
  ************************************************************************  
  ************************************************************************
 
2.  REQUIREMENTS
 
  This tape was meant to be installed on top of the 6.0.32 core release.
  The 6.0.32 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 "mprod.setup" file from the tape:

	  $ tar xvf /dev/<tape device name> -C ./mprodins/install mprod.setup

  d)	Shutdown the database.

	  $ sqldba shutdown

  e)	Move to the mprodins install directory:
									
	  $ cd $ORACLE_HOME/mprodins/install

  f)	Run "mprod.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 mprodins install directory again:

	  $ cd $ORACLE_HOME/mprodins/install

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

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

	IMPORTANT:
	IF YOU CHOOSE TO RELINK THE MOTIF VERSIONS OF SQL*FORMS30 OR 
	SQL*MENU50, MAKE SURE YOU DO SO WITH THE OPENWINDOWS 3.0 LIBRARIES. 
		
  k)    Become superuser (root) on your system. Move the file XKeysymDB
        from the orakit install directory to the directory /usr/lib/X11.
        If the file /usr/lib/X11/XKeysymDB already exists, either rename it,
        or merge its contents with the contents of the provided XKeysymDB. 

	  $ mv $ORACLE_HOME/orakit/install/XKeysymDB /usr/lib/X11
	  $ chgrp bin /usr/lib/X11/XKeysymDB
	  $ chown bin /usr/lib/X11/XKeysymDB

  l)	Copy either sun_mit or sun_news, according to which X server you are 
	running, as .motifbind to your home directory on the machine where you 
	run mwm.

	If mwm is running on a local machine:

	  $ cp $ORACLE_HOME/mprodins/<filename> ~/.motifbind

	If mwm is running on a remote machine, use a remote file transfer
	facility such as rcp or ftp to copy the file over.  Contact your local
	system administrator if you have problems doing this.
	  
	RESTART THE X SERVER.

	Note:	The file .motifbind contain mappings between OSF "virtual" 
		keysyms and their platform-dependent equivalents.  It gets 
		loaded into the server when you start up mwm.  Sun_mit is for 
		a Sun server with MIT Bindings with a type 4 keyboard, and 
		sun_news is for an OpenWindows 1.0.1 Server for a Sun-4 with a
		type 4 keyboard.


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

  IMPORTANT: 
  IF YOU ARE USING THE X11R4 SERVER, YOU SHOULD START THE SERVER WITH BACKING 
  STORE TURNED OFF.  This can be done by calling xinit with the -bs option.  

  There is a file, ".xmodmaprc", that is moved to $ORACLE_HOME by the install
  script.  This file enables the "META_L" (left Meta key).  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.

  THE "Meta" KEY (shaped like a diamond, located on the left side of the 
  spacebar) ON THE SUN KEYBOARD IS THE EQUIVALENT OF THE "Alt" KEY USED 
  WITH ACCELERATOR KEYS.  The actual "Alt" key (located next to the "Caps Lock"
  key) does nothing.  Either use the "Meta Key" or use the utility "xmodmap"
  (See the man pages) to redefine the actual "Alt" key to be the "Meta" key.

  Motif version executables (see $ORACLE_HOME/bin) all begin with
  the "m" character (e.g. msqlforms30).


6.  VARIANCES FROM OSF/MOTIF STYLE GUIDE

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

  1) The style guide specifies that, when a primary window is minimized or
     iconified, its secondary windows are temporarily removed from the display,
     and restored when the primary window is restored. SQL*Forms/Motif and
     SQL*Menu/Motif do not currently do this.

  2) The mouse pointer shape should change to an hourglass or watch design
     to indicate that the application is "working" on a user request. 
     Currently, SQL*Forms 3.0/Motif and SQL*Menu 5.0/Motif display the 
     "Working..." status line message to convey this information.

  3) 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.

  4) In most Motif Text, when you highlight (drag-select) a piece of text, 
     hitting backspace will wipe out the previously existing text. 
     In the forms/menu text controls, this doesn't work.  However, the
     highlighted text can be erased by using the Cut menu item or key 
     equivalent.


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

  1) Menu items

     The top menu bar layout in SQL*Forms 3.0/Motif (Design) and in 
     SQL*Menu 5.0/Motif (Design) has been modified for compliance with the
     OSF/Motif Style Guide. 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 OSF/Motif applications. The 
     last item on this menu is labeled "Exit" rather than "Quit", for the same
     reason.

  1.2) Menu bar buttons

     The OSF/Motif Style Guide specifies that the top menu bar be populated
     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 Motif 
     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 Motif, 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.

     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

     OSF/Motif provides two different methods for gaining access to menus using
     the keyboard only: mnemonics, and the [Menu] key.

  2.2.1) Mnemonics

     To display a pulldown menu using its mnemonic, hold down the <Alt> key and
     then press the letter that is underlined in the menu's label. (In 
     character mode, you would instead press the letter that is capitalized in 
     the menu label).

     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 
     <Alt> key is not required).

     On HP keyboards, the <Alt> key is labeled "Extend char"; on Sun keyboards,
     it is the diamond shaped key to the left of the spacebar (unfortunately, 
     the key labeled "Alt" does nothing). Other vendors may have their own 
     conventions.

  2.2.2) Using the [Menu] key

     Alternatively, you can press the [Menu] key (which is mapped to F10 on 
     most keyboards). This highlights the leftmost item in the menu bar. You 
     can then use the arrow keys to move around in the menu hierarchy; at any 
     given time, the currently selected item is highlighted. When you reach the
     desired item, press the <Return> key. If you change your mind and don't 
     want to run a command from the menu, just hit the <Escape> key.

     You can also combine these methods; i.e. press the [Menu] key to go to the
     menu bar, then press a mnemonic letter to select a particular item.

  2.3) Scrolling

     The preferred method for scrolling hidden data into view is to use the
     scrollbars. Consult the "OSF/Motif User's Guide" if you are unfamiliar 
     with the way scrollbars operate in Motif. 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. Motif supports a 
     similar capability; 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 Motif 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.

  5) Messages

     In the Motif 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/Motif (Design) and SQL*Menu/Motif 
     (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 Motif 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 pressing <Return> or clicking on the "OK" button) before
     you 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/Motif 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/Motif 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 Motif (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 MOTIF WIDGETS

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

  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 4 ways:

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

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

  2.) Copying Orakit to each users home directory.

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

  4.) Have each user set XENVIRONMENT to the full path name of the Orakit 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 "moraterm.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.
********

  Although moraterm.r may be edited with the character mode version of 
  Oracle*Terminal, the following is a list of key mappings that should NOT
  be changed:

  Same across all platforms:

  Help            F1
  MenuBar         F10
  Next Field      Tab
  Exit/Cancel     Escape
  Prev Field      (Shift-)BackTab (HP) or Shift-Tab

  Fixed for particular platforms:

  Function        HP              Sun             Dec
  --------        --              ---             ---
  Backspace       BackSpace       BackSpace       Delete
  BOL             Home            F27             Alt-Left
  EOL             F7              R13             Alt-Right
  Cut             Shift-DelChar   F20             Shift-Remove
  Copy            Ctrl-InsChar    F16             Ctrl-Insert
  Paste           Shift-InsChar   F18             Shift-Insert
  Undo            Alt-BackSpace   F14             Alt-BackSpace
  Select          Select          Ctrl+Space      Select
  ScrollUp        Prev            F29             Prior
  ScrollDown      Next            F35             Next



  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:		Motif Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/moraterm.r
	Invoke Command:	% msqlmenu50

******************************** 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:		Motif Mode
	Environment:	xterm window on a Sun-4 machine
	Resource file:	$ORACLE_HOME/forms30/admin/resource/moraterm.r
	Invoke Command:	% msqlforms30

  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 Motif bitmapped products is 
  included that can be edited using the character mode version of 
  Oracle*Terminal.  The resource file that can be edited is moraterm.r, 
  the default resource file for all Motif bitmapped products on this tape.

  Before you change the keymappings for the Motif 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 Motif; 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.
