gBASIC Studio

gBASIC Studio is a desktop IDE for gBASIC, written in the language it serves. It is deliberately a separate application with no privileged path into the runtime: Studio consumes the interpreter and standard library exactly as another gBASIC application would.

• 232headless golden-file cases across the Studio and agent suites
• 3database routes for SQL work: SQLite, PostgreSQL, and ODBC
• 1language dogfooding its own desktop application end to end

An editor that remembers the work, not just the file

Put the caret in a section and press Run. Studio replays the sections above it in a fresh child interpreter, runs the selected section, and keeps the result under a stable identity. Output history survives edits and restarts; stale results are marked rather than silently presented as current.

The surrounding panes follow the caret: the run strip names the active section before execution, results switch as you move, and failures remain readable in a dedicated errors pane instead of being clipped into a status line. Stop and Force Stop cover the difference between a cooperative process and an unresponsive one.

Programming and analysis in one workspace

• Project browser. Create or open a project, work with files and folders, and restore the session on the next launch.
• SQL documents. Each statement becomes a cell with its own result; Run All shares one connection across SQLite, PostgreSQL, or ODBC.
• Schema-aware tools. Browse tables and columns, see the exact catalog query Studio asked, and insert an explicit-column select.
• Rich results. Tables, charts, images, structured values, and ordinary text choose viewers without hiding the original result.
• Permissioned assistant. The integrated assistant can propose and perform actions through a declared permission model rather than receiving silent access to the workspace.

Why it matters

Studio is the hardest kind of language test: a real graphical application that has to manage processes, files, durable state, database connections, themes, and user mistakes. Much of gBASIC's process control, source inspection, atomic replacement, and diagnostics surface exists because this application needed it and exposed what was missing.

Run it

git clone https://github.com/Solifugus/gbasic-studio.git
cd gbasic-studio
./studio

# Or open an existing project directly
./studio gui ~/.gbasic-studio ~/development/myproject

Studio uses GTK 4 through gBASIC's GObject-Introspection bridge. Its core test suites are headless; display-specific tiers skip cleanly when GTK or a display is unavailable.