************************************** HTMLCAL Version 2.0 An HTML calendar maker (c) 1996, 1997 by Timothy C. Barmann tim@cybertalk.com http://www.cybertalk.com/~tim/software/ *************************************** OVERVIEW -------- HTMLCAL is a shareware program that makes Web page calendars. HTMLCAL generates full-page calendars that can be posted directly to your Web site or company intranet. Use it to list upcoming events or meetings. The calendars are designed to be viewed with both Netscape Navigator and Microsoft Internet Explorer Web browsers. You are welcome to try out this unregistered program and the calendars it creates for 30 days. When you register, you will receive a personalized copy of HTMLCAL, plus a version that will let you create and edit your calendars directly from any Web browser. Use it to coordinate meetings or projects for your company, or set up a community event calendar that anyone can access and add events to. The program costs either $10 or $20, depending on who you are and what you will use it for. See the registration section, or REGISTER.DOC for more information. I. HOW TO USE HTMLCAL --------------------- HTMLCAL works from the DOS or Unix command line. 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 1998, the program looks for a file called 1998.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 is used by itself and allows you to create calendars for each month of the current year without having to enter any other parameters. /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 1998, enter: HTMLCAL /y1998 /m7-12 For July only, enter: HTMLCAL /y1998 /m7 To make a series of calendars using an events list called myevents.dat from May to Nov., 1998, turning off the link bar: HTMLCAL /m5-11 /y1998 /fmyevents.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, 1999: HTMLCAL /m3-5 /y1999 /espring.dat /hhead.htm /ffoot.htm ----------------------------------------------------------------------------- Events file format The shareware version of HTMLCAL requires that you enter events in a data file, while the registered version also allows editing directly from a Web page form. The events file by default is called xxxx.dat, where xxxx is the year. For example, events for 1998 should be stored in a file called 1998.dat The events file is a plain, ASCII text file. Up to 200 events can be stored in the events file. (Any beyond that 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 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 should be a space. The events file should contain all the events for every calendar you are creating. For example, it you are creating a year's worth of calendars at one time, you only need to maintain one events file. HTMLCAL will search through the events file for each calendar it makes, looking for the relevant dates. 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 Directions to party 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. Multiple events on the same day will be automatically separated by a horizontal line. II. CUSTOMIZING THE CALENDARS ----------------------------- header.htm Use a header file (header.htm) if you want your calendars to have a particular wallpaper or background color. This is also where you can put a link to an image, such as your organization's logo, that you want to appear at the top of all the calendars you create. A typical header file, written in HTML, might contain this code: