HTMLCAL, the Web calendar maker and editor

Version 2.6 for Multiple Calendars

© 1996-2000 by Timothy C. Barmann
tim@htmlcal.com
http://www.htmlcal.com/

Contents
Overview
Web Installation
  • General notes
  • Step by step
  • link to the calendars
Editing the calendars
  • Adding events
  • Editing existing events
  • Deleting events
  • Restricting access
DOS Installation
  • Command line parameters
  • Examples
  • Events database file format
Customizing the calendars
  • header.htm file
  • footer.htm file
  • cal.ini settings
Version revisions
Legalese
Acknowledgement
Technical Support
Appendix
  • JavaScript notes
  • All files explained

OVERVIEW

Thanks for purchasing HTMLCAL!

This software is designed to let you create live, interactive calendars on your Web site or intranet.

Anyone you allow can view and make changes to the calendars from any Web browser. Those changes will be immediately reflected for others to see.

You may also use the software as a DOS-based program to generate non-interactive calendar files ready to upload to your Web site.

The calendars can communicate events and activities to employees, colleagues, a group, or to the general public visiting your Web site. Possible uses include:

You may want each employee to have his or her own calendar set, or you may want each department in your organization to have its own calendar set. To learn more about the pricing of additional licenses, please see http://www.htmlcal.com/pricing.shtml.

The software was designed to work with the 3.0 and higher versions of Microsoft Internet Explorer and Netscape Navigator. It works best with JavaScript turned on in the browser software.

The version you purchased runs on Windows 95, 98 and NT based Web servers and desktop computers. HTMLCAL is also available on several Unix-based operating systems, including Sun Microsystems's Sun OS 5.6 and the Red Hat 5.0 version of Linux.

I. WEB SERVER INSTALLATION

This section explains how to install HTMLCAL on a Web server, which is necessary to allow live calendar editing from a Web browser. If you want to use the program from the DOS command line instead to make non-interactive calendars, see the section DOS Installation.

General notes

The HTMLCAL software runs on a Web server as a CGI program. It works with your Web server software. HTMLCAL should be installed on the same computer that runs your Web site or intranet.

HTMLCAL will not allow live calendar editing on a network that has only shared drives. A Web server is required for that feature.

HTMLCAL is compatible with most any Windows-based Web server. There are several free Web servers available:

Installation involves copying the files included in this package to your Web server's hard drive, changing some URLs in two files, and changing four settings in a configuration file. You will also need to generate a year's worth of calendars. You may need to change some directory and file permissions with your Web server software.

The following instructions are for setting up your first calendar. To set up additional calendars, simply repeat these instructions, but choose a different directory name for your next set of calendars. Each calendar you set up must be stored in its own directory. All calendars will run from the same cgi programs, but will otherwise be unique.

You may set up as many calendars as your license allows. That information in in license.txt included with this package. To order additional licenses, contact info@htmlcal.com.

Step by step

1. Create a directory where your Web pages are stored on your Web server. Let's assume you have called it "calendar". That is, on a Windows NT system running the IIS Web server, you create

c:\inetpub\wwwroot\calendar\

2. Copy all the files that came with this package into the calendar directory.

3. Move these three files to your CGI-BIN or Scripts directory (or whatever directory your CGI programs need to go in.). If such a directory doesn't exist, create one on your web server's hard drive. Do NOT use the cgi-win directory.

Note: All filenames must be lower case.

4. Edit the cal.ini file with a text editor, such as Notepad. This file contains settings that tell the HTMLCAL software where it will find important directories on your Web server. It also contains some optional settings to alter the way the calendars look. See the Customization section for details on these optional settings.

For now, ignore all but the first four settings: calendars_url, calendars_path, events_path and cgi_path. Make sure the values you enter begin immediately after the "=" sign, as shown in the example values. Do not use quotation marks or spaces. Make sure entries end with a slash (forward for the URL entry; backward for the directory entries).

Entries explained:

calendars_url=http://www.yourdomain.com/calendar/

This is the URL that leads to the directory you created to store your calendar. In other words, it is the full address someone would enter in a Web browser to get to the directory where your calendar is stored. Do not use a relative URL. This entry must end with a forward slash as in the example.

calendars_path=c:\inetpub\wwwroot\calendar\

