I shall attempt to write an "official" response: 1. Yesterday, Atul added a function to CmdUtils called CmdUtils.parserVersion. It is based on Gary's solution (you got credit in the commit message! https://ubiquity.mozilla.com/hg/ubiquity-firefox/rev/651ba8eea7bf) and provides a way to support a Parser1 and Parser2 command in the same file. Someone should be adding info on this to the Command Update tutorial shortly.
2. The Herd is not Parser1/Parser2 aware right now, which means it's not indexing new commands. The Ubiquity team decided that getting 0.5 out to the community was our top priority, so we deferred updating the Herd. 3. Using CmdUtils.parserVersion will probably not be final solution for how to host 0.1 and 0.5 feeds, but it will work for those of you who are working now to get your feeds updated to support both sets of users. In the long run this solution makes things difficult for parsing commands in the herd, so we are exploring other options. 4. I think everyone will agree that breaking the API and branching the release so as not to break 0.1 commands has presented some challenges that we're working through. Thanks for your patience. I'd love to hear feedback from command developers who have been early upgraders about how we can make this process easier for people who follow in your footsteps, and I appreciate those who have already offered feedback about this. Heather On Jul 9, 12:38 am, Timofei Shatrov <[email protected]> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
