Ticket #155 (new planned)
clean up usage of Track-IDs
| Reported by: | ichthyo | Owned by: | ichthyo |
|---|---|---|---|
| Priority: | lesser | Milestone: | 0integration |
| Component: | lumieraProc | Keywords: | QA cleanup |
| Cc: | Blocked By: | #563, #581 | |
| Blocking: | #150, #514, #578, #637, #692 |
Description
While doing the initial draft, the whole concept of Assets wasn't clear. Meanwhile, we've gotten track Assets, which make first class candidates for getting a track designator.
Thus, we should phase out the direct (language) references to a session::Track in favour of an asset::ID<Track> (which is implemented as a simple hash value). Work on this ticket should likely be delayed until the MObject hierarchy is more stable
Change History
comment:7 Changed 20 months ago by ichthyo
meanwhile, even the track assets themselves are deprecated. Rather, I'm leaning towards an asset-like bare ID, with some automatic registration mechanism. Anyhow, the goal of this ticket remains valid, namely to get a uniform usage of track-IDs
comment:11 Changed 15 months ago by ichthyo
- Blocked By 715 removed
(In #715) intending to do that right away, together with renaming the internal track representation
