Talk:Thunderbird:Extension Installation: Difference between revisions

Talk:Thunderbird:Extension Installation (view source)

Revision as of 23:55, 9 April 2008

691 bytes added , 9 April 2008

no edit summary

Killjay

33

edits

@@ Line 6: / Line 6: @@
 Save to Disk if application/x-xpinstall;app=(Other Moz App name)
-Alternativly if the add-in is a multi-MIME *.xpi the add-in site would offer multiple links, one link per MIME where app=xxxxx is in the link.
+Alternatively if the add-in is a multi-MIME *.xpi the add-in site would offer multiple links, one link per MIME where app=xxxxx is in the link.
 Method One would need minimal code support leveraging existing MIME handler. Disadvantage is local install stays like present where user need to know where d/l was saved to.
@@ Line 12: / Line 12: @@
 Method Two would need Add-in page Webmaster support and Evangilisem to third-party sites.  For error resistance each app would need reject code that filters by parsing on the app=xxxxx portion of the MIME extension to prevent cross-app install of invalid features (bookmarks in mail, or LDAP in browser).
-One of the features of MR Tech Local Install that appeals is the ability to designate archive folders for add-in's. This code should be built into Mozilla Apps with an eye to a standard location per supported platform. On Windows 9X in the folder X:\Windows\Application Data\Mozilla\Addins\(app name) where other folders at the ..\Mozilla\.. level would be Firefox, Tunderbird, etc. Then when an add-in is d/l or updates, the *.xpi would be archived and have a standard path for install.  An added benifit is rollback and ease of adding add-in's to a new profile.<br>
+One of the features of MR Tech Local Install that appeals is the ability to designate archive folders for add-in's. This code should be built into Mozilla Apps with an eye to a standard location per supported platform. On Windows 9X in the folder X:\Windows\Application Data\Mozilla\Addins\(app name) where other folders at the ..\Mozilla\.. level would be Firefox, Tunderbird, etc. Then when an add-in is d/l or updates, the *.xpi would be archived and have a standard path for install.  An added benefit is rollback and ease of adding add-in's to a new profile.<br>
 --[[User:Killjay|Ron K.]] 17:19, 27 March 2007 (PDT)
+The MIME type approach has a serious down side not anticipated in my prior remarks.  During discussion in mozilla.dev.apps.thunderbird the issue of mirrors being used to serve add-on's was brought up.  To be workable, way too much redundancy would be required and the load on mirrors would more than double. Thus my thinking turns out to be unworkable.
+What has become possible is a "Drag and Drop" ability to drag the link from the AMO site onto the Thunderbird Add-on Manager to initiate install of an extension or theme. Alternatively, those who want an archive copy can drag and drop to a desktop first and then install from there.
+--[[User:Killjay|Ron K.]] 16:55, 9 April 2008 (PDT)
 --[[User:Philip Chee|Ratty]] 02:28, 28 March 2007 (PDT) When browsing with SeaMonkey for mailnews extensions like Tagzilla, it is unclear whether the user wants to install into SeaMonkey, or download for later installation into Thunderbird - There are people who use only the SeaMonkey Navigator but use Thunderbird for MailNews.