inputs

The <INPUT> tag is used in forms and allows interaction with the httpd server.

There are severeal types of input tags:

INPUT - buttons and textboxes.
textarea - multi line input fields
isindex - predefined form useful for searching.
select - list and menu selection.

Creates an input field in a form. NAME must be present for all types of inputi except submit and reset

TYPE can be one of

>image
This is not supported by Mswindows Mosaic.
checkbox
can be toggled on and off.
submit
calls the action specified in the form.
password
like a text input, but all input is represented by asterixs not Obelisks
radio
radio buttons. Input fields with the same NAME field. only one radio button of the same NAME can be checked at any time.
reset
clears all the fields in the form.
text
*default* an input field

Plain input field

  <form>
    <input NAME="From">
  </form>

text areas
On Xmosaic, the SIZE parameter is interpreted as a textarea. This is ignored in Mosaic for Windoze and proper TEXTAREAS should be used.

This wont work under Windoze

 ROWS=5 COLS=30 ALIGN=middle

This will work under windoze

<TEXTAREA ROWS=5 COLS=30 ALIGN=middle>            </pre>
</dl>


<hr>
<a name=input_submit><b>submission buttons</b></a>
<pre>
 Type="submit"<br>
 <input value="submit" Type="submit">
</pre>

<hr>
<a name=input_reset><b>reset button</b></a>
<pre>
 Type="reset"<br>
 <input value="reset" Type="reset">
</pre>

<hr>
<a name=input_check><b>check boxes</b></a>
<pre>
 Type=checkbox<br>
 <input name=check Type="checkbox" value="check">
 <input NAME=check value="check2" Type=checkbox checked>
</pre>

<hr>
<a name=input_radio><b>radio buttons</b></a>
<pre>
 Type=radio<br>
 <input name=radio Type=radio value="radio"><input NAME=radio value="radio2" Type=radio checked>
</pre>

<hr>
<a name=input_passwd><b>password box</b></a>
<pre>
 Type=password<br>
 <input name=password Type=password value="passwd">
</pre>
</form>

<HR>
<a name=select><LI><select [MULTIPLE]>...</select><P></a>
This creates a pull-down menu containing <a href=#option>Options</a>
in a <a href=#form>form</a>.
<p>
<dt>single select
<dd>
<pre>
  <form>
  <select NAME="direction">
  <OPTION SELECTED> North
    <OPTION> East
    <OPTION> South
    <OPTION> West
  </select>
</form>
</pre>
<dt>multiple single (use ctrl-click to select)
<dd>
<pre>
  <form>
  <select NAME="direction" MULTIPLE >
  <OPTION SELECTED> North
    <OPTION> East
    <OPTION> South
    <OPTION> West
  </select>
</form>
</dl>

produces:
<form>
  <select NAME="direction">
    <OPTION SELECTED>North
    <OPTION >East
    <OPTION>South
    <OPTION>West
  </select>
  <select NAME="direction" MULTIPLE>
    <OPTION SELECTED>North
    <OPTION >East
    <OPTION>South
    <OPTION>West
  </select>
</form>

<HR>
<a name=isindex><LI><isindex><P></a>
This is probably the oddest tag. When I first saw it, I though that it provided
a free text searching capability on a set of documents.
<p>
What it actually does is to provide a ready built form (standardisation and
all that), all you have to do is provide the processing at the server end. 
<p>
<isindex action=files/search.sh>
Note: <i>on Xmosaic the isindex form is inlined, on MSwindows the form appears
at the bottom of the screen... wierd!!</i>

<hr>
<a name=txt><LI><textarea [rows=<i>rows</i>] [cols=<i>cols</i>]><P></a>
This allows us to put
a panel of text in a <a href=#form>form</a>

<form>
<textarea rows=5 cols=30>
 this is a text area,  this is
 area, this is a text area, th
 a text area, this is a text


in Xmosaic, the text is shown within the text area.