diegocr
Collab on extending this addon or remake?
This is a crucial addon. Especially for getting addons from desktop onto android for testing. I was hoping to collab with multiple/whoever is willing to extend/recreate this. I wanted to add in some features:
- All work done off main thread (using jszip for zip stuff)
- Add installing from a folder support, like xpicompiler - https://addons.mozilla.org/en-US/firefox/addon/xpicompiler/
- By default, extensions should be installed as temporary addon using
AddonManager.installTemporaryAddon(nsiXpi)- Collab point - There is an issue, in that the install locks the file on disk, so we cant delete/edit it. The file remains locked by firefox. We should probably file this on bugzilla OR figure out what installTemporaryAddon is doing internally and do it ourselves.
- Add option to sign the addon on AMO, here is code that does it - https://github.com/Noitidart/AMO-Addon-Signer - user has to put in their amo key and secret. I have code to help user generate it automatically, I used it in Foxified - https://github.com/Noitidart/Chrome-Store-Foxified
- Install JPM addons
- Collab point - bootstrap.js of JPM addons is very simplified, I would need help on the details or contribution on generating a install.rdf from the package.json
- Install webextensions - just zip it, make it an xpi and install - nothing special needed (unlike jpm addons)
- Front end panel, similar to XPICompiler - I was hoping to use react/redux -
about:page, should load in content process (i have the communication API all done - i use it in many addons) - would be awesome if a ux/designer collabs to create a nice clean layout.
Of course the github would have inlay as seen in GitHubExtIns. For the signing option, we can have status update within here itself, no need for forwarding them to the front end panel.
Just brainstorming. I am totally ready to take this in any other directions per collaborators or user feedback.
Anyone willing to kick this project off? Are you interested @diegocr? Rather then something seperate should we just keep it "Github Extension Installer" and add the front end on the side for working with local files?
Thank you @marsjaninzmarsa - I am interested in landing a variant of this. It should install WebExtension from github directly into browser from Github.
Are you interested in collaborating?