Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support timezones #36

Open
danielrichman opened this issue May 31, 2014 · 2 comments
Open

Support timezones #36

danielrichman opened this issue May 31, 2014 · 2 comments

Comments

@danielrichman
Copy link
Member

... oh god.

Requested by James Ewen ve6srv

@mattjudge
Copy link
Member

You know, so long as we can rely on browsers supplying the correct local
and UTC time, it shouldn't be that hard to implement. Could be
interesting to check in practice though.

In the summer. After exams.
;)

Matt

On 01/06/2014 00:00, Daniel Richman wrote:

... oh god.

Requested by James Ewen [email protected] mailto:[email protected]


Reply to this email directly or view it on GitHub
#36.

@danielrichman
Copy link
Member Author

I don't think we can rely on that :P While it is the user’s loss if their clocks are set wrong, we'll have to make it quite obvious what times we've sent to the server, or someone is eventually wind up running predictions for 6 hours in the wrong direction (which could have pretty bad consequences). “Oh god” was more referring to the state of Javascript datetime support ;-).

Bonus points for autodetecting the timezone from the launch location on the map :P.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants