A few suggestions.
How about some notes on Upgrade.cgi? It's about as sparse a piece of code as you can get.
Some questions you can answer are:
- How are we supposed to know what version we have? I installed my calendar over a year ago
and I have no idea what I have. Does it make a difference which I pick? What happens if I
pick the wrong one? Should I run once with both options to be sure?
- How long does the upgrade take to run? I hit “Continue” after a minute or two and I got
an error about permissions on my member file. Does this mean I need to reset permissions and
run it again and leave it running this time? Does it mean I picked the wrong older version?
Under what conditions should I ever click “Continue”?
- And what’s up with the title “Upgrading - Calendar Hack 1.0 - 1.8 - 1.9”? Should 1.9
be 2.0 now? 1.9+?
Another pet peeve is how you have “calendar.txt” setup. Why do you put the edits in that order?
I have my UBB files saved off to my hard drive in the same directory structure as UBB has it.
So when I have to go back and forth between editing .cgi and .pl files I have to change
directories 9 times! I could see if you had them ordered for another purpose, but they’re not
even in alpha order in case you have all the files to edit in one directory. Give us a
break and cut and paste a bit!
I wish you would upgrade the design a bit and make things look a bit better. Shouldn’t
“Add a new event” and “Review today's events“ be on the same line and moved to one side or
the other? A lot of graphical tweaks could be done to remove blank lines and tighten things
up. The “Add New Event” header bar text should be moved to the left to match standard
UBB.classic. The “Review Today’s Events” header bat text should read “Review Events for …”
and font size should match every other text bar like it. There are a lot of little things
like that that could use some work.
A wish list item would be an admin function to clean and refresh the birthdays that people
set in their profile. All you would need would be a single character flag added to the
calendar event that tells whether the event came from a user’s profile or was custom added.
Then, on a click in the CP, all those profile birthdays could be removed and members could
be searched for their “Check To Display Birthday” flag. Deleted members would be expunged and
any glitches would be corrected.
Other than that, the program works great.
