GNOME Clocks has been in the works for 3 months now almost. It is an implementation of the designs prepared by the GNOME Designers (see https://live.gnome.org/Design/Apps/Clock)
Together with Allan Day, we are mentoring the awesome Emily Gonyer for her SoC project as well as our free time superhero Eslam Mostafa. One of the nice (non-techie) things about GNOME Clocks is that it allowed us (the mentors) to identify patterns of healthy communication between designers and developers (I will be preparing a post about this soon).
The project is in a more or less good development state… Here are some screenshots of the current status.
Clocks view
Alarm view
Timer & Stopwatch views
We have been hanging around #gnome-clocks for a bit to make the development environment protective and focused for our new devs. Now I think we can move forward. You can find the code at http://git.gnome.org/browse/gnome-clocks
It is all written in python so it should be easy to just jump in and contribute to a “core app” for GNOME. We need some help with our bugs and most help with autofoo and hosting on jhbuild. So if you are up for it you can find me or allan on #gnome-design & #gnome-clocks and files bugs at https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:%22clocks%22+
Have a nice weekend 
So, what is the use case for setting up world clocks that can only be viewed by opening this application? If someone is setting up world clocks there is only one likely scenario: they need to frequently check the time in some other part of the world. If that is the case, the info should be available either in the top panel directly (which could get cluttered), or within a top panel menu (so, within the clock/calendar menu).
The timer gui uses joggers to change the times. I have found these to be very hard to use, even on touchscreens. The reasons are that they are designed for mapping what they do to their relative positions, which speaks to nice, fairly universal concepts of forward/back, up/down, but does so at the cost of usability (actually changing the times). The fastest way to create time periods of the largest range is with the keyboard using entry boxes of hours, mins, sec. When clicked in, a dial shows up with the appropriate range for each interval. Obviously this biases things towards the keyboard users but it allows one to make timers/alarms more accurately, and more quickly (a tradeoff of accuracy or speed is really a problem with the current design since the mechanism allows one only linear access patterns, and a non-constant time to create each timer) for both keyboard and mouse users.
Also, it isn’t clear if you can create multiple timers. That is, let you save timers for use againlater, or to let you chain together timers to remind you when to start/stop an activity. The later is really useful for time management techniques or cooking.
Lastly, you need a map option for accessibility with regards to setting the world clock. A person may not know how to correctly spell the region (for instance, they spell caracas, korocis, or whatever– it’s not the kind of thing you’re going to have an algorithm good enough to guess what they mean… honestly, I don’t think one exists yet anywhere) they are interested in, nor the gmt offset. This doesn’t sound far fetched and is a serious problem.
I’ve been bitching about the state of gnome 3 and unity clocks for a while, so I’m happy to see new dev! I’d love to jump in and help out – are the intructions anywhere about what I do with this repo?
[...] Via | Seif Lotfy [...]
I was just looking through the code (since I could not get the program to run). And I noticed something that I HAVE to ask: Do you provide a way to add non-city clocks? For the city clocks you seem to use GWeather(!?) to get cities and you safe cities as clocks. But there are tons of non-city clocks which are very useful: UTC is the main example, but here are many others http://en.wikipedia.org/wiki/List_of_time_zone_abbreviations
Please note that the answer: ‘just use a city without an UTC offset instead of UTC’ is not a good answer. Often I get a time in UTC or PDT and I want to know how long it is until that time. If I have a clock labeled “UTC” and “PDT”, everything is fine.
If I have to open my webbrowser to search for a city without offset to “PDT” and then check my clocks again, that would not be ideal.
SO: please have a look at this use-case and check that it can be done (please do not only check UTC, this can be used in the clock-applet, but no other non-city clock can be used).
my pal pitched in this program his name is islam mustafa from egypt
)))))))))))))
way to go brooooooooo
I tried running it but no window or anything appears and it spits out this a million times:
(main.py:2442): GLib-GIO-CRITICAL **: g_dbus_connection_register_object: assertion `object_path != NULL && g_variant_is_object_path (object_path)’ failedTerminated
Then I had to kill the process.
So what about weather can that also please see some love?! (:
@anonym
Mccann says weather doesn’t belong with time. He doesn’t see them as related things.
See the discussion on the design page linked above.
I thought core apps would be developed in vala/c/js.
That is really interesting, You are an excessively professional blogger. I have joined your feed and look ahead to searching for extra of your fantastic post. Additionally, I’ve shared your site in my social networks!