Ticket #516 (closed todo: done)
(re)define Track
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | normal | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | design session cleanup |
| Cc: | Blocked By: | #371, #430, #563, #581 | |
| Blocking: | #500, #514, #564, #646, #657, #692 |
Description
in the emerging session API, track becomes more of an view. Decide on the relation to the track asset and draft the immediate operations on the track-MObject
Change History
comment:7 Changed 16 months ago by ichthyo
assert that Track is just a container-like mobject, backed by a suitable track-id
comment:9 Changed 15 months ago by ichthyo
- Status changed from new to closed
- Resolution set to done
Decision: The we dispose of special track mobjects. The entity is unified with the media bins. The resulting MObject becomes a mere marker object (like an algebraic data type). A name change for this implementation object is being considered (I'd like to call these objects Fork).
Similarily, on the asset side we dispose of specialised track-assets, only a simple EntryID is retained, which will participate in the general entity registration scheme to be implemented later.
Note: See
TracTickets for help on using
tickets.
