On 9 июл, 00:29, Gary Hodgson <[email protected]> wrote:
> Timofei, I posted this in an earlier
> thread<http://groups.google.com/group/ubiquity-firefox/browse_thread/thread/...>if
> it's at all useful...
>
> For what it's worth this is my solution to the upcoming 0.5 release. It's
> certainly not elegant, but it works, and it means I don't have the hassle of
> managing two versions of the commands whilst people migrate.
>
> var isParser2 = function(){
> var prefs = Components.classes["@mozilla.org/preferences-service;1
> "].getService(Components.interfaces.nsIPrefService);
> var branch = prefs.getBranch("extensions.ubiquity.");
>
> return (branch.getPrefType("parserVersion") != 0) ?
> branch.getIntPref("parserVersion") == 2 : false;
But would herd be able to parse such a code? I'd prefer if there was
an official solution from Ubiquity developers, as this issue would
definitely prevent me from transferring my commands to 0.5 format.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
