Blender Git Commits

Blender Git "asset-engine" branch commits.

Page: 25 / 79

September 6, 2016, 12:12 (GMT)
AmberAIO: Fix asyncio loop handling.

Finally found the right way to do this (at least, I think! :P).
September 6, 2016, 10:27 (GMT)
Merge branch 'master' into asset-engine
September 5, 2016, 13:10 (GMT)
Merge branch 'master' into asset-engine
August 31, 2016, 18:59 (GMT)
Merge branch 'master' into asset-engine
August 31, 2016, 10:51 (GMT)
Claude: add Pillar 'login' to Blender CLoud.

Reusing again mostly code from NlenderCloud add-on, adapted to asset engine system...
August 31, 2016, 08:17 (GMT)
Merge branch 'master' into asset-engine
August 29, 2016, 15:10 (GMT)
First (totally experimental and useless) version of a future 'BlenderCloud' asset engine.

For now it's nothing but an empty shell - but a working proof of concept of how to 'embed'
that ugly asyncio-based stuff into a background working thread for asset engines.

Hopefully more funny stuff to come soon(ish).
August 29, 2016, 15:05 (GMT)
Merge branch 'master' into asset-enginea, and update for new 'checkdir' behavior/expectations.

Conflicts:
source/blender/editors/space_file/filelist.c
August 28, 2016, 14:44 (GMT)
Grr, forgot that fix in previous commit...
August 27, 2016, 12:27 (GMT)
Add experimental 'asyncio-based' version of Amber.

This was done to both test asyncio usage in an 'asset engine' context, and wet my feet with this lib.

All in all, am really not convinced by asyncio in this use-case. async and coroutines are much more
complex to grasp and get working correctly (and efficiently!) than mere threading.
Further more, most python lib callbacks (os.listdir, os.ls_stat, etc.) are not async-ready,
so you have to call them through asyncio's executor (aka threads or processes),
which means using asyncio in this context is only adding overhead.

I think asyncio is only really relevant when you have to handle tens (and much more) concurrent I/O tasks,
otherwise threading (or multi-processing if compute-intensive) are much, much simpler to get working,
and also probably lighter in terms of overload?

Further more, asyncio paradigm is not so easy to adapt to the 'AssetEngine' paradigm, i.e. a
python interface that gets called to start, query and finalize jobs that are supposed to keep running
in-between (think event loop should run in a background thread actually...).
August 26, 2016, 20:03 (GMT)
Merge branch 'master' into asset-engine
August 24, 2016, 16:07 (GMT)
Merge branch 'master' into asset-engine
August 21, 2016, 13:31 (GMT)
Merge branch 'master' into asset-engine
August 14, 2016, 11:14 (GMT)
AssetEngine previews: fix some issues, make Amber generate dummy ones as test/example.

So now, amber generates dummy mosaic-like random previews (with a 100ms delay to mimic
really slow process), everything seems to work just fine. ;)
August 13, 2016, 16:40 (GMT)
Add initial support for previews to AssetEngine.

Code not really tested (it just builds and does not crash :P ).

Will also have to rethink a bit API and data structs imho... AssetUUID is starting to become a bit annoying.
August 13, 2016, 13:18 (GMT)
Merge branch 'master' into asset-engine
August 10, 2016, 20:06 (GMT)
Merge branch 'master' into asset-engine
August 10, 2016, 13:18 (GMT)
Merge branch 'master' into asset-engine
August 7, 2016, 19:19 (GMT)
Merge branch 'master' into asset-engine
August 7, 2016, 08:25 (GMT)
Merge branch 'master' into asset-engine

Conflicts:
source/blender/windowmanager/WM_api.h
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021