Re: [Usability] Request for feedback: Alarm Clock UI

["Johannes H. Jensen" <joh pseudoberries com>]

On Wed, Jan 6, 2010 at 10:55 PM, Allan Day <allanpday gmail com> wrote:
>> I've done a quick review of your suggestions and will respond with
>> more detailed thoughts as soon as possible :-)
>
> No problem. :)

I have added my notes to the wiki page[1] - could you have a quick
look and respond with your thoughts? Thank you :-)

>> I'm a bit unsure about using a popup menu as the list of alarms
>> though. Traditionally a menu item can only be clicked to activate one
>> action, not multiple as your mockup suggests (snooze, dismiss and
>> delete). I'm not sure this is even technically possible in GTK+...
>> They could appear in submenus, but that's not as elegant. It might be
>> possible to display some sort of popup-window with a custom list
>> though...
>
> In my mind, applets shouldn't really throw up windows. The purpose of
> applets is to have an interaction element that is visible and accessible
> all the time, irrespective of window placement or workspace. Once you
> start using windows for your primary interaction, that advantage is
> lost.

I completely agree - having a dropdown list as you propose would be
very neat. It would indeed make the alarms more easily accessible.

> That said, I completely understand the implementation difficulties that
> exist with what I'm proposing.

Yeah I'm still a bit divided on the issue. A window provides much more
flexibility and design possibilities. Just look at the NetworkManager
applet for example - it really has taken the concept of a menu to its
limits if you ask me... On the other hand, the pulseaudio volume
applet does not use a menu at all for the volume slider. So placing a
list of alarms below the icon is technically possible without using a
menu.

>> Another reason I'm reluctant is that I've kinda already implemented a
>> version of the alarm list window[1] mentioned in the BetterUI wiki
>> page[2] :-P What do you think of using a window instead of a popup
>> menu?
>
> Ha, I was too slow. :)

Or my fingers were itching too much to start coding. :-)

> A window isn't necessarily wrong, it just
> wouldn't have the advantage that I've described above. And hey, it's
> just my opinion.

Yeah, a window is also nice in the sense that it allows the user to
more closely monitor his/her alarms. I have to think some more about
this before I decide on what to do :-P

> You could easily apply the recommendations I've made in my review to
> your window design. Off the top of my head, I'd recommend not using
> editing functionality (just add and remove) and not using checkboxes to
> activate/deactivate alarms (just have them active by default). Also,
> make sure that your Snooze and Stop buttons (etc) grey out in the right
> circumstances.

Yeah, they definitely also apply to the window design. What's the main
reason for not using editing functionality though? To avoid cluttering
up the applet with unused alarms? You suggest that to disable an alarm
the user just deletes it instead?

> That's a nice mockup, by the way. :)

Thanks :-)


Best regards,

Johannes

[1] http://live.gnome.org/AlarmClock/Blueprints/BetterUI/More