Several desirable features:
Basic box and wire patch editor for core SAOL opcodes.
Ability for a patch to be wrapped up in and become a box.
Ability for 3rd parties to write "boxes" that encapsulate their own code
generators. That way, if someone does write a code generator for a physical
model of a gong with a mallet that shrinks and grows, it will plug into your
editor and work there.
The key to this is OO design: abstract box interface that draws itself in
bounds, accepts wires, and spits out SAOL code to a code collector, with
hardwired implemented boxes for core opcodes, and runtime-loaded boxes for
3rd party code generators, all providing names and descriptions and icons
for a palette of boxes/patches...
The editor should of course be able to run SAOL in order to test patches.
The SAOL interface also should be abstract so that various implementations
of SAOL will work with the editor. For now just shelling out to run sfront,
the c compiler, and the produced program would work. I have an ActiveX
control with a Java interface that encapsulates this process of compiling
and running SAOL and will be happy to give it to you (it is under GPL).
Check out Reaktor and Max for the best current examples of this paradigm.
-----Original Message-----
From: Bert Schiettecatte [mailto:bschiett@vub.ac.be]
Sent: Tuesday, October 26, 1999 12:30 PM
To: saol-dev@media.mit.edu
Subject: Editor for SAOL
Hi,
I'm thinking about implementing a SAOL environment (generates SAOL code
based on graphical connections between predefined instruments etc) in
Java, but I'd like to hear about as much feature requests/requirements as
possible, so that I know more or less which features are required.
thanks,
bert
__________________________________________________
Bert Schiettecatte bschiett@vub.ac.be
1e lic INF Vrije Universiteit Brussel
This archive was generated by hypermail 2b29 : Wed May 10 2000 - 12:15:41 EDT