> So haven't I essentially "broken" the script for people who haven't > yet made the jump to 0.5? Is there a "recommended" way for 3rd party > scripts to handle this?
For the time being, I don't think there's anything we can really particularly do on the command feed-side but, as is being discussed and Aza just presented some thoughts on [1], it's currently looking like we'll push a 0.1.9 release for the 0.1.x users which will tell them when they try to subscribed to a 0.5 API command that they must use Ubiquity 0.5. [1] http://vimeo.com/5483375 This should help with these users you describe who currently could try to subscribe to your command and "bad things" would happen. > And just 'cause I'm curious, would it be technically possible to > create a command for 0.5 that transformed old commands on the fly (say > a verb called "compat")? So I could invoke ubiq and type "compat OLD- > COMMAND-NAME stuff-i-want-it-to-act-upon" and it would sort out the > messy bits? > > I'm guessing this is a non-trivial problem, or else it would have been > built into the architecture of 0.5… This is indeed a non-trivial problem, but we're trying to support command authors during this transition with a command conversion tutorial [2]. This tutorial will walk through the conversion process (hopefully in an easy to understand fashion). And if it's not easy to understand, please let us know! I'd love to get some feedback on it. [2] https://wiki.mozilla.org/Labs/Ubiquity/Parser_2_API_Conversion_Tutorial mitcho -- mitcho (Michael 芳貴 Erlewine) [email protected] http://mitcho.com/ linguist, coder, teacher --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
