Blender Git Commits

Claude: Add previews handling.

Using PIL right now to load thumbnails, so won't work with 'stock' blender builds :/

Merge branch 'master' into asset-engine

Claude: add basic loading of selected images...

Note that you can link several images in a single run.

Also, images are using current 'link file as datablock' hack, awaiting for propper ID override to get really sane behavior here...

Merge branch 'master' into asset-engine

Merge branch 'master' into asset-engine

Merge branch 'master' into asset-engine

Claude: Fix erroneous uuid generation.

This uuid generation is just temp placeholder anyway, we want something based on actual uuid of Cloud items,
but at least let's avoid generating several time the same ID in current listing!

Merge branch 'master' into asset-engine

Claude: WIP, listing is kind of working, mush to be fixed still though, and of course no import yet.

Merge branch 'master' into asset-engine

Claude: More WIP work - repo listing starts to work - partially! :P

Merge branch 'master' into asset-engine

Claude: more WIP work towards listing content on Cloud repository.

Allow asset engines to change current dir also from list_dir function.

Rational is, in case of online repo, it may not be practical to decide
whether a path is valid or not from check_dir() callback, which should return
immediately.

So instead, check_dir() can only check whether path **looks** good, and
delegate actual path validation to list_dir (and maybe other similar functions).

That?s what is being tested with Claude engine at least.

Merge branch 'master' into asset-engine

Merge branch 'master' into asset-engine

Forgot to 'backport' those fixes in last commit :/

Merge branch 'master' into asset-engine

Claude: Fix asyncio handling!

Turns out using worker thread to run asyncio loop is not working with pillar, this code is totally
not blender-independent and hence cannot safely work in another thread.

So instead using same technique as in AmberAIO - 'stepping' of asyncio loop, instead of blindly
run_forever() and hoping loop will stop some day...

Note that we may rather call e.g. loop.run_later(1e-5, loop.stop), to actually give a bit more
time to the loop... Time will say what's best option here.

Claude: Fix pillar api url to new value.