Oracle Calendar Web Client Administrator's Guide Release 3.1 Part Number B10095-01 |
|
| View PDF |
Cascading style sheets are used to manage the appearance of the Oracle Calendar web client. Most appearance attributes can be modified from these style sheets. The attributes that cannot be modified from the style sheets are set in <fcgi-bin>/lexacal-private/ini/webcal.ini.
It is highly recommended that Administrators work with the style sheets as much as possible. If an attribute is configurable from both the style sheet and webcal.ini, the style sheet settings override any changes made to webcal.ini. Therefore, changes in webcal.ini should only be made to attributes that cannot be configured using the style sheets.
Parameter: s1
Description: The style sheet packaged with the Oracle Calendar web client for Standard mode.
Value: /owc/stylesheet/english/swcdefault.css
Parameter: ada
Description: The style sheet packaged with the Oracle Calendar web client for Accessible mode. If Accessible mode is enabled, the Accessible style sheet must be uncommented out to get the correct Accessible mode appearance.
Value: /owc/stylesheet/english/swcada.css
The values accepted for the attribute parameters must be part of the hexadecimal codes used for color definition in HTML. The color code uses the following pattern: RRGGBB, where each character is hex (base 16, 0 through f). This gives 256 levels each for Red, Green, and Blue.
The following table describes attribute parameters that cannot be defined in the Oracle Calendar web client style sheets. These parameters are found in <fcgi-bin>/lexacal-private/ini/webcal.ini.
The following attributes can be configured using the style sheet for the main Calendar and Task Views. However, to configure these attributes for secondary pages in the Oracle Calendar web client you must use webcal.ini
.
All display parameters are configured in webcal.ini
. The style sheets do not affect any of these settings.
The banner template files contain partial HTML mark-up that includes the banner's contents. There are no <BODY> or <HTML> tags in the banner templates. HTML balance-checking is not performed by any of the FCGIs on the content of these banner files. The HTML mark-up in the banner templates must be balanced so that all tags are closed off properly. If not, the view can be lost.
The path where the banner template files are located is set to <fcgi-bin>/lexacal-private/banners
.
If the banner template files cannot be accessed, the corresponding banner will not appear. No error will be reported on the user view.
If you have a script that dynamically generates your banner following the guidelines below, set the script's file extension to .scr. For example, if the file that produces the top banner templates is top.sh, rename the script to top.scr and make the appropriate mapping to top.scr in the webcal.ini file so that ban_top=top.scr.
The location of the banner producing scripts is set to <fcgi-bin>/lexacal-private/banners. Ensure that the permissions are set so that your script and the path leading to this directory are executable by others.
As with the static banner templates, if for some reason the banner script cannot be accessed or executed, the corresponding banner will not appear. No error will be reported on the user view.
The banner template files as well the banner scripts should produce HTML mark-up that has no <BODY> or <HTML>. Here is an example of how the banner mark-up should look.
<TABLE BORDER="0" WIDTH="548" CELLSPACING="0" CELLPADDING="0" ALIGN="CENTER"> <TR> <TD ALIGN=center> <A HREF="http://www.oracle.com/" target="_top"> <IMG src="/owc/images/english/banners/banner_top.gif" height=78 width=548 border=1 alt="Oracle"></A> </TD> </TR></TABLE>
To disable any of these banners in the Agenda View, comment out the corresponding parameter in the webcal.ini file.