things to do

David S. Cargo (
Thu, 5 Mar 1998 10:10:06 -0600

Date: Thu, 5 Mar 1998 10:10:06 -0600
From: (David S. Cargo)
Message-Id: <>
Subject: things to do

I tried to look at the GIF files that make up the animation, but I
found a couple of problems. The first problem is that the faith series
of files don't seem to be GIF files. The second problem is that the
mailtohtml files don't seem to have an obvious order. It looks like
the mailtohtml3 files go in increasing order and the mailtohtml3a file
go in decreasing order. (Having the order specified is of course
required to make the animation work.)

I don't know where the problem might be in the faith files. Could
somebody else check out the faith files to see if the problem is just
with my download? (And if the problem is not just with my download,
we need to figure out how to get newer versions available.)

Other things that we will be doing between now and Monday at 4:

the poster for the presentation
the brochure for the presentation
the script for the presentation
the code for the splash screen (the animation and the GIF files)
the code for the HTML Options tab previews (using the text widget)
the revised help info
the new user interface itself (which has many parts)

My plan is to work on the UI between tonight and Monday, whenever I can.
I do think that I can get everything done on the list. I plan to put
updated versions in my ftp directory whenever they are stable. (So, if
you download them, they should run, although the path from the original
interface to the final one might be kind of odd.)

Every release will be accompanied by a mail message, which if I can manage
will summarize what features are new and what remains to be done.

If I finish the UI before Sunday night (or stately alternatively if I have
more time to code available) I will work on some of the details for the
actual implementation (executing hypermail first, and then implementing

The reason I want everybody to know when there are new intermediate versions
available is so that you can test and evaluate them. Problems that show
up in the intermediate versions can be fixed, whereas problems that show
up in the final code are kind of stuck there.

Volunteers to work on revising the help, the splash screen, and the preview
screens are welcome.

If I have left anything out, please reply in a follow-up message.