||Title||This text will be placed within the browser window title bar. This item can contain a DIRT tag.|
|<10.2>||Form action||This is the name of the script (CGI/ISAPI/Other) that the page form will be handed to. This item is usually blank as the system automatically inserts the name of the "dll" that was used to invoke the page. This item can be changed to invoke other scripts, or to add "#" markers for page positioning.|
|<10.3>||Background image||Specify the URL of an image to be displayed as the background for the page. This image will be "tiled" (repeated to the right and bottom).|
Default page text color. HTML based colors are defined either as color
names (for the most well known colors like "black",
"white", "red") or defined as a mix of Red Green and
These amounts are defined in Hex (00 - FF) where 00 is the least amount of each color and FF is the most. The color sets are combined as an HTML color reference as follows: #FFFFFF (where the first byte - FF - defines the red color, the second byte defines green and the last byte defines blue).
The "#" is required for these types of color definitions. Complete information on HTML colors can be found within the HTML specification at World Wide Web Consortium
|<10.5>||Background color||Page background color. This option will be overridden by the background image option.|
This is the color that will be applied to items within the
|<10.7>||Visited link color||This is the color that will be applied to linked items (as defined above) that have been visited.|
|<10.8>||Active link color||This is that color that will be applied to linked items (as defined above) at the moment that they are clicked/selected.|
|<10.11>||Form method||The form method can either be "post" (the default) or "get". The "get" method should no longer be used for form submission, but is provided for backward compatibility. This option tells the browser how it should submit data to the server.|
Pages can be associated with database files. This is valuable in cases
where a page has been defined to have a direct relationship with a
Standard system subroutines (sysfilesave, sysfiledel and others) are provided, which make use of the file name specified here.
The file name is available to subroutines through the sysfile common block item. The file name option may only be useful for elementary page operations and should not be used for complex, multi-file updates and transactional applications.
|<10.13>||Page load event||This event element supports user-defined code to be run as the page loads. This occurs as a new page is downloaded to the browser.|
|<10.14>||Page unload event||This event element supports user-defined code to be run as the page unloads. This occurs when the browser page is changed through form submission or linked to a new URL.|
|<10.16>||Page reset event||This event element supports user-defined code to be run as the page form resets. This occurs when a form button of type "reset" is clicked.|
|<10.17>||File submit encoding|
Any text placed within this element will be included into the page within
|<10.19>||Post body HTML||
Any text placed within this element will be inserted into the page after
|<10.20>||Body tag inclusion||The text placed within this element will be included within the HTML tag. This allows for the insertion of HTML attributes not handled directly by the page builder.|
|<10.21>||Form tag inclusion||The text placed within this element will be included within the HTML tag. This allows for the insertion of HTML attributes not handled directly by the page builder.|
|<10.22>||Pre-page routine||The subroutine that will be executed before the page is constructed. This subroutine is usually used for the preparation of data carrier variables (sysid, sysdata, syshidden, sysperm).|
|<10.23>||Pre-page parameters||Any text stored within this element will be passed to the pre page routine within the syspageparm common block variable.|
|<10.24>||Post-page routine||The subroutine that will be executed after the page has been constructed. This subroutine is usually used for filtering the HTML code that has been generated.|
|<10.25>||Post-page parameters||Any text stored within this element will be passed to the post page routine within the syspageparm common block variable|
This can be specified for applications making use of frames.
If specified, the result of the form submission will be displayed within a frame with the name specified.
File Submit Encoding This item sets up the mechanism for page submission to support multi-part form data.
If set, this item works in conjunction with the
File items uploaded with this mechanism are stored within the "sysatt" file/directory.
|<10.27>||Page focus event||This event element supports user-defined code to be run as the user accesses the page. Event code should either contain a detailed in-line script or a function call to an already defined function. Page functions should be defined before they are used and are generally defined within the page HTML element. It is best to include function calls at this level to maximise code re-use and to reduce the possibility of special characters (", < and >) being used within complex in-line scripts. More information can be obtained from the World Wide Web Consortium, Microsoft Site Builder Network and Netscape.|
|<10.28>||Page blur event||This event element supports user-defined code to be run as the user leaves the page. This occurs when the user clicks away from the page or when script code moves the focus away from the page.|