Allow separate "home" and "away" locations

[GoogleCodeExporter]

I have received a suggestion for a portable version of the app for use just in 
LAN parties, but that's extremely complicated to implement (because of 
interactions with an existing base version).

However, the primary motivation for this is to handle non-"home" situations 
cleanly, and having different location profiles seems a good way to handle 
this. A sub-menu from the main context-menu to pick the active profile seems 
like a reasonable UI - the active profile should also be listed in the tooltip 
hover text for the limiter applet too.

The most subtle aspect of this is the interaction with the location selection 
webservice; there also needs to be a way to request redetection and ideally to 
express a preference for the autodetected, centrally managed rules over a local 
custom one (including perhaps a separate kind of update prompt similar to the 
version-upgrade one if the user's current ISP selection has different rules 
from the latest one at the server end).

Original issue reported on code.google.com by nigel.bree@gmail.com on 9 Dec 2011 at 4:46

[GoogleCodeExporter]

Internally, it's attractive making "custom rule" a type of location, with this 
profile being uploadable as a suggestion to the webservice; internally, the 
setfilter.js script will probably want an internal invisible temporary profile 
to support 'Cancel' in the profile-exit UI, and one wonders whether it would 
also be useful to have an implicit "block all traffic" profile as well?

Original comment by nigel.bree@gmail.com on 15 Dec 2011 at 10:51

• Changed state: Started
• Added labels: Milestone-Release0.5

[GoogleCodeExporter]

Implemented in the v0.5 release, will close after more testing

Original comment by nigel.bree@gmail.com on 20 Dec 2011 at 11:37

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by nigel.bree@gmail.com on 1 Feb 2012 at 9:10

• Changed state: Verified