Interfacing/miniAudicle - some questions

[diskonext]

Hi all,

I have recently started making electronic sounds again, and have dived into ChucK with a vengeance. You'll probably see me asking some questions here now and then...

I am very much convinced of the usefulness and absolute coolness of ChucK, and am therefore looking at interfacing methods... I guess most of you will agree that any instrument is defined by its interface!

Before I start building my own UI to end all UIs I am exploring other, existing, options.

So, looking at the miniAudicle - and particularly MAUI - as a potential interface of choice, I have some questions...

(all questions relate to Chuck/Dracula and miniAudicle 0.1.3.7 (alpha), running on OSX Leopard)

1) Can I use miniAudicle to connect to an already running VM, without resorting to OSC/Midi? I can't find any reference to this feature on the Wiki, docs or here in the forum.
2) How do you solve loading complex patches in to miniAudicle without going absolutely crazy?

Both questions are related as the current limitation of one public class per ChucK file forces me to have a very specific load order of my files to ensure all dependencies can be satisfied.
(I haven't run into any cyclical dependencies yet, but I am sure that day will come.)

I have also been looking at 'super global' variables so I can attach to various parts of my musical structures from files I load later, but the 'static' keyword in public classes doesn't seem to behave like I would expect from other languages. I think I saw a reference to this in the language specification, although I can't find it right now.
This is especially related to static references, not simple types.

Ok, enough questions for now. Any answers?