Fix #364: Make cbloader and cbsceneinventory the new defaults

[BigRoy]

Changes:

• Remove empty builder tool
• Remove old manager and loader, replace with cbloader and cbsceneinventory
• Refactor cbloader -> loader
• Refactor cbsceneinventory -> sceneinventory

---

Reference issue: #364

NOTE
Currently code is untested, only refactored it for now. This way it also allows others to check their dependencies on it plus potentially discuss the naming/refactoring of "sceneinventory" as opposed to the older "manager".

[houndci-bot]

Some files could not be reviewed due to errors:

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'
./avalon/maya/compat.py:25:-267: W605 invalid escape sequence '\M'
./avalon/maya/compat.py:25:-262: W605 invalid escape sequence '\s'
./avalon/maya/compat.py:25:-254: W605 invalid escape sequence '\g'
./avalon/maya/compat.py:25:-238: W605 invalid escape sequence '\h'

[houndci-bot]

Some files could not be reviewed due to errors:

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'
./avalon/maya/compat.py:25:-267: W605 invalid escape sequence '\M'
./avalon/maya/compat.py:25:-262: W605 invalid escape sequence '\s'
./avalon/maya/compat.py:25:-254: W605 invalid escape sequence '\g'
./avalon/maya/compat.py:25:-238: W605 invalid escape sequence '\h'

[mottosso]

Looks good, this is the right way forwards.

[BigRoy]

@mottosso do you happen to know what kind of drugs the Hound sniffed? :) I'm assuming those lines are {file}.py:{line}:{column}? Is it referring to negative columns/characters? Wut?

[houndci-bot]

Some files could not be reviewed due to errors:

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'
./avalon/maya/compat.py:25:-267: W605 invalid escape sequence '\M'
./avalon/maya/compat.py:25:-262: W605 invalid escape sequence '\s'
./avalon/maya/compat.py:25:-254: W605 invalid escape sequence '\g'
./avalon/maya/compat.py:25:-238: W605 invalid escape sequence '\h'

[houndci-bot]

Some files could not be reviewed due to errors:

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'
./avalon/maya/compat.py:25:-267: W605 invalid escape sequence '\M'
./avalon/maya/compat.py:25:-262: W605 invalid escape sequence '\s'
./avalon/maya/compat.py:25:-254: W605 invalid escape sequence '\g'
./avalon/maya/compat.py:25:-238: W605 invalid escape sequence '\h'

[houndci-bot]

Some files could not be reviewed due to errors:

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'

./avalon/maya/compat.py:25:-276: W605 invalid escape sequence '\p'
./avalon/maya/compat.py:25:-267: W605 invalid escape sequence '\M'
./avalon/maya/compat.py:25:-262: W605 invalid escape sequence '\s'
./avalon/maya/compat.py:25:-254: W605 invalid escape sequence '\g'
./avalon/maya/compat.py:25:-238: W605 invalid escape sequence '\h'

[mottosso]

@mottosso do you happen to know what kind of drugs the Hound sniffed? :)

Haha, no idea. Could it be line-endings, Windows versus Linux? Didn't you have a new file-server, could that have had an effect?

[BigRoy]

Haha, no idea. Could it be line-endings, Windows versus Linux? Didn't you have a new file-server, could that have had an effect?

Everything is saved from a Windows workstations. Plus it's the only file showing the odd behavior and it doesn't even show any other changes than one change on line 97. Additionally, checking symbols in the file doesn't show me anything odd other than just line endings everywhere. It's really finding something magically hidden.

[BigRoy]

It seems it failed on the backslashes in the docstring. Seems like a bug, anyway... changed it with e2f21d3 and it seems to make it pass. :)

[BigRoy]

@davidlatwe @tokejepsen @mkolar - tagging you guys to give this a test run - if you're referencing any of the tools in your own pipeline code note that they might need refactoring with these names changes. As such, if you are using these tools that are NOT public in Avalon API this could introduce a backwards incompatibility and will require you to update code along.

That is also described in this PR's issue #388

Also, AVALON_EARLY_ADOPTERS is effectively redundant with this change. It does not trigger any changes on behavior, but could still be used in the future if we introduce breaking changes in a point release. So note that the key is still mentioned here

---

This merge will likely become part of Avalon 6.0 - see: https://github.com/getavalon/core/projects/3

[davidlatwe]

I have tested on my end and looks working nicely after I changed those module name :)
And I also made a PR in Launcher getavalon/launcher#42 for this to working.

[BigRoy]

And I also made a PR in Launcher getavalon/launcher#42 for this to working.

Thanks, totally forgot that action was native to the launcher currently.

[mkolar]

This does not affect us much. We're actually preparing (and should be done this week @iLLiCiTiT? ) a refactor of the UIs which separates models, delegates and widgets from their tools into universally usable elements for UI building in avalon. As we worked with the tools it became a bit of a mishmash of tools cross-referencing widgets from other tools, so this is an effort to make it cleaner... #upcoming

[BigRoy]

a refactor of the UIs which separates models, delegates and widgets from their tools into universally usable elements for UI building in avalon. As we worked with the tools it became a bit of a mishmash of tools cross-referencing widgets from other tools, so this is an effort to make it cleaner... #upcoming

Perfect! :)