Greasemonkey: WebExt: External editor support (read/write extension directory)

Created on 5 Jun 2017 · 5Comments · Source: greasemonkey/greasemonkey

The runtime API provides multiple ways to read files from the extension directory, so what is left to explore is how to write files to the extension directory.

I think it's worth exploring if runtime#getPackageDirectoryEntry and fileSystem#getWritableEntry can used to write files to the extension directory, but I fear that the permission system might interfere.

Source

silverwind

👍1

Most helpful comment

FYI: https://violentmonkey.github.io/2017/03/14/How-to-edit-scripts-with-your-favorite-editor/

yfdyh000 on 12 Oct 2017

👍6

All 5 comments

Turns out fileSystem is not available to extensions, only to apps. So with a read-only API, it might still be possible to implement editor support but things like auto-update won't be possible.

silverwind on 5 Jun 2017

https://wiki.mozilla.org/WebExtensions/RoadMapFirefox57#Filesystem_Access
https://bugzilla.mozilla.org/show_bug.cgi?id=1246236

yfdyh000 on 9 Jun 2017

This is effectively impossible. The only thing I can imagine is to use native messaging and a custom written local binary. That will be a lot of work, at best.

arantius on 25 Jul 2017

FYI: https://violentmonkey.github.io/2017/03/14/How-to-edit-scripts-with-your-favorite-editor/

yfdyh000 on 12 Oct 2017

👍6

@yfdyh000 Thanks, that is incredibly helpful! I didn't even think about running python -m http.server to serve my userscript folder on localhost while I'm editing them. Now it's only two clicks and ~3 sec delay between them to reload a script from disk.

The only step missing to make it truly convenient is the Violentmonkey feature mentioned in the article: a checkbox on the GM "Install script" page to monitor the file instead of closing it after installing. Even simply keeping that installation page open instead of closing it after hitting Install would be awesome.