Get flash to fully experience Pearltrees
Today we announced Mozilla’s Open Badge Infrastructure project , an effort to make it easy to issue and share digital learning badges across the web. More and more people are looking at badges to show skills and achievements online.
This page contains small, self-explanatory code snippets. Output Saving the current web page to a local file Although the following code does not prompt the user for a filename, you can do so using the file picker component .
Downloading files To download a file, create an instance of nsIWebBrowserPersist and call its nsIWebBrowserPersist.saveURI() method, passing it a URL to download and an nsIFile instance representing the local file name/path. If you don't need detailed progress information, you might be happier with nsIDownloader . Downloading Binary Files with a Progress Listener
Add-on Versioning Add-ons should specify their versions using the Toolkit version format . As a rough overview this is a version string split by periods, some examples: 2.0 1.0b1 3.0pre1 18.104.22.168 Note: Before Firefox 1.5 the more basic Firefox Version Format was used: major.minor.release.build[+] where only digits were allowed. The toolkit version format supports the Firefox version format but allows greater flexibility.
Please don't edit this page directly, either add comments to the discussion page or to the threads in the newsgroup or forums . See also the original newsgroup thread where extension authors discuss the potential impact to the addon community. Overview This specification discusses changes to the Toolkit Extension Manager in Gecko 1.9 with the aim of improving the security of automated add-on updates.
Bonjour J'ai repris une extension (privée) d'un copain depuis plusieurs mois, et je n'ai pas réussi à mettre en place une mise à jour automatique jusque là. Je m'y suis penché plus sérieusement depuis ce week-end, mais j'obtiens toujours la même erreur lorsque je souhaite mettre à jour (sur Firefox Portable) :
Gosh, Ed, I'm sorry to hear this is giving you problems. Here's all you need to do: 1) Open McCoy and highlight the RSA entry you created when you installed the program. 2) Using McCoy, click on the "Install" button and locate your theme's install.rdf file. This inserts the updateKey. 3) Package your theme into a .jar file, calculate a hash, and place the updateHash entry inside the update.rdf file you will be using on your site. (See below for additional info on how to calculate the hash.) 4) Using McCoy, click on the "Sign" button and locate the update.rdf file.