Design Catalog system #90066
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#90066
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?
The Catalog system (as described in Asset Browser Workshop Outcomes) needs to be designed, and concrete implementation tasks created.
Catalogs Plan of Attack
Context: 2021-08-20 Asset Browser and 3.0 meeting.
This is a draft planning for tasks regarding the Catalogs. Unknowns will be split out into separate tasks, as not every question has to be answered now.
Design Considerations
C vs C++
The asset catalog system will be C++ with a C interface where necessary.
Since all the catalog information is runtime-only, and storage happens in separate plain-text files, there is no need for DNA.
File Format
A catalog definition file (CDF) is a plain text (UTF-8) file.
#
are ignored.Any other line should contain a catalog definition:
CATALOG_ID
may not contain spaces, as a space is used as separator between it and the path.Multiple definitions
A library could have zero, one, or multiple catalog definition files.
Deduplication
Multiple definitions of a
CATALOG_ID
in one file should be avoided. A warning could be logged (on the terminal, for example) and the first occurrence of the catalog wins.Defining the same catalog in multiple files is fine, as long as they don't confict. In case of conflict, the one defined in the top-most file wins, and the rest is synchronized when it changes (i.e. when a write is triggered).
File Locations
Multiple locations are supported:
${ASSET_LIBRARY_ROOT}/blender-asset-library.cats.txt
blendfile-path-without-extension.cats.txt
blender-asset-library.cats.txt
in each subdirectory? Will become relevant when subdirs are possible with the Asset Browser.Big chunks to do
Decide on line endings
What happens when writing the file? Probably best to keep the line ending that's in use (to stay friendly with versioning systems).
Decide how to keep track of which catalog is defined in which CDF
A catalog can be defined in multiple files, and when updated should be written to all those files.
This can be done by keeping track of a
set<AssetCatalogDefinitionFile *>
in each catalog.Decide UX for editing catalog IDs
The catalog paths are what users will be primarily interacting with. The catalog IDs allow for nifty tricks (like moving assets without updating their blend file), but do make things harder to explain/use. This should be clear in the UI.
Decide UX for creating new Catalogs
Users have to choose a catalog ID, which could default to the slugified last element of the catalog path.
Something (user or Blender) has to choose where to save the catalog info:
Add Catalog ID to
AssetMetaData
A symbolic identifier of which catalog path this asset is stored in.
...
char catalog_id[64];
TBD: the max length. 64 was just chosen arbitrarily.
Add
AssetLibraryCatalogs
classManages catalogs of a single asset library.
TBD: this needs to be split up into smaller TODOs.
Reading, writing, tracking
TBD: internal data structure. What is written above is just one simple idea. It's probably better to have the internal structure stored in a tree, such that a rename of a path just requires moving some elements of the tree around. Might be over-engineered though, as the catalogs are meant to be human-manageable and thus there won't be thousands of them anyway.
Add Tree view of available catalogs
Make things collapsible, selectable, determines which assets are shown in the asset browser.
Allows renaming and moving of catalogs. These operations are the same from the CDF perspective, but are different operations for the user interface.
Add current catalog (ID or path) to asset browser
The asset browser should be able to show assets from a single catalog path + its children.
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @dr.sybren
Added subscriber: @GeorgiaPacific
Added subscriber: @JulianEisel
Changed status from 'Confirmed' to: 'Resolved'
Bulk closing all tasks in the "Done" column. Sybren and I agreed that we don't need to keep this history anymore at this point.
Thanks all :)