design the edit operations in a systematic manner

[raevol]

"Edit operations" are the high-level primitives which can be issued by the GUI or a script to work with the objects in the Session/EDLs.
They will be recieved by the Proc-Dispatcher (not to be confused with the dispatcher in the backend), and each of those operations will be UNDOable. As such they are user visible and thus each of those Edit operations needs to embody a concept which is understandable for the user and makes sense as "something the user does"

While there are certainly quite some Edit operations which map
naturally to some specific, internal operations within the proc layer, like calling a factory for creating a new object of a given kind, generally it would be better to design those operations as a whole in a systematic manner, rather then just add them technology driven as we go.

Thus, this task is the call for a designer willing to have a dedicated look into this issue. It is not so much about coding, but you need a thorough understanding of coding and if the PROC layer design.

[ichthyo]

reorganising core component tickets

[ichthyo]

this is indeed and still very important, but -- realistically speaking, no one can care for it right now.
Pushing to future