Ryszard, it looks to me that you are well on your way. I've modified/written something similar for our University calendar that you might want to look at for some ideas on layout. It provides several different views (6-month calendar, plain-text monthly, weekly and daily views). The link is USA Campus Calendar. I borrowed the core 6-month view code from an Ill. University (Urbana, I think, with their permission of course). It reads directly from the xnix cal command.

I don't really see that the speed to create the calendar table itself will present much of a bottleneck. It is more likely that fetching your data will take much more time (depending on your method), particularly if you have to retrieve data dynamically from Yahoo. You might want to consider a batch process that periodically updates a database or series of files (one file per event). The series of files method is the one I used since our events are generated manually at our site (through a Web interface). Unfortunately, we don't have a hit counter in place, so I can't say exactly how much it is used.

If you are interested in seeing some of my code, I can post it to my scratch pad. Particularly how the 6-month view is generated.

As far as your code goes, the only thing that some people might recommend is changing your  for (;;){} loops to  for (..){} loops. But I don't think in this case that it is objectionable (besides, the code that I modified/wrote uses them and doesn't utilize CGI table building methods as you have, so I'm not worthy to complain).

Good luck finishing your project!

--Jim