[jitter] Breakin up Engine and GUI

I'll throw in my bit of experience with this sort of thing....

I have used two instances of Max to divvy up my video processing and  
it worked out quite well.  I was using xray.jit.water in one instance,  
which was quite processor-intensive, so I split that part of the patch  
off and ran it in one instance.  With jit.net.send/recv, I was able to  
send a 1 char 720 480 matrix between instances at a solid 30fps (on a  
MBP 2.33GHz, 3GB RAM, Radeon X1600).   I did experiment with  
jit.broadcast and jit.qt.broadcast but I don't recall the results.  :-X

Note: on Mac it's easy to just duplicate Max/MSP and have two editable  
(non-runtime) instances going at once -- not sure how it works on XP.

 From what I gather, OSC is definitely the way to go for sending  
control data (I haven't done it yet).

hth,
dan