Supercollider gui install#
Supercollider gui full#
Supercollider gui code#

Managing your code with git is optional, but you should consider using it early on. Now you can (un)install your own packages from your local folder. Or create a folder where you do your development work and add that to the additional folders: Quarks.addFolder('~/supercollider/quarks')

Supercollider gui install#

Install any source code folder as a Quark: Quarks.install('~/path/to/my-quark') Packages are a natural way to store your work.

Supercollider gui full#

`~/supercollider/quarks/my-thing` was not a git repo so the best it can do is to specify the path.Įven if a quark was installed by name using the directory, the full repository URL will be saved to ensure that the reference is unvarying (the directory.txt could be edited and the URL changed, and that might then point to different source code).Īny packages not under git source control are specified by path, abbreviated to the most logical path relative to the quark file, the home directory or by absolute path. In both cases this results in an exact reference. The file format looks like this: that in this case `quarkname` was checked out to the tag 4.1.4, and `ddwCommon` was not on a tag so the refspec is the SHA hash. If you have installed local paths that are not under git source control (your own work or things you have downloaded) then the paths will be saved without any version or refspec. In git terminology this is known as a refspec. The save format specifies the revisions using git tags with a fall back to the full sha hash that specifies the revision. If you have uncommitted changes in one of the quarks then it will warn you that its dirty. This saves both what quarks you have and what git revision they are on. Quarks.load('~/supercollider/quarks.txt') Quarks.save('~/supercollider/quarks.txt')

This is very useful for projects because you can pin the exact releases of each Quark that your project depends on and you should be able to reload them exactly even years in the future. This is similar to what the LanguageConfig does but this also downloads the Quarks if needed and installs all dependencies. To make project work simpler you can save and later reload your currently installed Quarks to and from a quarks.txt file. You can also manually edit sclang_config.yaml Saving and Loading sets of Quarks If you are using the SC IDE then open Preferences > Interpreter and remove the paths from the Include Paths. The Quarks interface can only work if SuperCollider is compiled and running, so if something goes wrong then you have to fix it manually. SuperCollider does not allow duplicate class definitions and will fail to compile if you've accidentally installed conflicting packages. You can also see or edit these settings in the file sclang_config.yaml Fixing Conflicts You can view and edit the current include paths via Preferences > Interpreter > Include Paths. When you install one it is cloned using git into: Quarks.folder Īnd this path is added to the LanguageConfig includePaths so that the classes are in SuperCollider's class path when you recompile the library. If you've made a bit of a mess: // remove everything Recompile the class libraryĪfter installing or uninstalling you need to Language > Recompile Class Library addFolder does not add individual quark directories. Then, use Quarks: *addFolder to add the primary directory. If you wish to be able to uninstall local quarks, but still see them in the GUI, it is highly recommended to collect your local quark directories under a single primary directory. Now each quark inside that folder will appear on the GUI for you to un/install. You can also add a folder where you keep your development quarks (your own and things you have forked): Quarks.addFolder('~/supercollider/quarks') Quarks.install('~/Downloads/something-i-found') install something that you downloaded and want to try out

Quarks.install('~/supercollider/quarks/my-thing') Quarks.uninstall('') from a local folderĪnd you can install any local folder: // add your own classes Quarks.uninstall('MathLib') by git URL Quarks.install('') You can (un)install a Quark by name: Quarks.install('MathLib') Quarks.addFolder('~/supercollider/quarks') by name These will also be shown on the GUI as options for installing. You can also add additional folders where you keep your personally developed quarks or those you have forked or downloaded. This offers many community contributed packages most of which are hosted on github. You can install Quarks using the interface: Quarks.gui The Quarks class manages downloading these packages and installing or uninstalling them. Quarks are packages of SuperCollider code containing classes, extension methods, documentation and server UGen plugins.