Ticket #311 (accepted planned)

Opened 2 years ago

Last modified 3 months ago

draft how the Timeline-Sequence Binding works

Reported by: ichthyo Owned by: ichthyo
Priority: lesser Milestone: 0integration
Component: lumieraProc Keywords: design data
Cc: Blocked By: #310, #312, #646, #651, #657, #716
Blocking: #151, #442, #550, #578, #580, #632, #806

Description (last modified by ichthyo) (diff)

  • direction of this association
  • can it be switched, changed and disabled?
  • how to store ouput pipe mapping data
  • how to store the link to the global pipes

Change History

comment:1 Changed 2 years ago by ichthyo

  • Blocked By 312 added

comment:2 Changed 2 years ago by ichthyo

...and, last but not least: how to handle the interference with the Scope concept? More specifically: how is the correct way of entering top Placement of the Sequence (i.e. the root track) into the PlacementIndex? It is clear that it needs to be entered, but doing so would require to specify a scope. But there is no scope, speaking strictly logically. Or, maybe using the root scope in this case?

comment:3 Changed 2 years ago by ichthyo

  • Blocking 550 added

comment:4 Changed 23 months ago by ichthyo

  • Blocking 578 added

comment:5 Changed 23 months ago by ichthyo

  • Blocking 580 added

comment:6 Changed 22 months ago by ichthyo

  • Status changed from new to accepted
  • Description modified (diff)
  • Milestone changed from 1alpha to 0integration

a bit sidelined, but basically caring for that now

comment:7 Changed 20 months ago by ichthyo

  • Priority changed from normal to grave

...seems to become kind of a blocker. But still the difficult part is #312 how to organise the output designators

comment:8 Changed 20 months ago by ichthyo

  • Blocking 632 added

comment:9 Changed 19 months ago by ichthyo

  • Blocked By 651 added

comment:10 Changed 16 months ago by ichthyo

  • Blocking 302 removed

(In #302) The planning of timeline-sequence binding (#311) isn't finished yet, but I think this won't cause any significant changes to the design of the placement scopes. I consider the latter stable now, its even mostly implemented and passes the basic tests.

comment:11 Changed 16 months ago by ichthyo

  • Priority changed from grave to urgent
  • Blocking 442 added

This part of the design is still not completely settled, which is likely to become a blocker.

Note: the implementation can be safely delayed until Alpha or later

comment:12 Changed 15 months ago by ichthyo

  • Blocked By 716 added

comment:13 Changed 15 months ago by ichthyo

  • Blocking
  • Blocked By 646, 657 added

This evolved into a huge blocker meanwhile. really need a concentrated effort to work this out. The problem is that any decision here requires a roughly complete understanding of the general wiring and output handling, thus I'm forced to target this topic right now

comment:14 Changed 15 months ago by ichthyo

  • Blocked By

The main design work is done now. Answers:

  • Timeline is an facade asset, pointing to a Binding (MObject)
  • the Binding links to a Sequence
  • Sequence is an facade asset too, pointing to a root track (MObject)
  • A timeline can't existi without this link to a Sequence
  • but that link may be switched
  • the Binding-MObject is the central implementation location

comment:15 Changed 9 months ago by ichthyo

  • Priority changed from urgent to lesser

basically clear now, waiting on the (planned) renaming and refactoring actions within the session.

comment:16 Changed 9 months ago by ichthyo

  • Blocking 806 added

comment:17 Changed 3 months ago by ichthyo

  • Type changed from todo to planned

future -- currently concentrating on the engine

Note: See TracTickets for help on using tickets.