voleum/gr-base
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.org

Browse source
This commit is contained in:
EatThePooh 2025-07-30 17:21:16 +00:00 • committed by GitHub
parent 08906a78b8
commit bbee313d53
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
README.org
View file

@ -92,7 +92,7 @@ Spells based on interpreter scrolls (like Bash, Node.js) can have their inscript
*** Development environment
Grimu-R projects being Nix flakes, the development tooling ("loom") is provisioned as a Nix shell. It gives you the visual editor, the companion CLI tool and the scroll-defined execution context for spells.
*** Workflow
The visual editor is served by a development or application server. Changes and execution requests for server-side spells are sent over a bidirectional WebSocket connection. User modifications are stored locally in the browser's storage, exportable as a file. Weaves are tracked by usual SVC tools.
The visual editor is served by a development or application server. Changes and execution requests for server-side spells are sent over a bidirectional WebSocket connection. User modifications are stored locally in the browser's storage, exportable as a file. Weaves are tracked by usual VSC tools.
*** Cross-language connections
Think Unix pipes but with structured data formats like JSON lines instead of plain text.
*** Execution environment
@ -132,7 +132,7 @@ To some extent, yes. While Grimu-R is built on top of Nix and wouldn't make a lo
*** How do I test my weave?
If you do it manually: right in the visual editor. Add spells with a constant output as test data sources and stitch them to the spells you want to test.
If you need automation: build an edition and call the ornaments programatically. If you already have test data stored in the weave, you can extract it by the spell's id using loom CLI or library.
If you need automation: build an edition and call the ornaments programmatically. If you already have test data stored in the weave, you can extract it by the spell's id using loom CLI or library.
** Features
| | On the roadmap | Ideas |
|--------------------------+--------------------------------+--------------------|