Ticket #579 (closed todo: done)
design interface for ID and type association
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | asset session design |
| Cc: | Blocked By: | #582 | |
| Blocking: | #551, #578, #593, #594, #595, #596, #598 |
Description
At places, we use assets just to get an ID registered. This unnecessarily complicates creation of entities like tracks, labels and pipes, as the link has to be established explicitly and managed as an asset dependency. Simply using an automatic association would be a much better solution.
As we don't need this association right now -- it suffices to define and implement an interface and integrate suitable extension points into the participating objects (Clip, Track, Label, Sequence and maybe Pipe)
Change History
comment:2 Changed 23 months ago by ichthyo
- Status changed from new to accepted
- Blocking 551 added
For the general reasoning behind this feature, see »TypedID« in the Proc-Layer wiki.
The immediate need prompting to start development on this facility, is how to get sub-selections from the objects in the session -- especially how to deal with retrieving the referred track for the sequence and timeline handling. To serve this purpose, a preliminary implementation is enough, but later, the extension of such an association service will play a crucial role for enabling rules based configuration.
