SuperCollider Byte Code Reference
Brian Heim 2018-06-19
Table of Contents
Add a new
:bundle. When this target is set
false. We want to take advantage of the fact that the
require for libs found in
:nodejs-rt false clarifies that
we are not actually going to target the Node.js runtime.
:bundle target always generates an
index.js file, it need only be created once.
The contents of index.js looks like the following:
NOTE: This proposal is dead. A simpler solution was arrived at via the new `:bundle` target.
|// Twister devices are expected to be named in this form:|
|// classvar <endpointDevice="Midi Fighter Twister %", <endpointName="Midi Fighter Twister";|
|// Where "Midi Fighter Twister 1" is TwisterDevice(\default) and "Midi Fighter Twister 2" is TwisterDevice(\secondary)|
|// A twister device. These are singletons - there is only ever one registered per device. It works ala Ndef, Pdef, etc, see Singleton help file.|
|~device = TwisterDevice(\default);|
|// If your MIDI Fighter is named something other than the above, you can register it via:|
|this.registerDevice(\myDevice, "endpoint device", "endpoint name");|
|// And then access it via TwisterDevice(\myDevice)|
NOTE: This gist uses the master branch of ClojureScript. Clone ClojureScript and from the checkout run
./script/uberjar. This will produce
target/cljs.jarwhich you can use to follow this guide.
As client applications become larger it becomes desirable to load only the code actually
required to run a particular logical screen. Previously ClojureScript
:modules compiler option
permitted such code splitting, but this feature only worked under
and users would still have to manage loading these splits.
:modules also required manual