[MKDoc-dev] Is better timezone handling worth a new dependency?
Sam Tregar
sam at tregar.com
Fri Oct 15 21:15:00 BST 2004
Hello all. I'm working on the events component described here
earlier. A part of this work is a new TimeRange component which will
allow the user to enter start and end dates, including a timezone
component for each.
At present MKDoc uses Date::Manip for doing date math. Date::Manip
has some timezone support, but it's not particularly robust. It only
supports a small subset of timezone abbreviations, one for each
offset, and it has some limitations in dealing with daylight-savings
time (see the BUGS section in the Date::Manip docs). It also lacks
any means to produce a list of available timezones.
A number of better options exist on CPAN, chief among them
DateTime::TimeZone which supports every timezone in the Olson database
(i.e. all of them) and includes a call to list them for selection.
The only downside to using DateTime::TimeZone is the added dependency.
Since MKDoc lacks an installation system to install new dependencies
all MKDoc users would have to install any new modules before
upgrading.
So, the question is whether to make do with less feature-full timezone
support or go for quality and add a dependency. Opinions?
-sam
More information about the MKDoc-dev
mailing list