On Mon, 22 Jul 2002 17:36:48 -0700 John Lazzaro <[EMAIL PROTECTED]> wrote:
> http://www.ietf.org/html.charters/mmusic-charter.html No, no, none of this is of any use. We already have the best of the best apis for audio and midi, so this isnt the problem. Also to Taybin, what is meant isnt a "session manager" like in gnome, or x (which take care of apps running with their windows placement, etc). I'm talking about a "Project" manager, this hasnt been done before, and it wasnt done before no apis existed which would provide such amount of modularity (like jack/alsa), and because in commercial OSs it's no usual for programs to cooperate so much... so this is basically a new ground. the tasks involve: -Saving current status of the apps, files open, data, etc, into a file you choose, or even be smart enough to tell your apps "save all your stuff here in this dir" and it does a nice tar.gz with your project in case you want to backup it. -Loading current status of the apps, from just telling them filenames, or just giving it the files. -Managing priorities. Certain apps have to be loaded or configured before or after others since some of them will be responsable of restoring all the interconnection stuff And later could be expanded to: -Leting a program know when another has died (crash?) so they can restabilish links -Generic message passing IPC communication api. When talking about the unix way, I have meant "have apps cooperate" Obviously times have evolved and streamed pipes are not the all-wonderful solution, but if you check the current status of the apis such as ALSA or JACK, you will notice that they encourage ways of inter-process-communcation a lot more than the respective apis in windows/mac. So what should this program/api be? "A project manager for IPC enabled apps". That's it. Juan Linietsky
