Not actually implemented yet, but...

http://theunfocused.net/2009/01/16/ubiquitous-information-part-1/

- Blair




On 27/02/2009 11:32 PM, Christian Sonne wrote:
> On Fri, Feb 27, 2009 at 10:07 AM, GooseusTheGreen
> <[email protected] <mailto:[email protected]>> wrote:
>
>
>     So I'm wondering about interfacing with web APIs which require API
>     keys... such as my drop.io <http://drop.io> command.  I have my api
>     key hardcoded for
>     the command I'm subscribed to, but I can't share it with everyone like
>     that.  I also can't expect users to pass in their own API key at the
>     command line everytime and if they just copy the code locally and add
>     the key then they won't be subscribed to my actual command and won't
>     know when I've made updates, etc.
>
>     I was wondering if there was any way I could store a value from the
>     user permanently (or until Ubiquity/Command is uninstalled or is
>     manually changed)?  Is there a Ubiquity 'registry' or similar DB/tree
>     that I commands can save to and recall from another session?  Such a
>     thing would also be good for setting certain preferences for commands
>     as well.
>
>
> I'm not actually sure if we have an API for this yet, but I can tell you
> that this is usually done by saving a pref in
> extensions.ubiquity.<commandname>.<prefname>...
>
> I should note though that it's probably not a good idea to do this all
> too often, we wouldn't like to pollute the prefs too much.
>
> -- cers / Christian Sonne
>
>
>
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ubiquity-firefox" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/ubiquity-firefox?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to