I've updated a couple of scripts I've published so they are compatible with 0.5, but then I published the new source to the same URL…
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 those of you running 0.5, the very simple percent encode/decode script is at http://earth2marsh.com/ubiquity/ ] 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… --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
