[chuck-users] code reusability

Michael Heuer heuermh at gmail.com
Fri Jun 11 09:53:31 EDT 2010

Thomas Girod wrote:

> I'm currently working on a chuck project that is progressively
> increasing in size. Some parts of this project are already quite
> generic, and I will probably use them in other projects later (namely,
> an interface to communicate with the novation's monome ripoff).
> So I start to wonder: how can I organize my code for easy reuse ? What
> are the options / good practices to write less monolithic chuck code ?
> Is it possible to write something that could behave as a library ?

LiCK is such a library


The import mechanism is not ideal though, there is an import.ck script
that imports all the other classes with Machine.add calls in the right

$ chuck --loop &
$ chuck + import.ck
$ chuck + myChuckScript.ck


More information about the chuck-users mailing list