Sam
On Dec 24, 2007 12:35 PM, Dan Stowell <
danstowell@xxxxxxxxx> wrote:
JH's prototyping stuff may well help you out here, as he's described.
But for a "big GUI application" I'd definitely recommend becoming
familiar with classes and using them, at least for core components.
For example, for some of my apps I create a class which encapsulates a
buffer as well as the GUI object used to manipulate it, as well as a
couple of other pieces of functionality.
Yes, you have to recompile to update class definitions; but once
you've developed some of your core components, they will change very
very rarely. Classes are SC's primary abstraction method, it's
standard object-oriented programming, and it's very very useful.
Dan
2007/12/24, Vytautas Jancauskas <unaudio@xxxxxxxxx>:
> What options for abstraction do i have in sclang? Obviously classes but
> don't those only get evaluated when sclang get's started? I tried defining a
> class and then sending it to sclang from emacs but that didn't work. Is that
> possible? Functions don't really cut it for this big GUI application i am
> planning, so i was wondering...
>
> sc-users mailing list
> sc-users@xxxxxxxxxxxxxxx
> http://www.create.ucsb.edu/mailman/listinfo/sc-users
>
>
--
http://www.mcld.co.uk
_______________________________________________
sc-users mailing list
sc-users@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-users
--
It suddenly occurred to me that true believers in hard-driving jazz - Albert Ayler, Don Cherry, Cecil Taylor - could never become owners of cleaning shops in malls across from railway stations. Or maybe they could. The just wouldn't be happy.
Haruki Murakami - The Wind-Up Bird Chronicle