ffalarms 0.3 -- recurring alarms

Łukasz Pankowski lukpank at o2.pl
Tue Oct 27 00:21:18 CET 2009


Marcel <tanuva at googlemail.com> writes:

> Am Montag, den 26.10.2009, 23:09 +0100 schrieb Łukasz Pankowski: 
>> Marcel <tanuva at googlemail.com> writes:
>> 
>> > Am Montag, den 26.10.2009, 22:15 +0100 schrieb Łukasz Pankowski: 
>> >> Marcel <tanuva at googlemail.com> writes:
>> >> 
>> >> > Am Montag, den 26.10.2009, 02:07 +0100 schrieb Łukasz Pankowski: 
>> >> >> Hi
>> >> >> 
>> >> >> I have just released ffalarms 0.3, it adds recurring alarms, please test
>> >> >> it before depending on it.
>> >> >> 
>> >> >> For me the most missing feature now is being able to edit the alarms and
>> >> >> postponing in the acknowledge window.  Ideas and comments are welcome.
>> >> >> 
>> >> >> 
>> >> >> Notes:
>> >> >> - add support for recurring alarms, attaching messages to alarms, and
>> >> >>   choosing alarm date from a calendar
>> >> >> 
>> >> >> - add configuration option for alarm volume, alarm_script and alsa_state
>> >> >> 
>> >> >> Download:
>> >> >> http://projects.openmoko.org/frs/?group_id=260&release_id=580
>> >> >> (I also provide libical, in case it is not in your distro)
>> >> >
>> >> > Yay! I use ffalarms mostly more than once a day and it's just great to
>> >> > have it. Thanks for your work! :)
>> >> >
>> >> > Although I know you're not too fond of it - what about making it
>> >> > possible to simply turn an alarm off without that puzzle? It's quite
>> >> > annoying me from time to time, especially when I'm just finishing it
>> >> > when its regenerating and I need to hear that alarm once again...
>> >> 
>> >> Yes I am quite attached to the puzzle it is there since the beginning
>> >> :).  BUT: it is there for the particular purpose to avoid accidental
>> >> turning off of the alarm.  And now Elementary [1] comes with the widget
>> >> that plays that rule well enough -- slider -- without the annoyance of
>> >> the puzzle (yes, I say it too).
>> >> 
>> >> v0.3 adds the acknowledge window that displays after the puzzle, and
>> >> consider merging the two into one acknowledge window with two sliders:
>> >> 
>> >> * first one to turn off the alarm sound (when it is loud you want to
>> >> turn of this first and not read the message), then
>> >> 
>> >> * the second to acknowledge you read the alarm message (this will appear
>> >> if you slide the first one).
>> >> 
>> >> What do you think of such interface?
>> >
>> > The slider is a good idea, already works fine in shr-today. (Which
>> > didn't survive my scaling experiments very well...)
>> > I'm not sure if two windows for turning off the alarm and then
>> > acknowledging the alarm messages are nessecary. Couldn't we have one
>> > slider in the upper third of a window to turn off the alarm (maybe even
>> > red?! I fear that might be hardwired to the theme...), the alarm message
>> > in the middle and the acknowledgement switch for that on the bottom. So
>> > one could if there's no mesage or its trivial just slide the lower
>> > slider and both the message window and the alarm disappear/stop without
>> > having to slide twice. What about that? :)
>> 
>> I was saying about one window:
>> 
>> |--------------------|
>> | Message            |
>> |                    |
>> |                    |
>> | [Turn off slider]  |
>> | [ACK slider] (*)   |
>> |                    |
>> | {Close button} (*) |
>> |                    |
>> |--------------------|
>> 
>> where (*) are hidden until you slide the turn off slider.
>> 
>> The other idea which might be better is to use single slider which you
>> slide right to turn off the alarm and slide back to ACK it.
>> 
>> |------------------------------|
>> | Message                      |
>> |                              |
>> |                              |
>> | [Turn off=> / <= ACK slider] |
>> | {Close button} (*)           |
>> |                              |
>> |------------------------------|
>> 
>> I think it is even simpler and not that annoying, what do you think?
>> (I hope you like it).
>> 
>> In your idea I would be afraid I can use the wrong slider (may be would
>> require the ACK slider to be normal size (to make the difference
>> obvious) which would be less finger friendly), but would have to test it
>> on myself see if it is a real or imaginary problem.
>
> First approach: I'd have placed one slider at the top and one at the
> bottom of the window, with the alarm message (in case such exists) in
> between them. Isn't that enough to differentiate them?
>
> Would the second approach require one to "drop" the slider once to make
> E recognize that it has been slided? Or could one slide it right and
> back in one movement? I guess the former is the case... I'd still prefer
> some approach that allows getting rid of the window with just one
> movement/click. And what I see right now: Do you plan to make another
> button to close the window visible after sliding ACK? That seems too
> complicated to me.

Yes, it would require to "drop" the slider, (2) below is simpler.

1) Your interface is with two sliders and no buttons.

That may be a good aproach, I will have to think of that later and may
be test it on myself.  The problem is that now if you acknowledge the
alarm there is no way back to read the alarm info -- it is deleted
(unless recurring).  That is why I want to make it two step
(slider/button), so I may do the following:

2) Another posibility is:

One slider to "Acknowledge" the alarm (and also turn off the sound), if
you slide it right the Close button appears (Elementary buttons are
clicked with mouse down, no way to undo by sliding off the button).

If you want to explicitely NOT acknowledge the alarm you have to: slide
it right (to turn off the sound) and slide it back to make it
unacknowledged.



More information about the community mailing list