[IAEP] [PATCH] add clock frame device

[Eben Eliason]

A few thoughts.

1. I think that we need to show the leading 0 when the hour is a one
digit number, eg. 08:07. Otherwise everything in the Frame is going to
shift depending on the time.

2. I find the radio buttons a little odd. I wonder if we could have a
single menu item that either a) reads "Use 24 hour clock" and uses a
checkmark to show its state or b) toggles between "Use 24 hour clock"
and "Use 12 hour clock" when clicked.

3. We could expose some more useful info in the palette, both primary
and secondary. The primary palette, for instance, could read:

My Clock
Friday, May 8, 2009

I'd put the date label in the secondary string, so we can retain the
standard practice of listing the device name in the primary. Including
the day of the week would be nice, and displaying the date in a human
friendly manner will make it feel less cold & "computery". I also
think (this is a future feature suggestion, and needn't be there in a
first pass) that the secondary palette should have a nice little
inline calendar as well.

4. This is another future suggestion: we've talked in the past about
having an option on various devices which jumps directly to the
corresponding section of settings. This device should have a "Show
Date & TIme Settings" option when we add that capability.

5. Finally, I'd like to see if it's at all readable if we limit the
clock to a single unit like the rest of the devices icons.

I'll try to make some mockups of all of these thoughts before
tomorrow's design meeting. Let me know your thoughts on the
suggestions.

Eben



On Fri, May 8, 2009 at 7:51 PM, Martin Dengler <martin at martindengler.com> wrote:
> [ccing sugar-devel as well]
>
> On Sat, May 09, 2009 at 09:18:02AM +1000, forster at ozonline.com.au wrote:
>> > The below patch adds a clock device to the frame:
>> Thanks Martin, I have wanted a clock for a long time.
>>
>> Can we please have an idiots guide for installation?
>
> Unfortunately, you can't yet in any released version of Sugar.  The
> purpose of my mail was not to give anyone besides a developer code
> they could actually use (sorry for the disapointment - I should have
> pointed this out very clearly).  The purpose was both to solicit
> another round of feedback on the design/behavior, and also to
> demonstrate that I had actually written some code that did it (note I
> do not say "the best code" nor "the code anyone believes should be
> released").
>
> If you have a moment to suggest any improvements you can think of that
> would be most helpful.  I can't guarantee to implement them all but I
> (and the Sugar world) am listening seriously.  The links again are:
>
> http://www.martindengler.com/tmp/screenshot_clock_device_frame-06_a6_a689bf1e-3f34-4da3-afed-aa910ab4f677.png
> http://www.martindengler.com/tmp/screenshot_clock_device_frame-07_84_841da15d-9bd7-4fe4-aada-8e8ab723f806.png
> http://www.martindengler.com/tmp/screenshot_clock_device_frame-08_4b_4ba1059e-4db9-4f22-8661-7916f6a167f8.png
>
> However, if you happen to be running SoaS, you can run the clock
> "as-is".  Start the Terminal activity and execute (cut & paste) these
> commands:
>
> su -
> cd /usr/share/sugar/extensions/deviceicon
> wget http://www.martindengler.com/tmp/clock.py
>
> ...and then restart Sugar by pressing Control-Alt-Erase at the same
> time.
>
> If there's enough interest someone (maybe I) may backport the clock to
> the currently-released-but-very-old-in-developer-terms Sugar software.
>
> You may also be interested in my prior clock design, which I did
> backport to the latest released OLPC build:
> http://wiki.laptop.org/go/User:MartinDengler#Build_767_.2F_801_.28current_stable.29
>
> Martin
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>