separation functions & editors… even in span

[reno-]

The separation of editors and function-processing has always been an important requirement for tapemovie. But if we were be able to use noedit & nobuild mode, they cannot for ALL the functions.

I guess we must be attentive in span for this kind of details, and be able to run a span edit on a computer, controlling span patch on another computer.

So now we have at least two editors embed in span.maxpat patch :

• events edit functions
• open/new/update project functions

One more benefit we will have with a separation of the process will be to don't use an editor for the events for the time the project is running.
The lighter it could be, more process we will be able to add without having a too large loading time.

So what I suggest is to :

1. put the events edit functions in the span.events GUI.
2. put the open/close/update dialog in the span.project GUI

What do you think about? Is there any side effect I didn't think about?

[reno-]

With json string format, I guess we will even be able to edit events remotely, for version 0.2 !!

[tmays]

Very strange. I posted a reply to this, and it disappeared! Maybe I didn't hit save or something...

Anyway, the point of what I said was that IMHO there's an important difference between low-level editor functions and a Graphical User Interface, and that it's ok and even preferable for us to have low-level editor functions in span, while NOT having the GUI. This allows us to 1) make solid, bug-free low-level functions that allow multiple editors and instances of editors to exist without duplicating the basic functions, 2) manipulate those functions over the network. We can talk more about this, but I think that we are on the right track. I think it makes sense to have these low-level editor functions within span so that span can have the stand-alone quality that we have been trying to maintain - with minimal functionality.

As we said, span needs to contain:
project management
event management
database functions
osc in/out
basic osc mapping

low-level non-graphic editor functions need to be in span so that these features can be achieved with just the abs.

Don't you agree?