From: Jason Grosland <jcg3@cs.duke.edu>
  To  : 
  Date: Thu, 18 Feb 1999 01:25:43 -0500

Re: Table Format

On Sun, 14 Feb 1999, Huned M. Botee wrote:

> The above didn't really make sense to me, but I think what's supposed to
> happen is this: For each appointment description, the program generates
> an HTML file and that page is linked in from the main hyperwag
> schedule/table/thingie. Actually, a better way to do it might be to have
> all the descriptions in ONE html file, where each description is given
> an anchor name. That way, you don't have to clutter the user's
> directories with html files. That would be neat, I guess.

This is a tough decision from your user interface perspective.  If you
include it all in one html file and use anchors, then the things at the
bottom of the html page are not easily viewed because your browser won't
have the anchor at the top (where you want the user to focus) of the page.

You might think about trying more interesting stuff if you know stuff
about dHTML like layers, or if you want to do some stuff with frames...
or javascript pop-up alerts...  there are quite a few options.

If you're feeling really aggressive, you can implement these all, and
allow the user to select what their default would be-- either through a
.hyperrc file, or command line options, or a hyperconfig program...

A good thing to do is to think about how you might develop your design so
it is expandable for these kinds of options.  I know several people who
have gone on to use hyperwag for real applications.  You might also notice
all the interest in the online portals offering calendar services...  this
isn't just a cute little learning exercize.

-Jason
cps 108 uta
- jcg3@duke.edu         shanty.dorm.duke.edu         www.duke.edu/~jcg3 -