This is the path on your Web server's hard drive that leads to the directory you created to store the calendar. In other words, it is the full path you would type at a command prompt following DIR to see a listing of the files in that directory. Do not use a relative path. This entry must end with a back slash as in the example.

events_path=c:\inetpub\wwwroot\calendar\

This entry tells the HTMLCAL program where to find the events database file. (That file is named for the current year, followed by .dat. The 2001 file is called 2001.dat for example.) You may store the events database file in any directory you like on the Web server. For simplicity, we recommend storing it in the same directory as the calendar files. That would make this entry identical to the calendar_path entry above. Do not use a relative path. This entry must end with a back slash as in the example.

cgi_path=c:\inetpub\scripts\

This is the directory on your Web server's hard drive where cgi programs are placed. Do not use a relative path. This entry must end with a back slash as in the example.

5. Make sure the permissions are set on the calendar directory so it has read and write permission. Also make sure the CGI-BIN or scripts directory execute permission. And set the *.dat file (2000.dat for 2000) to have both read and write permission, and make sure the directory where it is stored has read and write permission too.

There are two places to change those settings on Windows NT machines. The first is the Web server software administration tools. There is a place to change permissions on files and directories. Secondly, use NT Explorer to change permissions on file and directories.

6. Edit the Web page called fcaledit.htm. If needed, change the URL in the line: <FORM ACTION="/scripts/caled-nt.exe" METHOD="POST" target="bottom"> to the correct URL to the caled-nt.exe program.

7. Also in fcaledit.htm on the very next line, change the value in the "hidden" form entry to the correct path on the Web server to your cal.ini file. Use a full path, not a relative one:

<input type="hidden" name="ini_path" value="c:\inetpub\wwwroot\calendar\">
Also note this too must end with a backslash as illustrated. Do not include cal.ini as part of the path statement. Remember this path; you will need it again in steps 9 and 10.

8. Edit the Web page called calframe.htm and change the line:

<frame src="/calendar/fcaledit.htm"> to the correct URL, if needed.

9. In the same file (calframe.htm), change the line:

<frame src="http://www.yourdomain.com/scripts/caltime.exe? c:\inetpub\wwwroot\calendar\" name="bottom">

to the correct URL and path. (All this should be on the same line.) This may look confusing. The first URL is where your cgi-bin or scripts directory is located. Immediately following the question mark is the PATH where the calendar files are located. Again, in the second PATH, make sure it has a back slash at the end, as in the example.

10. Create this year's calendars from your Web browser. Enter the URL:

http://www.yourdomain.com/scripts/htmlc-nt.exe? /a+/pc:\inetpub\wwwroot\calendar\+/w
substituting your domain name, of course. And, instead of the c:\inetpub\wwwroot\calendar\ in this example, substitute the path on your server's hard drive to the cal.ini file for this set of calendars.

So, if your server is at http://www.rock.com, your cgi programs are stored in "scripts" and you've put your calendars and the cal.ini file in c:\inetpub\wwwroot\calendar\ you would enter:

http://www.rock.com/scripts/htmlc-nt.exe? /a+/pd:\inetpub\wwwroot\calendar\+/w
To create calendars for another year, you'll need to enter more information. For example, to create calendars for 2001:

http://www.yourdomain.com/scripts/htmlc-nt.exe? /y2001+/m1-12+/pc:\inetpub\wwwroot\calendar\+/w

Where the year follows the "y" and the month range follows the "m".

That's it. You are ready to open up calframe.htm from a Web browser and begin editing the calendar.

Linking to the calendars

Once the calendars are created, you can create a link that will always open up the current month's calendar. Just put this line of html code in a web page (with the correct url of course):

<a href="http://www.yourdomain.com/scripts/caltime.exe? c:\inetpub\wwwroot\calendar\">View this month's calendar</a>

II. EDITING THE CALENDARS

To edit the calendars, make sure your Web server software is running. Open the Web page called calframe.htm with a Web browser. You should open this file by entering the full Web address in the browser, even if you are working at the machine that is running the Web server:

http://www.yourdomain.com/calendar/calframe.htm

That file should open two frames. The top frame is the editing form, and the bottom frame should initially be the current month's calendar.

Adding events

To add an event, simply choose the date you want the event to appear, type in an event in the event field, then click the "Add" button. Events can be up to 255 characters long. Any characters entered beyond that limit are ignored.

