My apologies to those of you who are regular readers. I’ve been rather preoccupied with writing my calendar. Here’s what I’ve done so far:
- Created a name, Simple Calendar.
- Created a large and a small logo (simple logos as the name would imply!)
- Borrowed heavily from the open source calendar Datenator. I use this calendar now, so it only made sense to me to modify this to suit my needs.
- Created a schema for the settings. This is a one row table that contains all of the administrative settings for the calendar.
I’ve modified this schema about three times since creating the table. - Created a schema for the events. This will have one row per event and contain all the details of the event. Haven’t done much with this yet, but I hope NOT to change the schema.
- Modified the Datenator admin login page, using the WordPress admin login as my model.
- Modified the Datenator administrative page, removing the stuff I don’t want to use and adding in a number of items that I want to use.
- Spent most of last night looking up holidays and how they are computed — man is computing Easter twisted! The formula I used can be found here.
- The only way to compute Ash Wednesday is to back up 46 days before Easter; the only way to compute Palm Sunday is to back up 7 days before Easter; the only way to compute Good Friday is to back up 2 days before Easter. WOW!
- Working on the core functions; I will need to include functions to compute all floating holidays in this file.
- After the core functions are done, the next step will be to display the calendar.
- Last, but not least, will be modules to add, edit and remove events from the calendar. I want to include recurrence, so it won’t be a complete copy of Datenator, but again I’ll be borrowing from it.
I hope Lauri Itkonen, the creator of Datenator, isn’t upset with me for borrowing so much of the code. But, you know what they say: Imitation is the sincerest form of flattery.
