|
The main template provides positioning information for each of the components of every Class Calendar
web page. The following idealised table is taken from the body of the template. Areas in grey are
hold content generated by the application; white areas provide spacing:
DAY
DATE MONTH
YEAR
|
|
HEADER
|
|
|
|
|
NAVIGATION
BUTTONS
|
|
|
|
CERTIFICATE
|
|
|
|
|
|
|
|
WORKFLOW INDICATOR
|
|
|
|
MAIN
REPORT
|
|
|
|
|
|
|
You can re-write all of this HTML in your own custom template. However, be careful not to remove the
SUB_<CONTENT> entries in the template, because these are used to place dynamically generated
content into the completed document.
In addition, the start of the template contains HTML comments of the form:
<!-- SUB tocBackground SUB_TOC_BACKGROUND -->
These comments must be left as they are, because they are used to direct server-side data
into the document.
You can place any number of HTML structures around the existing HTML structure of the main table.
However, some restrictions are necessary to enable the JavaScript code used to animate button
roll-overs to work correctly. In particular, the JavaScript invocation in the HTML
body tag:
onload="buildNav( 0, SUB_PRSP, SUB_VIEW, SUB_IS_TERMS, SUB_IS_SCHOOL, SUB_IS_ACTING, 'SUB_BUTTON_SET_BASE_URL', SUB_HEADER_SIZE );
is used to indicate how many HTML <img ...> tags exist before the main table. In this case, there are no
images. If there were two images, the JavaScript call should read:
onload="buildNav( 2, SUB_PRSP, SUB_VIEW, SUB_IS_TERMS, SUB_IS_SCHOOL, SUB_IS_ACTING, 'SUB_BUTTON_SET_BASE_URL', SUB_HEADER_SIZE );
Placing extra HTML <img ...> tags within the table is not advisable. If you wish to proceed
with this, you will probably need to alter the JavaScript code referenced by the main template.
|
