Extension Manager:Sqlite Storage: Difference between revisions

Extension Manager:Sqlite Storage (view source)

203 bytes added , 18 July 2008

canmove, Confirmed users

1,570

edits

@@ Line 89: / Line 89: @@
 Currently the UI is purely template based which has meant that plugin and add-on search results have ended up being put into in-memory rdf datasources. Switching away from templates will allow us to break this into a more straightforward approach. We just have one richlistbox per pane in a deck, on startup we create richlistitems for every installed add-on, plugin and search results when available.
-For the install and add-on lists we will have to have some kind of notification from the EM backend to the UI to let it know that a change has been made that might require updating the UI. Add-on properties don't change all that much, mainly state changes which should make this easy to handle. We already have state changed exposed through observer notifications, we can likely reuse/adapt that method.
+For the install and add-on lists we will have to have some kind of notification from the EM backend to the UI to let it know that a change has been made that might require updating the UI.
+For installs the already present <code>nsIAddonInstallListener</code> interface will be used. There will be some cleaning up so it gets passed the same <code>nsIAddonDownload</code> object for every single call.
+Properties for installed add-ons don't change all that much, mainly pending operation changes. We already have state changes exposed through observer notifications, we can likely reuse/adapt that method.
 ==API==