The previous reports display can be enabled as a debugging option
since reports flatten errors from different processes which can make
them more difficult to follow.
This was possible to do with add-ons so support it for extensions too.
Otherwise users are forced to navigate to the extension directory
with a file manager and manually remove which is inconvenient.
- Remove unused operator.
- Rename "Repository" to "Local Repository" when installing from disk.
- Make the URL hidden (so the UI can be exposed in the future without
showing the full URL).
This is a bit of a hack, but not sure if we have a better way to
implement this at the moment.
The idea is that an installed extension checkbox should look different
than a not installed one, since you cannot enable/disable the latter.
Ref: !25
Instead of relying on exceptions, temporarily override the stdout
to capture from & warning reports.
This allows multiple reports to be forwarded and not all reports
need to be errors.
While errors caused by updating / installing could be dismissed
any errors that occurred while reading repository data for drawing
were always displayed.
Now errors encountered while drawing are displayed in a single
box with the option to dismiss it.
Any changes to the errors will show the errors again.
- Show inactive disabled checkbox for non-installed extensions.
- Show inactive enabled checkbox for installed non-add-ons extensions.
They cannot be disabled for now, use a place-holder operator.
Part of #117841.
Add "Show Development Utilities" preference which exposes:
- Make Obsolete (useful for testing upgrade).
- Explicit repository lock/unlock.
This avoids showing utilities for developing the extensions by default.
This add-on implements installing/upgrading extensions and remains
experimental (depends on extension repositories).
Move to a addons_contrib add-on so users can test more easily.
See #117286.