Optionally, you may choose a font color, style or size for that event. You can also specify a Web page or E-mail address to link the event to on the calendar. In the link field, enter the Web address, beginning with "http://" or enter an e-mail address beginning with "mailto:" (without the quotes).

Tip: If you have a JavaScript-enabled browser, you may select the date to add an event to by clicking on the date on the calendar itself. The feature only works when the editing form is visible.

Deleting events

To delete an event, click on the arrow next to the event you want to delete, and the information from that event should appear in the editing form. Then click on the "delete" button. This feature only works with a JavaScript-enabled browser.

If your browser does not support JavaScript, follow these steps: In the event field, type in a word that is part of the event you want to delete. Select the day it occurs. Then click "delete". If you want to delete an event that falls on a day that has multiple events, make sure you enter a word that is unique to the event you want to delete.

Editing existing events

To replace an existing event with a new one, click on the arrow next to the event you want to edit, and the information from that event should appear in the editing form. Make any changes to the event, the link, font information, and even the date. Then click the "replace" button.

Note: You must click on the arrow before the replace option will work properly. Also note that it will not work properly if JavaScript is not enabled on your browser.

Without JavaScript, replacing an existing event requires two steps. First you must delete an event (see previous section). Then you must re-type the new event in the editing form and add it again.

Restricting Access

HTMLCAL was designed to be an open calendar editing system. It does not place any restrictions on who can view or edit the calendars. You can, however, restrict access to the calendars by changing settings on your Web server software to limit access to certain files or directories.

To limit who can see the calendars, simply password protect the directory where the calendars are stored.

To restrict who can edit the calendars, place the calframe.htm and fcaledit.htm files in their own directory and password protect that directory.

If you take the latter approach, you may want to remove the JavaScript code found in the header.htm file. That code places a link at the top of each calendar that lets someone viewing the calendar toggle between full-screen viewing mode and editing mode. At the very least, you will have to modify the path in the JavaScript code in header.htm if you move the fcaledit.htm and calframe.htm files to another directory.

It is beyond the scope of the document to explain how to set up password protection with your Web server. In general, this is accomplished using the Web server administration tool. See your manual or Web server documentation for additional information.

If you are the only person allowed to edit the calendars, you may want to keep them off the Web or your intranet altogether. Simply place calframe.htm and fcaledit.htm on your own PC.

III. USING HTMLCAL FROM THE COMMAND LINE

If you choose not to install HTMLCAL on a Web server, you may also use the software as an MS-DOS program to generate non-interactive, HTML calendars on your computer and upload them later to your Web site. This section explains how to run the program from the DOS command line. It works almost exactly like the shareware version.

Usage:

c:\>HTMLCAL (you will be prompted for month and year)

c:\>HTMLCAL [/mMM][-MM] [/yYYYY] [/eEvents] [/hHeader] [/fFooter] [/a] [/b]

WHERE:

MM-MM is the month or range of months desired.

YYYY is the year to create calendars for.

Events is the file name of events to place on calendars. See below for description of the events file format. By default, if no events file is listed, HTMLCAL looks for a file with a name comprised of the current year, with an extension of DAT. For 1999, the program looks for a file called 1999.dat. This file is optional.

Header is the file name of HTML source you want to appear at the top of all the calendars. Place in this file HTML code for a logo background color, etc. By default, if a header file is not specified, HTMLCAL looks for a file called HEADER.HTM. This file is optional.

Footer is the filename of HTML source you want to appear at the bottom of all the calendars. Place in this file HTML source for things such as links to a home page. By default, if a footer file is not specified, HTMLCAL looks for a file called FOOTER.HTM. This file is optional. /a is Auto mode. This optional command allows you to create calendars for each month of the current year.

/b Turns OFF the link bar which otherwise will be appended to the bottom of each calendar. The link bar lets the user switch to any other month by clicking on it. By default, if you don't use this command, the link bar will be placed below the calendar. It looks like this:

Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec

Examples

To create all 12 calendars for the current year, enter:

htmlcal /a

To make a series of calendars for July through December in 2001, enter:

htmlcal /y2001 /m7-12

For July only, enter:

htmlcal /y2001 /m7

To make a series of calendars using an events list called myevents.dat from May to Nov., 2000, turning off the link bar:

htmlcal /m5-11 /y2000 /emyevents.dat /b

To make a series of calendars using an events list called spring.dat, a header file called head.htm and a footer file called foot.htm, for March, April and May 2001:

htmlcal /m3-5 /y2001 /espring.dat /hhead.htm /ffoot.htm

Events file format

The events file is a plain, ASCII text file. Up to 200 events for each month can be stored in the events file. Any beyond that limit is ignored by HTMLCAL.

The events file holds the dates of the events and a description, in this format:

 07 04 Independence Day

 |  |  |--  The DESCRIPTION field begins at the 7th character.
 |  |       It can be up to 255 characters long, and must end
 |  |       with a carriage return. The description can
 |  |       contain HTML code, such as a link to a related Web
 |  |       site, or a link to an image.
 |  |
 |  |------ The DAY of the month field begins at the 4th
 |          character position. Pad single digit dates with
 |          a 0, as in this example.
 |
 |--------------- The MONTH field begins at the 1st character
                  on a new line. Pad single digit months with
                  a 0, as in this example.
The 3rd and 6th character is a space.

The events file should contain all the events for one entire calendar year. It's not necessary to put events in chronological order in the events file.

The description field in the events file can also contain HTML code, so the event can link to another Web page. For example, lets say you wanted to link to a Web site with directions to a July 4th party on your July calendar. It might be listed in your events file this way:

07 04 <a href="http://www.someplace.org/party/">Directions to party</a>

Each event, including the date, description, and optional link information, cannot exceed 255 characters, and must end with a carriage return. Do not break up a long description with carriage returns. (You must use a word processor that allows you to create lines more than 80 characters long do to this.)

The events file can have comments. Commented lines must begin with a semicolon (;) as the first character:

; This is an example of a comment in the events file. HTMLCAL
; will ignore these lines.

IV. CUSTOMIZING THE CALENDARS (both Web and command line versions)

HTMLCAL gives you a lot of control over the way the calendars look. There are several characteristics you can change, including the background image, background color, calendar table border width, color of the cells, and more.

If you are happy with the way the calendars look, you can simply skip this section. All settings are optional.

Note: Any changes you make described below will not take effect until you re-create your calendars, as explained above in the installation section.

There are three files that contain settings to customize the look of the calendars:

A. header.htm

Use the file header.htm to add HTML code to the top of each calendar. By doing so, you can put an image, such as your organization's logo. It will appear at the top of all the calendars.

The file header.htm also allows you to specify a particular wallpaper or background color with the <body> tag.

A typical header file might contain this code:

<BODY BGCOLOR="#FFFFFF" onLoad="InitEditFields()">
<IMG SRC="LOGO.GIF">
<HR>

This will make the background of the calendars white, and will link to the image "logo.gif," placing it at the top of all calendars. And it will add a horizontal rule.

The "onLoad" part of the body tag is necessary to make the replace function work properly.

The header.htm file is optional. By default, if it's not found, HTMLCAL will make the background color white, and will automatically insert the "onLoad" parameter.

header.htm should be stored in same directory as your events file, which is specified in cal.ini after the entry events_path=

B. footer.htm

Use a footer file to add HTML code to the bottom of each calendar. A typical use would be to add a set of links to other sites, such as a home page. HTMLCAL does not come with a footer.htm, but you can create one if you like with any text editor.

A typical footer might look like this:

<CENTER>
| <A HREF="http://www.mysite.com/">HOME PAGE</A> |
</CENTER>

This would place a link to http://www.mysite.com at the bottom of each calendar.

As with the header file, the footer file is optional. It should be stored in same directory as your events file, which is specified in cal.ini after the entry events_path=

C. cal.ini settings

You can further customize the way the calendar looks by changing the optional settings in the cal.ini file.

dow_font_color=white

Day of the Week font color sets the color of the font for the days of the week -- Sunday, Monday, etc., that appear at the top of every calendar. You can use any color that is part of the HTML standard, such as white, blue, green and so on. You can also use HTML hexadecimal color codes. For example, #FFFFFF would be white.

dow_bgcolor=blue

Day of the Week background color sets the color of the background for the days of the week row at the top of each calendar. You can use any color that is part of the HTML standard, such as white, blue, green and so on. You can also use HTML hexadecimal color codes. For example, #000000 is black.

Note: Make sure this background color is not the same color as day of the week font in the dow_font_color setting. Otherwise the letters will be invisible.

date_cell_bgcolor=#FFFFBB

