turn ringer off for a specified time

Karsten Ensinger karsten.at.openmoko at onlinehome.de
Fri Aug 17 08:21:59 CEST 2007


R. Tyler Ballance wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> On Aug 16, 2007, at 10:13 PM, Karsten Ensinger wrote:
> 
>> Clarke Wixon wrote:
>>> Thomas Wood wrote:
>>>> Sounds interesting, although I would hate to use the feature in a
>>>> meeting that over ran. Do you use the feature yourself?
>>> Of course, there are a couple of other ways to deal with the 
>>> overlong-meeting problem: allow some extra time for it in the first 
>>> place (which can be inconvenient if the meeting *doesn't* run long), 
>>> or re-up the mute time when you notice the meeting running long 
>>> (which is easy enough to do).
>>
>> Why not use the GPS for determining, if one already left the
>> meeting room?
>> Take a considerable distance from the center point (which is
>> determined during the time of the meeting) and extend the
>> time of muting following the end time of the meeting until
>> the distance is exceeded or the user marks the meeting as
>> "ended".
> 
> Interesting but extremely complex for a simple problem.
> 
> Assuming you sync your calendars to the application, when an event is 
> marked as "quiet" or semantically, looks like a meeting, turn the phone 
> to vibrate. When the event's specified end time elapses, return to the 
> previous ring-state.
> 
> Use the data the user already has provided.

Maybe you haven't got the problem?
The point mentioned here was the one you/we quoted first:

 >>>> Sounds interesting, although I would hate to use the feature in a
 >>>> meeting that over ran. Do you use the feature yourself?

So the problem is NOT to switch back to the profile set before
the meeting, but the overrun of the end time.
When you simply switch back to the previous settings when reaching
the end time of the meeting but the meeting lasts longer, one has
to remember to adjust the end time in his calendar entry before
reaching the end time.
To avoid this, my suggestions was to use the location as additional
information for the duration of the muting.
Of course one could "ask" the user if it is ok to switch back.
But we want as much as smart as possible, don't we? Just mark a
calendar entry as meeting and getting the muting as long as you
do not leave the "meeting area" without any need to think about
a prolongation of the muting timeframe.

Regards
Karsten



More information about the openmoko-apps mailing list