2024 Jul 25, 04:27 PM
(This post was last modified: 2024 Jul 25, 04:31 PM by jonathan.
Edit Reason: augmented
)
The improvement is actually simple (just two lines of code), but I also updated the proto plugin to illustrate how this works and make it easier for plug in authors to get started. See https://github.com/Dan-in-CA/SIP/commit/...eedaac3881. I'm still testing it with my custom plugins, if I find no issue I'll do a pull request. If you see any possible improvements let me know. I'm not sure how it will work with the plugin manager - simply adding the .js file to the manifest should be sufficient to allow installation and enablement, no?
Found another very handy scenario - testing plug ins! I've written one to try to help identify the issue with 318 and I'm now using it to verify my fix before committing. The plugin would be easier to share for user verification than a random source code fix.
Found another very handy scenario - testing plug ins! I've written one to try to help identify the issue with 318 and I'm now using it to verify my fix before committing. The plugin would be easier to share for user verification than a random source code fix.