Concept¶
what should the pipeLion do:¶
- handle the whole pipeline (work and dataflow) in small and medium size productions
- make it easy for the artist to switch projects
- make it easy for the producers to keep the overview about artists, schedule, milestones etc
- make it easy to setup the pipeline for a project
- take care of versioning and asset-management
what shoudn’t the pipeLion do:¶
- replacing a pipeline-td
- restrict the user to use certain tools or packages
- removing files or versions
node-based approach:¶
advantages:¶
- each node represents a task
- each connection between nodes represents how the asset will be processed
- shots, sequences and the project itself are group-tasks
- fast to setup
- easy to understand dependencies and constraints
- easy to debug
disadvantages:¶
- the node-flows can get huge
- to get more detailed information nodes have to be accessed (more clicks to get info)
consequences:¶
- impossible to get rid of table-views or schedules
- good data-filtering and grouping
