summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-07-24 14:02:39 -0300
committerGabriel Schneider <[email protected]>2026-08-01 15:02:07 -0300
commit2c670371a21cde5ab506eda02dc2233e20fc1fe1 (patch)
tree5b5b09ac6b1bf40dd739d7ad9e21325763336455 /docs
parent685b8c8e74c9edbdf701594f50ff1b70ac288ec9 (diff)
parentfcfe51b6507ade9c72f94e40ee5c31a8ee818e30 (diff)
downloadpardes-2c670371a21cde5ab506eda02dc2233e20fc1fe1.tar.gz
pardes-2c670371a21cde5ab506eda02dc2233e20fc1fe1.zip
docs: note native web client + WASM-only text logic in ideas.typ
Diffstat (limited to 'docs')
-rw-r--r--docs/ideas.typ4
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/ideas.typ b/docs/ideas.typ
index f4faf810..c954dbbd 100644
--- a/docs/ideas.typ
+++ b/docs/ideas.typ
@@ -8,6 +8,4 @@
- like if I get some search results I can just use tab to navigate them, the editor should know:
- semantic boundaries (maybe just jump to the next clickable thing?)
-- undo for everything?
- - I want search results in general to be logged, that's one of the reasons why the tty is a good fit
- - so it'd be cool to undo that too?
+|- web: native web client (DOM-rendered, not canvas/WASM). Use WASM only for text logic (parsing, grep, treesitter analysis, look internals) — rendering stays in native DOM/CSS for accessibility, performance, and browser-native text selection. Send structured display commands (layout tree, styled spans, cursor, scroll pos) from WASM to JS via a flat buffer or JSON.