[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sc-devel] Modifying Main:run to run run.rtf in analogy to startup.rtf
but why forgo the current file based approach?
I find the idea of startup.rtf as genial as it is simple.
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.
If people need to have platform-specific startup and run mechanisms, lets keep the current platform localization scheme. Are there problems with it?
In any case I would propose that all schemes include the usage of 2 files in the ~/scwork folder:
On Dec 26, 2007 8:43 PM, felix <felix@xxxxxxxxxxxxxxxxxxx
sure, I'd love to take a look whenever you finish.
to my mind it sounds much simpler to have a single class that handles all of the default application behaviors, and then let people subclass it to customize. then you can see in one file how you have your app set up.
it sounds harder to figure out where a given "feature" was inserted into StartUp and then how to disable it. are you supposed to go delete it out of the StartUp stack?
anyway, I'll check it out when you get around to posting it. I'm sure its an improvement.
On Dec 26, 2007 3:02 PM, Scott Wilson <i@xxxxxxxxxxxxxx
Julian and I have been working on making CmdPeriod more flexible, as well as adding CmdPeriod/StartUp like objects for other events (shutdown, server boot/quit). (This was discussed in the Hague.) In the current draft (which we can forward to the list once a couple of things are sorted) the default stop stuff (clocks and servers-free) are moved into CmdPeriod, and can be disabled so that you can have your own behaviour.
Something similar could be done with StartUp, so you could disable or replace the platform specific stuff.
Sc-devel mailing list