Date cell background color is the color of background for cells in the calendar that contain day numbers, as opposed to blank cells that simply fill out a week at the beginning or end of a month. You can use any color that is recognized by your browser, such as white, blue, green. You can also use HTML hexadecimal color codes. For example, #FFFFFF would be white.

blank_cell_bgcolor=#EEEEEE

Blank cell background color is the color of background for cells in the calendar that do not contain dates -- those that simply fill out a week at the beginning or end of a month. You can use any color that is recognized by your browser, such as white, blue, green. You can also use HTML hexadecimal color codes. For example, #FFFFFF would be white.

cellpadding=0

Cell padding determines how much space, in pixels, there is between the text inside a cell and the borders. This would be the same value you would use as if you were inserting the actual cellpadding HTML code inside a Web page table.

cellspacing=0

Cell spacing determines how much space, in pixels, there is between each cell of the calendar. This would be the same value you would use as if you were inserting the actual cellspacing HTML code inside a Web page table.

cell_height=2

Cell height determines the minimum number of blank lines that will appear in each cell on days when there are no events. Blank lines are used to improve the look of the calendars. You may want to adjust this setting if you are trying to print the calendars.Note: the calendar cells will stretch to fill the maximum number of events that fall on a particular day, regardless of this setting.

table_border=1

Table border determines whether the border on each calendar is visible or not. A setting of 1 makes the border visible; 0 makes it invisible.

percent_width=100

Percent width allows you change how the horizontal width of the calendar, relative to the width of the browser window or frame. The default value of 100 will take up the entire width of the brower window or frame. We recommend a value of 75 or higher to make the calendars appear as they were intended.

link_bar=TRUE

Link bar allows you to turn on or off the links to other months that appear at the bottom of the calendars. TRUE turns the link bar on; FALSE turns it off.

hr=on

The horizontal rule setting determines whether there will be a horizontal rule separating multiple events that occur on the same day. "on" means there is a rule, "off" means there is not.

target=target_name

This setting allows you to change the target frame for events that are linked to another Web site. By default, if this is not set in cal.ini, the software will make the target "_top". That will replace the entire frame with the linked Web site. If you are using frames, you may want to change this setting where you want the links to appear. Enter the name of the frame immediately after the = sign.

V. BUGS

Please send any questions, comments or bug reports to me at: tim@htmlcal.com, or visit the HTMLCAL Web site at http://www.htmlcal.com.

VI. VERSION REVISIONS

Version 2.5, September 1999

Version 2.2, November, 1998

Version 2.1, September 1997 Version 2.0, June 1997

Version 1.0, April 1996

VII. LEGALESE

Use this program at your own risk. While we've made considerable effort to make sure this program works properly, by using this program you agree not to hold Timothy C. Barmann or Barmann Software, LLC liable for any damage or loss of data, or any other loss that occurs from its use or misuse. No warranty is expressed or implied.

VIII. ACKNOWLEDGEMENTS

The Web server version of HTMLCAL uses a subroutine written by James Marshall, jms@jmarshall.com. The source code to this routine, called getcgivars, is freely available on his Web site at http://www.jmarshall.com. This helpful site has other documents and source code to help programmers with CGI programming.

IX. TECHNICAL SUPPORT

Barmann Software will give technical support by e-mail for six months. If you encounter any problems with HTMLCAL, please send your message to support@htmlcal.com.

Please attach the following files: cal.ini, fcaledit.htm and calframe.htm. Please include details about your problem and cut and paste any error messages you may be receiving.

Additionally, you may write to us at P.O. Box 1145, Providence, RI 02901. The HTMLCAL Web site, http://www.htmlcal.com/ will announce any software updates.

X. APPENDIX

Notes about using JavaScript

This version of HTMLCAL uses JavaScript to make it easier and faster to accomplish some tasks. The JavaScript code we use makes sure you enter a date that is valid, and it makes it possible to modify an existing event without having to first delete and then add it again.

JavaScript is widely supported on nearly all browsers. It is generally transparent to the person using the browser. Don't confuse JavaScript with Java, which is a completely different programming language that can slow down your browser. The calendar files are slightly larger than they were in previous versions, due to the extra JavaScript code. However, this should make very little, if any noticeable difference in how fast the calendars load.

If for some reason you do not want to take advantage of the JavaScript features, you can instruct the software not to use JavaScript code inside the calendar files. Place this command on its own line in the cal.ini file:

