Calendar Gets an Overhaul
The calendar module is getting a much needed overhaul. To be released soon.
Category: Modules
I was digging through the Calendar module the other day, trying to fix a few bugs, and I got into a mood (that doesn't happen too often anymore by the way... I'm typically way too busy). Anyways, I started going nuts fixing some of the stuff that should've been done a long time ago, and bringing the calendar module up to the specifications of the other modules I maintain.
Here's a short summary of what I'm doing:
- Fixing known bugs
- I'll be going through the tracker and trying to fix as many bugs as I can reproduce.
- I'll be going through the tracker and trying to fix as many bugs as I can reproduce.
- Re-implementing templating
- I've made Calendar dependant upon the CGExtensions module, and have re-organized the admin interface to allow handling multiple database templates in the way my other modules do. This includes Products and CompanyDirectory. This will get rid of the 'file templates' tab completely, and allow numerous templates of each different type.
- I've made Calendar dependant upon the CGExtensions module, and have re-organized the admin interface to allow handling multiple database templates in the way my other modules do. This includes Products and CompanyDirectory. This will get rid of the 'file templates' tab completely, and allow numerous templates of each different type.
- Introducing Lazy-Loading to try to reduce the memory footprint for the module for front end displays.
- Fixing the link generation
- Make pretty url generation consistent among all of the different calendar displays
- Pass appropriate parameters like detailpage and eventtemplate along on the next/prev links in the calendar, yearlist, and list displays
- Pass all necessary parameters along in detail links when pretty urls are disabled.
- This may break backward compatibility for some sites. But will be consistent and will hopefully be more logical in the new version.
- I'm getting rid of the extra lang preference in the module, and making it consistent with the other modules
- I'm getting rid of the dateformat parameter, and in exchange will be using the cms_date_format smarty modifier.
- Re-documenting the module
- I'm going to completely redo the template to be a bit more consistent with the documentation of the other modules, so that it is a bit easier to understand, and to translate.
- Fixing date handling in the templates
- Where possible, I'll be modifying the default templates to use the cms_date_format parameter when displaying dates. This will be consistent with the other modules, and allow for easier maintenance of date formatting. This won't be possible everywhere, but I hope that a few important places will use cms_date_format when displaying dates.
- Re-licensing
- I'll be changing the license of the module to be consistent with my other modules.
- Whatever else I find while I'm at it.
