Blender Git Commits

Merge branch 'master' into asset-metadata

Merge branch 'master' into asset-metadata

Add File Browser Link/Append option to show only assets

Support "Author" metadata field

Merge branch 'master' into asset-metadata

Add access to asset-data from ID

Remove asset data-block again, back to ID.asset_data design

So rather than having an asset data-block to reference data-blocks, let
the data-blocks reference asset-data.

After talking to Brecht, it seems that this approach is just fine. I previously
added the data-block type because I saw some benefits (faster & simpler asset
metadata reading, non-data-block assets, better file-browser integration,
simple remapping of referenced data-blocks), but there are ways to do the same
without the data-block. It's a bit more complicated that way, but still very
doable.

Add custom tag support to assets

Tags are basically a list of strings. We could optimize these in future if
needed. We could also easily add colors or icons for individual tags (e.g. like
on developer.blender.org).

Note that there's no UI for this yet. Functionality is available via Python
though.

Support arbitrary descriptions for assets

Simply have a dynamic string in the asset data-block. That can be set and
updated at any point.

Support preview thumbnails for new asset data-blocks in file browser

Assets have to own a copy of the referenced data-block's preview for this to
work. We *could* do without that, but it complicates partial reading of
data-blocks for the file browser (which may be addressed with further work
though).

Use new Asset data-block type for "Create Asset" operator

AssetData is unused now. Just keeping it in case it's useful later (to avoid
having to do the monkey work to add it again).

Merge branch 'master' into asset-metadata

Add new asset data-block type

With this we can read asset data in .blends more efficiently, e.g. for browsing
files or assets (where we avoid reading more than we have to). But there are
other things besides performance that I'd like to play with.
Basically I see the asset information a bit similar to library information,
which we also deal with as a separate data-block.

The "Create Asset" operator doesn't actually create these data-blocks yet.
That'll be added in a followup commit.

Of course this is not set in stone, but I think a reasonable design to work
with for now.

Merge branch 'master' into asset-metadata

Fix crash when changing file after "Create Asset"

Support object preview thumbnails, generated on asset creation

To generate the preview, a temporary main data-base is created (think of this
as a virtual .blend within the current .blend) with a new scene and the object
to generate the preview for. It's rendered with a camera from the front, using
the "Camera Fit Frame to Selected" logic.
This should be a simple solution requiring no further setup that should work in
most cases. If needed we can have a way to set up the preview differently.

To see it in action:
* In the Outliner context menu for an object run ID Data > Create Asset
* Save the file
* Open a different file (so you can browse into the former)
* Use link/append to navigate into the saved file with the assets. You should
see the preview in thumbnail mode.

Show info report on successful asset creation

Also set fake-user for new asset data-block so it's not purged when closing the
file.

Rename "Make Asset" to "Create Asset"

The term "make" in this context refers to modifying an item to obtain a certain
property. Creating an asset however means saving a copy of a data-block as
asset. So "create" is better suited here.

Generate preview when making a data-block an asset

Initial "Make Asset" operator

Accessible via the Outliner context menu (ID Data submenu).

The operator currently copies the data-block and creates empty asset data for
it. This will later contain all the meta-data to "give the data-block meaning".

Of course there are many TODOs and questions remaining. This is the first step
so I can work more on meta-data support.
I created some files and that I think make sense.