New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebExt: External editor support (read/write extension directory) #2513
Comments
Turns out |
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. |
@yfdyh000 Thanks, that is incredibly helpful! I didn't even think about running 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. |
to be able to use external editor. Resolves greasemonkey#2513 .
to be able to use external editor. Resolves greasemonkey#2513 , resolves greasemonkey#3048 , resolves greasemonkey#2666 , resolves greasemonkey#2710 , resolves greasemonkey#2738 , resolves greasemonkey#2737 , resolves greasemonkey#2736 , resolves greasemonkey#2735 , resolves greasemonkey#3098 , and resolves part of greasemonkey#2669 and greasemonkey#3115 .
to be able to use external editor. Resolves greasemonkey#2513 , resolves greasemonkey#3048 , resolves greasemonkey#2666 , resolves greasemonkey#2710 , resolves greasemonkey#2738 , resolves greasemonkey#2737 , resolves greasemonkey#2736 , resolves greasemonkey#2735 , resolves greasemonkey#3098 , and resolves part of greasemonkey#2669 and greasemonkey#3115 .
to be able to use external editor. Resolves greasemonkey#2513 , resolves greasemonkey#2932 , resolves greasemonkey#3048 .
to be able to use external editor. Resolves greasemonkey#2513 , resolves greasemonkey#2932 , resolves greasemonkey#3048 .
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.
The text was updated successfully, but these errors were encountered: