Asset Project: Workflow
This design task aims to develop the basic workflows for asset interaction (see also main design task T46049).
On most basic level, asset interactions are:
- Browsing assets
- Loading assets
- Updating assets
Role of the asset engine in the workflow
We want to give the asset engine itself as much flexibility possible to integrate its data into the UI. Therefore, we only want to develop an UI "skeleton" that the asset engine can use to build up upon.
Integrating the asset management functionality into Blender
We have decided to integrate the Asset Manager with the Blender File Browser. We are doing this for a few reasons:
- It allows us to re-use as much shared code as possible between the asset browser and file browser
- As we make improvements to asset browsing, the file browser will come along for the ride
- People already use the file browser as a kind of asset manager
In Blender 2.8, to better reflect this, we will rename the File Browser to 'Asset Browser'. Using the the Open, Save, & Save As... commands will continue to work seamlessly, and users won't be bothered with any asset-related options where not applicable.
When using the Asset Browser editor type, we will present different views to the user, to switch between File Browser, Current File as well as various asset repositories.
Setting up asset repositories
We've decided to do this in Preferences. Users will only set these up once, and from then on be able to quickly switch between them in the Asset Manager. While you are browsing your assets, you don't want to be bothered with setting up the repositories themselves.
UI pending for this.
This section will give an idea of what our plans are for the user interface.
First, to better support both file browsing and asset management in one editor, we'll need to start by re-designing the file browser somewhat:
See T54642 for details
Description will be updated to represent current state of discussion.