VS Code
The goome extension
vscode-goome is on the VS Code Marketplace. Search goome in Extensions, or:
code --install-extension goome-ui.vscode-goome
On VSCodium and the other forks it is on Open VSX, search goome there too. Offline, grab the .vsix from its releases and use Extensions > … > Install from VSIX.
The side panel 0.5. Click the goome icon in the activity bar. It has:
- quick actions: New Project, Open UI builder, Search docs, Open docs
- every
.goome.jsonand.goome-theme.jsonin your workspace, click one to preview it. The same list sits in the Explorer under your files - the templates for each language, click one and New Project starts with it picked
- a snippet cheat sheet, click one and it goes into the file you have open
The rest:
- Snippets - type
goomein C, C#, Python or Java.goome-overlayandgoome-appare a whole program,goome-loopis the poll loop, and theres one for every common widget. The 0.5 ones aregoome-anim,goome-anim-color,goome-ease,goome-text-input,goome-a11y,goome-font-fallbackandgoome-text-dir0.5 - goome: New Project - runs goome new. If its not on your PATH it downloads goome.py and runs it with Python
- Preview - open a
.goome.jsonand hit the preview button top right. It draws with the builders own code and updates while you type. The C, C#, Python and Java buttons copy the code out - Hover - any
goome_*function in C for its signature, the note from goome.h and a docs link - Schemas -
.goome.jsonand.goome-theme.jsonget checked while you type
Settings: goome.cli points at your own goome or goome.py, goome.python picks the Python.
Per language
| Language | Extensions |
|---|---|
| C | C/C++ (ms-vscode.cpptools), and CMake Tools (ms-vscode.cmake-tools) if you use CMake |
| C# | C# Dev Kit (ms-dotnettools.csdevkit) |
| Python | Python (ms-python.python) |
| Rust 0.5 | rust-analyzer (rust-lang.rust-analyzer), CodeLLDB (vadimcn.vscode-lldb) to debug. More |
| Node 0.5 | nothing extra, the types come with the package. More |
| Go 0.5 | Go (golang.go). More |
| Zig 0.5 | Zig Language (ziglang.vscode-zig), CodeLLDB to debug. More |
| Lua 0.5 | Lua (sumneko.lua). More |
C, your own project
- Folder with
goome.h, agoome.cwith the two implementation lines and yourmain.c(the get script makes these). - File > Open Folder.
.vscode/tasks.jsonfor Ctrl+Shift+B:
{
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"command": "gcc -g -O0 -o myapp main.c goome.c",
"windows": { "command": "cl /Zi /Od main.c goome.c /Fe:myapp.exe" },
"group": { "kind": "build", "isDefault": true },
"problemMatcher": ["$gcc"]
}
]
}
.vscode/launch.jsonwith acppdbgconfig,programset to${workspaceFolder}/myappand"preLaunchTask": "build". Windows iscppvsdbgandmyapp.exe, Mac needs"MIMode": "lldb". Then F5.
cl only works if VS Code got started from the Visual Studio developer prompt. With mingw use the gcc line on Windows too.
C, inside the c-goome repo
Theres already a .vscode folder, open the repo and install the extensions it asks for. It configures itself from the CMake presets.
- Ctrl+Shift+B is the CMake build
- the test task runs ctest
- the remake goome.h task runs
tools/single.py - in the debug menu hello is the real thing, hello (test backend) runs a test script so nothing touches your screen. Both run the launch target CMake Tools has picked
C#
dotnet new console -o MyApp, open the folder.dotnet add package GoomeSharpin the terminal. Working on a csharp-goome clone instead?./build.shthere anddotnet add reference ../csharp-goome/src/GoomeSharp/GoomeSharp.csproj.- F5, C# Dev Kit makes the launch config.
Python
- Python: Create Environment in the command palette, pick it as the interpreter.
pip install goomein the terminal- F5 on your script.
Add "env": {"GOOME_BACKEND": "test", "GOOME_TEST_SHOTS": "shots/"} to the launch config for the test backend.
Gotchas
On Windows C# and Python need goome.dll next to your exe or in runtimes/win-x64/native/. GoomeSharp copies it on build but only if ./build.sh win (or build.sh in Git Bash with mingw) made it first, otherwise its a DllNotFoundException. GOOME_NATIVE=C:\path\to\folder points somewhere else.
Mac permission prompts say VS Code, not your app. Why.