Ticket #2684 (closed enhancement: fixed)

Opened 7 years ago

Last modified 7 years ago

No way to set the timezone or the time or the time format, but the journal shows timestamps on everything

Reported by: gnu Owned by: erikos
Priority: normal Milestone: Update.1
Component: sugar Version: Build 542
Keywords: Cc: jg
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

It tells me I started the Chat activity Today at 08:19 AM, but that's wrong, and there's no way to fix it.

I suspect that if there's a school server nearby, an XO that doesn't know its timezone should set its timezone from the school server.

Kids are going to have real trouble figuring out the difference between setting your clock and setting your timezone. This probably needs user interface design.

PS: "08:19 AM"? How can I get rid of that obsolete "AM" stuff and use 24-hour times like God intended (and like all the other people in my country use)? I guess we need to get into Locale-setting here, too...

PPS: #430 tried to report this bug months ago, but it was closed out "wontfix" because their proposed fix (shipping in UTC timezone) wasn't right either. What good is a clock that you can't set?

Change History

Changed 7 years ago by jg

  • cc Eben, wad, jg added
  • owner changed from dcbw to Hal
  • milestone changed from Untriaged to Trial-3

We've documented in the wiki how to customize a build, including timezone, as the temporary solution.

I'm assigning this to Hal Murray to opine if there is a standard way to get timezone information from a local server, as he's more expert at ntp and friends than I am.

Changed 7 years ago by hal

Nice try, but NTP works in UTC and ignores time zones.

So does *nix internally. Time zones are a UI/conversion issue.

I assume the systems shipped to each country will be customized somewhat. If nothing else, a new machine should defalt to using the the local language. Can setting the time zone piggyback on that? How many target countries span multiple time zones?

The default local time zone file lives in /etc/localtime so something like this will fix it:

cp -p /usr/share/zoneinfo/xxx /etc/localtime

PS: You can save a few megabytes of disk space if you don't need the other zone files.

Changed 7 years ago by gnu

  • owner changed from Hal to Eben

Suggesting that Eben look at UI design for setting time/timezone/locale, since setting it via NTP doesn't work. Fedora has a well developed interface for much of this: system-config-time for time and timezone and NTP servers. I haven't found a GUI in Fedora for setting the locale, only system-config-language which sets human language, not date and currency formatting. Perhaps these should be the first things in a Sugar system-administration or system-preferences interface.

Changed 7 years ago by Eben

  • owner changed from Eben to hal

I think that taking the time zone from the school server is a good idea. This can be part of the registration process, which will also make it easy for kids who move and switch time zones. Apart from that, we may want to add a manual way to adjust time zones, but as mentioned, this should be an edge case and not a requirement. We don't yet have a global settings or preferences center, but we'll eventually need something of this nature.

Regarding the AM vs. PM vs. "who cares exactly what time it was anyway...it was last week" argument, the relative date API should be adopting the 3rd option. We want to use relative times with decreasing granularity as time passes, so that something from 9 months ago is dated as "9 months ago." There are tickets for this, and of course, as with everything, localization will also apply here too. (For those that need the details, the detail view for each entry will reveal the exact time, based on the timestamp (and perhaps the timezone) and that might have a global setting for display as well...maybe we'll just adopt 24 hour time as a default anyway...I like that approach.)

Changed 7 years ago by marco

  • milestone changed from Trial-3 to Untriaged

New features...

Changed 7 years ago by jg

  • milestone changed from Untriaged to First Deployment, V1.0

This might be worth putting into the configuration GUI we've discussed; this is pretty low priority, though, as it is pretty easy to set up in customizing an image for deployment.

Changed 7 years ago by marco

  • type changed from defect to enhancement
  • milestone changed from First Deployment, V1.0 to Untriaged

Changed 7 years ago by tomeu

We are not showing in the journal any absolute date anymore, only the period of time elapsed since last modification.

I guess we need to leave this open and we'll show dates somewhere someday.

Changed 7 years ago by Eben

The Journal design calls for the absolute date within the detail view for an entry, in addition to other technical goodies like filesize, extension, etc. Priority isn't high.

Changed 7 years ago by jg

Again G1G1 may force our hands slightly for timezone... We'll have to think about that.

Changed 7 years ago by AlbertCahalan

There is something to be said for manually dragging the hour hand of a clock. The TZ environment variable gets set to something like OLPC+5:45 or OLPC+14. (an arbitrary name and an offset from UTC) You need 15-minute increments to handle Nepal and offsets over 12 to handle New Zealand, so the minute hand and date must move as well. Of course you don't get to mess with UTC; that comes from NTP.

This avoids the whole complicated geography issue, and the ugly situation of maps having political boundries that may be offensive or illegal.

Daylight saving time, if any, would handled just as on a wall clock. You drag the hour hand twice a year. This was even standard on PCs for over a dozen years.

Changed 7 years ago by jg

  • cc Eben, wad removed
  • owner changed from hal to erikos
  • milestone changed from Untriaged to Update.1

If I remember correctly, Simon was implementing some way to set the timezone. (a script initially).

Simon, if this has been done, please go ahead and close this.

Changed 7 years ago by marco

  • status changed from new to closed
  • resolution set to fixed

I think this is implemented in sugar-control-panel

Note: See TracTickets for help on using tickets.