I think the "delegate" class is a good idea.
You talked about the server windows. Before it was very easy to comment those
out in the Main class. Now you have to look for the class (what's it's name...???) from
within Main, then Platform, then giving up and going into Finder to browse SC's class
system to stumble upon a class called OSXPlatform (on my system). It's not as straight
forward as it used to be.
Would your "delegate" class simplify this process?
On 27 Dec 2007, at 11:16, felix wrote:
Certainly, the default ApplicationBehavior (or whatever its called, this delegate class that I was discussing) would do exactly what is currently done: load the start up file(s), make server windows etc.
I could subclass that and override to customize the startup.
so it would not forgo it, just enhance it.
I use Main-run to open a menu
the idea behind a delegate is that all of the application behaviors are in a single class and you can clearly see what the original behavior is and override the methods you want to.
On Dec 27, 2007 10:05 AM, Iannis Zannos <zannos@xxxxxxxxx
The point is to avoid having to change class definition code for customizing ones startup and run. I believe there should be in SuperCollider always a scheme for customizing those basic things independently of class code.
For me I prefer to keep everything in class code.
If we have a single delegate class then we can discuss these things in terms of what is best for a simple and clear application behavior for beginners.
because the rest of us can easily customize.
and I agree, the file is simpler to explain. telling someone to subclass the ApplicationBehavior is a bit more involved.
Sc-devel mailing list