-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add manager GUI #30
Comments
Manager is currently located in dccpipe.pipe.tools: Steps to accomplish:1However, since this would be a standalone application--not a plugin built-on to an existing application like MayaTools, HouTools, etc...--I think it would be a good idea to pull this out into just dccpipe.pipe, into a new module for standalone apps. Call it applications. 2Next, we should redesign the structure of Manager so the logic is in a controller module, and the gui is isolated as much as possible. Right now, there are many GUI classes inside main.py, and I don't think there are any controller files at all. 3Then, we need to actually hook up manager to use actual data from the pipeline, not dummy data. 4Finally, add in useful tools like search, create, delete, move, etc. |
Also another useful tool would be rename |
This is going to be a lot bigger of a project than I anticipated. The application isn't as well set up currently as I hoped it would be. |
Some good functions to add would be safe deletion of publishes and clearing of the rib_archive directory for a selected asset. A bulk method to clear all rib_archives would also be reallly nice. It should only be run when no one is submitting a shot to the farm and while no shots are being rendered on the farm. Maybe a select from list dialog to exclude selected shots from being cleared would be good. |
No description provided.
The text was updated successfully, but these errors were encountered: