fork/Graphite
1
0
Fork 0
mirror of https://github.com/GraphiteEditor/Graphite.git synced 2026-10-07 07:38:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update references to the latest tech stack plans

Browse Source
This commit is contained in:
Keavon Chambers
2025-07-29 15:17:41 -07:00
parent 00cfa073b8
commit 4391f88d03
14 changed files with 15 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website/content/volunteer/guide/graphene/_index.md
+1 -1
View File
@@ -62,7 +62,7 @@ The fully compiled regime is used only when the user exports the procedural artw
### Compile server
The three regimes have thus far been only a description of the eventual architecture direction. The interpreted regime is currently the only mode implemented in Graphene. The other two will require access to `rustc` which will necessitate the compile server that we will finish building and then publicly host for Graphite users in the future. Users of the desktop version of Graphite, utilizing [Tauri](https://tauri.app/), will be able to use an embedded `rustc` if the user has opted to download the Rust toolchain while installing Graphite.
The three regimes have thus far been only a description of the eventual architecture direction. The interpreted regime is currently the only mode implemented in Graphene. The other two will require access to `rustc` which will necessitate the compile server that we will finish building and then publicly host for Graphite users in the future. Users of the desktop version of Graphite will be able to use an embedded `rustc` if the user has opted to download the Rust toolchain while installing Graphite.
Without a compile server, all the nodes are precompiled when Graphite is built. The node registry (in the file `node_registry.rs`) currently exists to allow the interpreted executor to find the Rust functions that correspond to each node with its appropriate type signature. Nodes support generics, so it's currently necessary to list every forseeable concrete type signature in the registry until the compile server can generate bytecode for less common type combinations on-the-fly.