Installation
How to get Resonon running on your system?
What You’re Installing
Section titled “What You’re Installing”A Resonon coding environment has three main components:
- Resonon — The core binary of the system. Think of it as the language itself - it includes the interpreter, audio and MIDI engine, and the server for live-coding.
- LSP — Language server protocol (LSP) support for Resonon.
- IDE Support — This can be thought of as the convenience layer for Resonon user-interaction. Currently the standard integration comes in the form of an extension for Visual Studio Code, that connects to the Resonon server and lets you evaluate selected code with
Cmd+Enter. It provides controls for sessions and transport, gives quick access to helpful TUI windows, and more. Internally, the extension uses the Resonon LSP.
In the future there will hopefully be integrations for other editors (think VIM, Emacs, …)
System Requirements
Section titled “System Requirements”- macOS
Installation
Section titled “Installation”Resonon + LSP
Section titled “Resonon + LSP”Download the latest installer (.pkg). The program will guide you through the automatic installation of the Resonon language and LSP.
IDE Support
Section titled “IDE Support”Download the latest extension (.vsix). Then, within Visual Studio Code open the command pallette using Cmd+Shift+p and chose “Install extension from file” in the command-pallette. Select the downloaded file when prompted.
Verify Installation
Section titled “Verify Installation”resonon --versionIf the current version is printed in the terminal, the Resonon language is correctly installed.
In VSCode the extension should show up in the “Extensions” panel. To quickly verify, just open any .non file and see the LSP and RESONON buttons in the footer appear. (The LSP should show a checkmark to the left side.)
If all this checks, you’re all set to start with your first Resonon project!
Installation from Source
Section titled “Installation from Source”If you want to make changes to the core source code of Resonon or have other reasons for not using the official installers, you can always build from source…
Clone the repository, then build and install using make.
If you found yourself here, you probably know your way around this sort of thing. Check the repo for how everything is setup and what packages and tools are required…