Generic Help for RPS/WWW

This help file is intended to be read by those who are not familiar with RPS/WWW. It is short, so please read it completely.

Warnings, Caveats, Etc.: PLEASE READ THIS ENTRY, IF NOTHING ELSE.
The user of RPS/WWW, REGARDLESS of experience, should develop the habit of saving her/his work often. WWW RPS works as a stateless server (and works ONLY because it is stateless); in other words, no system anywhere is waiting for input from the user. The system responds only to a specific request, the request is handled, and the server then forgets it handled that request. NO backups of any files exist UNLESS THE USER CREATES THEM. Ignore this advice at your peril.
Therefore, if a user is not careful, s/he can wipe out a filled-in form. Save early, save often. Use the 'Save' button at the top or bottom of the FORM, not the browser window button. A good rule: once form appears, NEVER touch the browser buttons without first using the form buttons.
Finally, be certain to save the form as an HTML file, by specifying .html as the extension. Otherwise it will not re-load properly.
Limitations
1. View the Platform support page
There are several "gotcha's" in using X-Mosaic. We list those of which we are aware below.
1. There is an especially vexing bug in X-Mosaic that, thankfully, does not appear often. It may be described as a "permanent field" and it only appears with forms. Once the bug appears, at least one text entry field remains glued in place relative to the window borders. Scrolling does not move the field. As far as we know, the only cure is to save whatever is being worked on, and exit X-Mosaic. One user has stated that using the 'Back' and 'Forward' buttons clears the problem.
  We have one report of a user encountering differences in the file when the file was saved before and after the appearance of the bug. If the bug is encountered, please save the file and send it to:
  rpshelp@athena.gsfc.nasa.gov
2. The user supposedly can tab from field to field. Some users have found that the tab key does not work. The supposed fix: in the .Xdefaults file, enter the following line:
```
Mosaic*keyboardFocusPolicy:   explicit
```
  (note: if 'Mosaic' is left off, ALL X-window applications will respond to the tab key; if this is desirable, then leave 'Mosaic' off).
3. If the borders of the boxes appear "thick" to the point of over-writing the prompts, the user should be aware that the border thickness is an X-window parameter (BorderWidth) in the .Xdefaults file. Decreasing the value of the border width will cure the problem. For example, entering the following line in the .Xdefaults file will set the Mosaic application borders to a width of 2:
```
Mosaic*BorderWidth:   2
```
4. Please do not use the small fonts in the XMosaic options menu. The small fonts foul up the form spacing. The spacing is fine for medium and large fonts.
5. Some users have found that the delete key no longer functions while inside X-Mosaic (back-space continues to work, however). The cure for this annoyance is to enter the following in the .Xdefaults file (enter this EXACTLY as it is written (the amount of white-space is immaterial, but not the backslashes or multi-line entry)):
```
Mosaic*XmText.translations: #override\n\
           osfDelete: delete-previous-character() \n\
           osfBackSpace: delete-previous-character()  
```
```
Mosaic*XmTextField.translations: #override\n\
           osfDelete: delete-previous-character() \n\
           osfBackSpace: delete-previous-character()  
```
Re-loading a saved file
A saved file may be re-loaded by using the "Re-load" button at the top or bottom of the form. A request for an "URL To Open" sub-window will appear. The user should type the name of the file, previously saved, to open. If X-Mosaic has been started from a different directory than the directory in which the file resides, the full path name should be supplied.
Boxes, etc.
The boxes are dimensioned as long and as high as the allowed text for that box. If you find the text scrolling, you've typed too much.
The forms may appear to be mixed up, particularly if you use 'Add Target'. The forms are all re-sorted if you 'Submit' the file or request 'LaTeX' output.
Scrolling, Jump scrolling
The middle mouse button may be used to scroll or jump-scroll down the page. Move the cursor onto the scroll bar (usually on the RIGHT side of the Mosaic environment), hold down the middle mouse button, and move the indicator to the desired location. In addition, the left mouse button, if clicked while the mouse cursor lies within the scroll bar, moves the window down the file a window page at a time.
LaTeX concerns (e.g. LaTeX markups in the Abstract)
The RPS processor prepends all LaTeX special characters, such as $ % # \ with a backslash (\) when generating the LaTeX file. When this file is run through the LaTeX processor, the special characters will be printed as they were entered. If these special characters are intended as LaTeX markups (i.e, a math environment delimited by dollar signs in the abstract field), the prepended backslashes must be removed by editing the LaTeX file before the file is LaTeX'd.
One-line description of each RPS form button (alphabetic order)
- Add Target - Target adding and Cloning Form
- Delete Target - remove a target form - must have set 'delete target' flag at top of the form of the target to be deleted (note: the target numbers will appear to be wrong after a target is deleted: the processor WILL correct this when the LaTeX form is generated)
- Feedback - opens a sub-window for sending comments, complaints, etc. to rpshelp@athena
- LaTeX - obtain the LaTeX version; save after receipt (blank forms may be obtained by using the LaTeX button BEFORE entering any information into the form)
- Reload - Reload previously saved HTML form
- PostScript - obtain the PostScript version of your form.
- Save - save the values entered in the form boxes
- Submit - submit the electronic version to the proposal database - this should be used as the LAST step. The submit button will not appear on the form until after the proposal has been 'verified' successfully.
- Upload - takes you to the upload form which can be used to upload the scientific justification and PostScript forms.
- Verify - send the electronic version for verification

For general RPS interface questions contact the:
RPS Development Team: RPShelp@athena.gsfc.nasa.gov

Satellite-specific questions should be addressed to the relevant satellite GOF.