Sorry for not chiming in earlier, but I thought we decided last week
that since this issue of default timezone is so confusing (Is it per
user? Per collection? what the heck does it even MEAN?) that we would
not have any sort of default timezone in 0.6 meaning that timezone
support for 0.6 would be:
1) New Events default to floating timezone (like now) but you can
choose a timezone from the list.
2) Events with timezones get placed on the canvas relative to the
browser's offset (exactly like now)
So the upshot is that the only new functionality is the ability to
edit timezones on events. But with all this infrastructure work going
on, default timezones will be easy in the next release - once we
figure out what we want.
And for the record Matthew and Jeffrey are correct - you cannot get
the timezone from the browser in any sort of reliable way.
Bobby
On Nov 13, 2006, at 11:01 AM, Matthew Eernisse wrote:
JS has nothing like that built in, but we are working on full-blown
timezone support for dates in JS for Cosmo 0.6.
Priscilla Chung wrote:
computer is set to, not based on the IP address. I have been
informed that Cosmo the web client can get the time-zone from the
browser through javascript–Matthew correct me if I'm wrong here.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
