Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maya Instance Browser #45

Open
mottosso opened this issue Aug 22, 2015 · 5 comments
Open

Maya Instance Browser #45

mottosso opened this issue Aug 22, 2015 · 5 comments

Comments

@mottosso
Copy link
Member

We'll need a way to update instances in Maya without fuzz.

It should handle:

  • Listing instances in the current scene
  • Visualising the current version from which an instance was made
  • Listing available versions of an asset per instance
  • Switching between versions

Visually it needn't be much more complicated than..

Source asset | Instance | Version
 _________________________________
|_________________________________|
|/ben////////| ben01    | v001    |
| chair      |/ben02////| v002    |
| table      |          | v003    |
| sofa       |          | v004    |
| gunA       |          | v005    |
| hand       |          | v006    |
|            |          | v007    |
|            |          | v008    |
|            |          | v009    |
|            |          | v010    |
|            |          |/v011////|
|            |          | v012    |
|____________|__________|_________|
|                         Update  |
|_________________________________|
@BigRoy
Copy link
Member

BigRoy commented Aug 22, 2015

I put together a quick mockup in PySide, see here:

reference_manager

Currently it allows you to easily switch any of the currently loaded items to another version and provides the information about the files. (In design, not in actual functionality)

Missing in the mockup is the update all button (which could also be under a right mouse menu), but I assume update all might be done frequently so having it at the bottom could be a good addition.

What do you think?

@mottosso
Copy link
Member Author

Looks great,but what do you think about not including the path? I'm thinking it's not relevant to the task and better suited for a tool-tip or right-click menu, such as a "Open in Explorer" item, if it needs to be there at all (probably not).

@BigRoy
Copy link
Member

BigRoy commented Aug 23, 2015

...what do you think about not including the path? I'm thinking it's not relevant to the task and better suited for a tool-tip or right-click menu, such as a "Open in Explorer" item, if it needs to be there at all (probably not).

Yes, might be too much info as it stands now.


Actually I've been looking up some references just now. (Also made some notes over it). This is from the Shotgun/Psyop pipeline video.

psyop_asset_manager

I think this looks really good.

@mottosso
Copy link
Member Author

Yes that looks great, but let's focus on what is absolutely essential right now, which I think is just updating existing instances to their later versions. The UI you've got is a great Beta 0.1, then we could focus on the asset browser, which is more important I think.

@BigRoy
Copy link
Member

BigRoy commented Aug 23, 2015

Here's the code for the draft I had so far:
BigRoy@8a14dd7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants