I agree with Joshua's intent. I think that the timezone selection
right now is the most difficult part of using DateTime if the user has
to specify it (and especially if you are not using a GUI).
I agree that changing DT::TZ is probably not the right thing to do.
Perhaps there should be a DT::TZ::Helper namespace?
I would also love a module that would set up appropriate
DT::TZ::Alias(es) for a given country. So if I loaded
DT::TZ::Alias::Country qw(US); (or whatever) it would load EST as an
alias for America/New_York.
Finally, having the aliases US/Eastern makes a lot of sense to me.
Perhaps it would make sense to make equivalent alises for all of the
countries (possibly under a DT::TZ::Alias submodule). So for
countries without different zones that is simply:
China
Britain
Then for countries with multiple zones:
Australia/Eastern
etc.
-ben
On Mon, Sep 22, 2003 at 10:31:38PM -1000, Joshua Hoblitt wrote:
> > It's become painfully obvious that having end users choose
> > a timezone based on the huge list that is provided natively
> > by DateTime::TimeZone::all_names just isn't very practical
> > at this time. (Perhaps in the future when more people are
> > used to dealing with the Olson names.)
..