Extension Manager:API Rewrite: Difference between revisions

Extension Manager:API Rewrite (view source)

1,014 bytes added , 13 November 2009

no edit summary

canmove, Confirmed users

1,570

edits

@@ Line 41: / Line 41: @@
 Certain types on installs may skip steps. Installing an add-on from the file system for example may jump straight to the Downloaded (or Checking) state since there is no need to download it.
+==Dependencies and Bootstrapping==
+It is anticipated that at some time automatic downloading of dependencies and bootstrap add-ons will be implemented. This is intended to happen in the AddonInstall Downloading and Checking states. Once the initial file for an add-on is downloaded the AddonManager checks to see if a repository is installed to handle it.
+If there is a repository to handle the add-on then it is used to check for compatibility, updates and dependency information. And dependent items will be downloaded before the AddonInstall moves to the Downloaded state, allowing the item to be installed and usable with minimal delay after that point.
+If there is no repository to handle the add-on then some form of bootstrapping mechanism will be used to find and add-on that contains a repository to handle the new add-on. As an example we may have a means to detect that the file is a zip file containing a manifest.json file which would suggest we should download the Jetpack runtime and install it.