jsedit=off
You will need to regenerate the calendars to delete the JavaScript code from the calendar files. In addition, there is JavaScript code inside the header.htm and fcaledit.htm files.

Explanation of files that come with this package

htmlc-nt.exe

The HTMLCAL program. This program can be run as a standalone DOS program to create Web calendar files on your PC, ready to upload to your Web site. Or the program should be installed on your Web server according to the installation instructions. This file should be stored in the cgi-bin or scripts directory. It should NOT be placed in the cgi-win directory.

caled-nt.exe

Part of the calendar editing software. It works in in conjunction with htmlc-nt.exe. It cannot be run as a standalone program. This file should be stored in the cgi-bin or scripts directory. It should NOT be placed in the cgi-win directory.

caltime.exe

This program, when opened by a browser, causes the current month's calendar to load. You may link to this program in order to load this month's calendar. The HTML code would look like:
<a href="http://www.yourdomain.com/scripts/caltime.exe? c:\inetpub\wwwroot\calendar\">View this month's calendar</a>

(Change this to the correct URL and path to the cal.ini file.)

Caltime.exe should be stored in the cgi-bin or scripts directory. It should NOT be placed in the cgi-win directory.

cal.ini

This is the initialization file that is used to store the information for the calendar software. Each calendar must have its own cal.ini file. It describes the paths and URLs where your calendars are stored. It also contains information about how the calendars should look. We recommend you store the cal.ini file in the same directory as the calendars it contains settings for.

(The contents of the cal.ini file are explained in detail in the installation instructions section of this document.)

2000.dat, 1999.dat, etc.

The database file that HTMLCAL uses to store and retrieve events that are placed on the calendars. There is a separate database file for each year. For 1999, the database file is called 1999.dat. For 2000, it is called 2000.dat, etc. HTMLCAL will automatically create an events data file if it doesn't find one. This file should have read and write permission, as should the directory where it is stored.

The events data file should be stored in the path specified in cal.ini after the entry events_path=.

header.htm

Put any HTML source code you want to appear at the top of all calendars in this file. Do not put in a complete HTML Web page in this file. Only place the HTML code you want inserted into the calendar files. You can optionally put in a background color in this file by putting in this code:

<body bgcolor="#FFFFFF">

The header.htm file is shipped with some JavaScript code that makes it easy to toggle back and forth between a full screen calendar and the editing mode. If you do not want to allow others to edit the calendars, you may wish to remove this code.

The header file should be stored in same directory as your events file, which is specified in cal.ini after the entry events_path=

footer.htm

The program is not shipped with a footer.htm file, but you may create one with any text editor. Put any HTML source code you want to appear at the bottom of all calendars in this file. Do not put in a complete HTML Web page in this file. Only place the HTML code you want inserted at the bottom of the calendar files.

The footer file should be stored in same directory as your events file, which is specified in cal.ini after the entry events_path=

calframe.htm

Main page to open in order to edit the calendars. This Web page creates two frames. The top frame is the editing form (fcaledit.htm) and the bottom frame initially loads the current month's calendar.

fcaledit.htm

Form for editing calendars. You may make minor editing changes to this file, such as adding a logo, changing the background color, etc., but you must keep the rest of the HTML source that creates the form exactly as it is in the original fcaledit.htm file.

calframe.htm and fcaledit.htm work with each other and should be stored together in the same directory. It is recommended that you store them in the directory of the calendars they will edit.

htmlcalt.jpg, main.jpg

htmlcalt.jpg is the HTMLCAL logo for the fcaledit.htm page. You may substitute your own if you wish. main.jpg is the logo that goes with this document.

editon.gif, editoff.gif

These are small arrow images that appear next to each event. These should be stored in your calendar directory. Editon.gif is a red arrow; editoff.gif is a black arrow. If you are using a JavaScript enabled browser, the arrow will turn red if the mouse is place over it, and the editing form is visible. (When in full screen calendar view, the arrow stays black.) Clicking on an arrow loads the event information into the editing form.

help.htm

Help file for using HTMLCAL for live calendar editing. It is a small subset of this document. This file is linked to from the fcaledit.htm file.

htmlcal.htm

This document.

Revised October 6, 1999

This document © 1999 by Timothy C. Barmann, Barmann Software LLC, P.O. Box 1145, Providence, RI 02901