Getting Started with Quorum

Install then create!.

Installing Quorum Studio

Quorum can be used online and offline as we see fit. For learning, using Quorum in the browser is often good enough, whereas for larger or more intense projects (e.g., physics, user interface design), we need to write our code using the desktop application Quorum Studio. On this page, we walk through obtaining the offline version of Quorum inside of Quorum Studio, our Integrated Development Environment (IDE). To do this, we first go to the download page, which contains links and instructions.

Creating a Quorum project

Once we have installed Quorum, we can create a project in Quorum Studio. There are many kinds of templates we can use for Quorum projects and they are categorized as follows:


These projects are templates and can be adjusted by us after being created however we see fit. In other words, just because we started a Lego robots project does not mean we cannot use that project for other types of code. To make any new project in the IDE, first we load Quorum Studio, which looks approximately like this:

This is an image of the default Quorum Studio environment start screen.

Next, we either press COMMAND + N on Mac, CTRL + N on Windows, open the File Menu -> New Project item or press the first button on the toolbar to open the New Project window, which looks like this:

This image shows Quorum selected in the left pane and the four project types, in addition to a description field, a name field, and an ok button.

On the left hand side of this window is a tree that categorizes project types and lets us create them. For our purposes, we are going to open Graphics and select “Skybox.” This is an advanced template, but we are choosing it to highlight the types of applications that can be created. As an alternative for those that want audio applications, Other -> Sine Waves or User Interface would be good alternatives.

Running or Debugging a Quorum program

Once we have created a new project, we can use the tree of the project to navigate to a source file and open it. In the case of the skybox template, there are two folders, Skybox, and SourceCode. Our source files, for all projects, are always in the folder named SourceCode, even if we have other media files in the project. Using the normal navigation keys with the keyboard, left, right, up, or down, we can either navigate the tree with the keyboard or use the mouse to open the folder and select (or double click) Main.quorum. Once on the source code window, we can go back to the tree with COMMAND (or CTRL on Windows) + 1 key, then back to the editor with the same keys + 2.

To run a program, we can either press the green button on the top bar of the program, which looks like a play button on a remote control, or we can navigate to the Run menu and select Run Project. The standard hotkey is COMMAND + R on Mac and CTRL + R on Windows. The following shows an image of the run and debug buttons:

This is an image of Quorum Studio with a project open. On the top, the run and debug buttons are present. All of these buttons are available with keyboard shortcuts like COMMAND or CTRL + R for running and + D for debugging.

To debug a program, the steps are similar. Normally, the purpose of debugging is to temporarily halt a program so that we can investigate it at a particular point in time. To do this, we have to set a breakpoint, which means set a point in our program where Quorum Studio knows to stop. This is accomplished by either clicking the vertical line where the line numbers are (called the line gutter), or by going to the line and using the hotkey (COMMAND + K on Mac or CTRL + K on Windows). The following is an image of a breakpoint that has been set:

This is an image of Quorum Studio with a breakpoint set.

The following is an example of a breakpoint that has been hit:

This is an image of Quorum Studio with a breakpoint that has been hit in execution.

Debugging Controls

Debugging and Running are very similar, except that with debugging we stop a program while it is running in order to inspect it for errors. We highly recommend using the debugger and memorizing the hotkeys, as they can be helpful when quickly investigating our code. The available controls are listed below: