kristopher.dick
-
11 votescompleted ·
AdminCarter
(Admin, two forty four a.m.)
responded
This has been implemented by the “Locale Call Detection Plug-in” plug-in condition for Locale 1.0. To find this plug-in on the Market, simply open Locale and choose Get Plug-ins from the menu.
kristopher.dick
gave this 1 vote
·
-
477 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
At long last Locale 3.0 introduces the Calendar condition to detect events on your Google Calendar, Exchange Calendar, or any other calendar supported by Android.
While Locale 3.0 is available for Android 2.2 or later, the Calendar condition requires Android 4.0 or later. To learn more about Locale 3.0, please see our release notes here http://blog.twofortyfouram.com/post/19303488607/locale-3-0
kristopher.dick
gave this 2 votes
·
-
774 votesunder review ·AdminCarter
(Admin, two forty four a.m.)
responded
The original request here was for a logical NOT operator, although it doesn’t make sense to create a logical NOT operator in Locale. Most of the time, NOT isn’t the right way of thinking about a Condition. For example, NOT 9 am to 5 pm could be redefined as 5pm to 9am. NOT at work would simply be the Default situation. For the other conditions built-in to Locale, thinking about the problem in a different way usually means that NOT isn’t needed. If a Condition truly needs NOT logic, then that should probably be put into the individual Condition’s UI itself rather than as part of the Edit Situation screen in Locale.
Although this request is for a NOT operator, I believe the underlying request here is a way of detecting the transition between situations. The strongest use case would be detecting when you’ve left a particular Location. While Locale… more
kristopher.dick
gave this 2 votes
·
-
21 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
Locale 1.0 offers significantly improved location detection that should solve this problem. You don’t have to do anything to configure it; Locale 1.0 handles this automatically. The solution doesn’t work exactly as you’ve described here, because the solution in Locale 1.0 is better :).
Locale 1.0 is available on the Android Market today in countries that support paid apps. Full release notes are here: http://www.twofortyfouram.com/notes.html
kristopher.dick
gave this 1 vote
·
-
11 votesdeclined ·AdminCarter
(Admin, two forty four a.m.)
responded
While an interesting idea, our studies have found the location data in contact lists is not very useful. Most people don’t even have addresses in their contact list. And for those addresses that are in the contact list, most of the “locations” in your address book aren’t really going to be places you’d want the ringer to be silent (e.g. who puts the movie theater or library in their address book?)
The best use case I could see for this would be a consultant who travels to a number of different clients, and would like his ringer to turn off at each of those client locations. Having done that type of work in the past, I could see such a feature useful. I just don’t think currently there are enough people who would need this sort of functionality.
Is there any important use case that’s been missed?
kristopher.dick
shared this idea and gave it 1 vote
·
-
6 votesdeclined ·AdminCarter
(Admin, two forty four a.m.)
responded
Locale 1.0 allows multiple locations to be added to a situation, by long-press on the Add Condition button. This effectively gives a primitive with which you can “draw” a non-circular area by simply partially overlapping several circular areas.
Actually allowing non-circular locations to be drawn wouldn’t work well, because the location information Locale obtains from cell towers, Wi-Fi, and GPS is represented by a single point with an error. In other words, Locale can only work in circular locations.
kristopher.dick
shared this idea and gave it 1 vote
·
-
10 votescompleted ·AdminCarter
(Admin, two forty four a.m.)
responded
Preliminary support for plug-in conditions is now supported in Locale 1.0. Documentation of these APIs is available at http://www.twofortyfouram.com/developer.html
Locale 1.0 is available on the Android Market today in countries that support paid apps. Full release notes are here: http://www.twofortyfouram.com/notes.html
kristopher.dick
gave this 1 vote
·
kristopher.dick
commented
·
These battery life/performance issues would be the responsibility of the plug-in, though. Locale should be accepting a condition intent from condition plug-ins. Then all you're left dealing with is the id and value of the condition. Some concern regarding perception of locale as a resource hog resulting from greedy condition plug-ins is understandable. However, with the Donut power manager features, this is readily addressed with a "my phone is slow, eating batteries, etc" button that automatically links to the Battery Use page.
The "On a Call" condition can be useful for so much more, though. I might want to use it to update my various statuses, or pause my media player, or tell my computer to open my calendar app (When I'm at home), or any number of other thing's that haven't been imagined. The application of a single use case doesn't equate to a limit on usability, but an example of it.
Of course, if the conditions API were opened up there wouldn't be the constant stream of ignored requests for additional conditions.