AcademySoftwareFoundation / AcademySoftwareFoundation/OpenTimelineIO
Markers should use core.Item
- Dominant language
- C++
- Stars
- 2k
- Forks
- 351
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 1
Description
Hi, I'm having issues with markers, I'm implementing a treeview representation of the otio structure, which is going well but Markers are a pain as they are not parented, which is odd, as they are useless out of context, they always need a parent for calculating their position in the timeline.
So would it make sense for then to work the same way as every other structure in otio, i.e. using core.Item, this also means that their clip/timeline position can be resolved through a function call, instead of guesswork (took ages to work out how they work).
cheers
Contributor guide
Research direction
The issue does not name any files, tests, or entry points. Begin by locating the marker and core.Item implementations, then review how parent context and timeline positions are resolved; done means an agreed design and corresponding behavior for markers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100