Files and folders

The file tree is the whole of a project's structure. There is no hidden config and no build file you cannot see.

Creating and renaming#

Right-click in the tree, or use the buttons above it. Creating a file and renaming one use the same dialog, and both ask for a path rather than just a name - so typing utils/format.java creates the folder on the way.

Folders are implied by paths. There is no separate "new folder" step, and an empty folder does not persist, because there is nothing to store.

What a path may look like#

• Letters, digits, dashes, underscores, dots and forward slashes.
• No leading slash, no .., no trailing dot.
• Each segment has to be non-empty - src//main.java is rejected.

The dialog validates as you type and says which rule failed rather than refusing silently.

Which files a project accepts#

Each kind allows a specific set of extensions, and the server is the authority. A Java project takes .java and a set of data and text files; it does not take .py.

Deleting#

Deleting is immediate and there is no recycle bin in the tree. What there is instead is restore points - if you delete something you needed, an earlier working set will still have it.

Pairing a Canvas board#

A project can hold a .rqd file, which links a Canvas board to the project.

Open it and the board opens in Canvas. Delete the .rqd and the board is untouched - you have removed the link, not the diagram.

What counts against your limits#

Source files count toward the byte budget. Binary assets held outside the project's text storage do not. The exact ceilings are in project limits.