Skip to main content
Version: 0.0.1

RayQuiro 0.0.1

RayQuiro is a scripting language that runs through the rqio CLI. In 0.0.1, the language already covers:

  • .rq source files
  • local and framework imports
  • a built-in interpreter
  • a VM path for supported core scripts
  • native build output through rqio build
  • built-in web, ui, app, engine, fs, env, and process
  • installable frameworks such as telebot

This page is the entry point for the versioned 0.0.1 docs. Use it as a map, then continue into the dedicated pages for syntax, modules, CLI, and frameworks.

What RayQuiro Can Do​

With the current release, one language can be used for:

  • console scripts
  • simple desktop tools
  • installer-like Windows flows
  • static and live local web pages
  • small 3D scenes and mini games
  • automation around files, environment variables, and processes
  • Telegram bot workflows through telebot

Execution Modes​

RayQuiro currently has three practical execution paths.

rqio file.rq​

This is the main way to run scripts. rqio tries to execute the program inside its built-in interpreter first. This is the most convenient path for:

  • core language code
  • system modules
  • rayquiro.web
  • rayquiro.ui
  • rayquiro.app
  • rayquiro.engine

rqio run --vm file.rq​

This path compiles the supported core subset of RayQuiro into RayQuiro bytecode and runs it in the VM.

Use it when you want:

  • a more closed execution path for supported core scripts
  • .rqb packages
  • bundle output

rqio build file.rq​

This creates a Windows .exe. In 0.0.1, the build path still goes through generated C++ and a bundled or system toolchain.

Use it when you need:

  • a standalone native executable
  • a build artifact for release
  • a native output for projects that are outside the current VM subset

Quick Start​

Create a project:

rqio init my-app
cd my-app
rqio

The starter project creates:

  • rqproject.json
  • main.rq
  • .rq_modules/
  • .rq_cache/
  • build/
  • .gitignore

Minimal script:

print("RayQuiro CLI is live");

Run it:

rqio hello.rq

Project Layout​

RayQuiro uses a simple project shape.

rqproject.json​

Project metadata and entry file:

{
  "name": "my-app",
  "version": "0.0.1",
  "entry": "main.rq",
  "build_dir": "build",
  "cache_dir": ".rq_cache"
}

.rq_modules/​

Project-local frameworks installed with:

rqio install telebot --local

.rq_cache/​

Temporary generated files such as generated C++.

build/​

Output artifacts:

  • .exe
  • .html
  • .rqb
  • bundle folders

Language At A Glance​

RayQuiro syntax is intentionally small.

import rayquiro.web as web;

var project = "RayQuiro";

fn greet(name) {
    return "Hello, " + name;
}

print(greet(project));

Control flow is explicit:

var i = 0;
while (i < 3) {
    print(i);
    i = i + 1;
}

For loops are C-style:

for (var i = 0; i < 5; i = i + 1) {
    print(i);
}

Core Built-ins​

The standard core built-ins in 0.0.1 are:

  • print
  • len
  • str
  • num
  • bool
  • type
  • range
  • push
  • pop
  • join
  • split
  • upper
  • lower
  • contains
  • trim
  • replace
  • slice
  • floor
  • ceil
  • round
  • min
  • max
  • clamp
  • sleep
  • clock.ms
  • random
  • random.int

The complete reference is documented in Syntax Basics.

Imports And Frameworks​

RayQuiro supports:

  • local file imports
  • alias imports
  • selective imports
  • built-in namespaces
  • project-local frameworks
  • global frameworks

Examples:

import "./lib/math.rq" as math;
from "./lib/math.rq" import sum, label as math_label;

import rayquiro.web as web;
from rayquiro.fs import write;

Module resolution order:

  1. direct path such as ./lib/math.rq
  2. project-local .rq_modules/
  3. global %USERPROFILE%/.rqio/frameworks

The full module reference is in Imports and Modules.

Built-in Frameworks​

rayquiro.web​

Builder-style HTML, routes, shell templates, and live local serving.

rayquiro.ui​

Themeable Windows UI for installers, launchers, and action-driven screens.

rayquiro.app​

Lower-level native Windows controls.

rayquiro.engine​

Simple 3D and mini-game runtime.

rayquiro.fs, rayquiro.env, rayquiro.process​

System automation APIs.

Each framework has its own reference page in this section.

Packaging And Closed Distribution​

RayQuiro includes VM-oriented package formats for supported scripts.

.rqb​

RayQuiro bytecode package created with:

rqio pack main.rq

Bundle output​

Create a distributable folder:

rqio bundle main.rq

The bundle contains:

  • an .exe launcher
  • an .rqb payload
  • launcher helpers

This is useful when you want to distribute a program without shipping the original .rq source file.

Ecosystem​

The first documented framework is telebot.

Install from the approved registry:

rqio install telebot

Or install directly from GitHub:

rqio framework install RayQuiro/Telebot

Registry manifest:

https://raw.githubusercontent.com/Raytolfas/RayQuiroAssets/main/frameworks.json

Update manifest:

https://raw.githubusercontent.com/Raytolfas/RayQuiroAssets/main/update.json

For a full first pass through the language:

  1. Installation and CLI
  2. First Program
  3. Syntax Basics
  4. Imports and Modules
  5. built-in framework pages
  6. telebot Framework
  7. Release 0.0.1