-
-
Notifications
You must be signed in to change notification settings - Fork 631
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
Add-on: Adds an unpackaged Add-on to facilitate the development and testing of Add-ons. #17239
Comments
Thanks for opening this. I have a couple of clarifying questions
If you are doing this from source, and keeping the file in the scratchpad, wouldn't you just need to git checkout the release tag of NVDA you want, without copy/pasting?
Can this be fixed by cloning into the scratchpad dir? If that can't be done now, it would be a useful structure to support
Where would you like to specify this? Can you elaborate more on the UX. My proposal on #6277 was to add something to advanced settings to allow adding additional scratchpad directories |
Yes, I should add cases where I need to interact with applications that have administrator rights.
Unless the repository's root directory holds the Add-on source code, and only the individual Add-on types, this should be unlikely.
For the presence of manifest.ini, I'm not sure. add-on store or add-on store settings panel might be good.
For the scratchpad directory, I agree with the |
Some thoughts:
|
When we want to test the Add-on on different versions of NVDA, we may need to copy and paste the modified original file frequently.
If you are doing this from source, and keeping the file in the scratchpad, wouldn't you just need to git checkout the release tag of NVDA you want, without copy/pasting?
What I'm getting, is that he develops, using many add-on source files, under a source checkout, but tests in a separate installed copy (or several of them? Somehow?).
In that scenario, the installed copy isn't git-managed, so I don't see how your solution would work there.
Being able to setup additional scratchpad directories, would allow pointing the directory in several NVDA copies, to a single place.
For the reasons @CyrilleB79 pointed out, I don't develop complex stuff in the Scratchpad personally.
Maybe an "Additional add-on paths" option would be better? Allowing the search for externally installed add-ons to be expanded to manually entered directories.
The UX, then, would be a simple path chooser under either Advanced, or the Add-on store panel.
|
Is your feature request related to a problem? Please describe.
Currently we can develop Add-on's on an ad-hoc basis via the scratchpad catalogue, but there are several problems with this.
When we want to test the Add-on on different versions of NVDA, we may need to copy and paste the modified original file frequently.
Especially if you need to interact with applications that have administrator privileges.
There is also the inconvenience when we want to develop and test the source code of an Add-on cloned from GitHub.
Describe the solution you'd like
For cases where a complete Add-on structure exists, you can manually specify the unpacked Add-on directory from which to load the Add-on, and perhaps also the corresponding manifest.ini
When there is no manifest.ini, this directory behaves like scratchpad.
Describe alternatives you've considered
Manually create hard links without NVDA processing.
Additional context
Follow-up to #6277
The text was updated successfully, but these errors were encountered: