Extensions: First time dialogs and setups #120665
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#120665
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
With the introduction of the extension system, Blender needs a clear way for users to grant access to online repositories. Even Blender's own extensions.blender.org should be explicitly authorized (enabled) before Blender starts accessing it.
When will Blender access the remote repositories:
Proposed changes:
In the future the Extensions system will likely also be used for assets. Making the definition of extensions close to: "External resources to extend Blender functionality".
The remaining of this task specify how we should handle all the scenarios when users first interact with extensions.
Preferences
A welcome panel will greet users when they open Preferences → Extensions. The panel can be collapsed. But to remove it permanently users need to either:
Enable
: This will enable the extensions.blender.org repository.Dismiss
: This will close the panel permanently (saved with preferences.blend).If the extensions.blender.org repository was enabled via the drag to install popup dialog, this is dismissed as well.
Text
Drag in a extensions.blender.org URL extension
If an extension from extensions.blender.org is dragged in while the repository is disabled we get a special dialog.
Text
Drag in a extension URL from a repository not added yet
Extensions download URLs have an optional parameter to specify which repository they come from.
https://extensions.blender.org/add-ons/mypackage/1.0.0/download/?repository=/
https://aws1.com/mypackage.zip?repository=http://mysite.com/blender.json
If this extension is not in any of the available repositories (even after the check for updates that happens automatically) the user first has to setup the repository:
Text
Drag in a extension URL from a unknown repository
If this extension is not in any of the available repositories and no repository information is available:
Text
Install an Extension
In all these cases, after you click on "Enable..." or "Add Repository...", the next dialog shown is the "regular" Install Extension dialog. Similar to a Wizard (first-time setup).
It would be nice if both set of dialogs were shown centralized (like "Saving changes before closing"), instead of where the cursor is.
Design done together with Pablo Vazquez.
What is confusing to me is this concept of checking for updates, which includes both refreshing the list of extensions, and doing that refresh on startup and notifying the user about updates.
I would rather expect that as soon as you have enabled a repository, it is fine to refresh the list of extensions when going to the extensions preferences. That's like browsing a web page, you don't expect it to be out of date. What I think you want permission for is (a) to enable/add the repository, and (b) for Blender to automatically access the internet in the background.
So from that point of view, I would expect the welcome message to be asking to enable or add the extensions.blender.org repository, rather than having it already enabled and only a refresh away from being used.
For the dialog when installing an extension, maybe it would be better to have a single dialog instead of two, with a Add Repository checkbox? I can imagine some confusion with this intermediate step, and it not being obvious that it will be possible to install the extension in the next dialog.
Task updated with new design iteration. We may still iterate over the text after (or before?) this is implemented.