4 ms·
Have you seen the Haystack editor? Addresses some of this: https://github.com/haystackeditor/haystack-editor https://github.com/haystackeditor/haystack-editor
by threecheese 2y ago
Have you seen the Haystack editor? Addresses some of this: https://github.com/haystackeditor/haystack-editor https://github.com/haystackeditor/haystack-editor
I am interested in “node-based” design tools and libraries, given the convergence of editors and whiteboards within the knowledge management domain (Obsidian canvas, Heptabase), and they are encountering the kinds of issues you noted. The generative AI boom has been pushing this along very quickly, by improving and creating libraries to support tools like ComfyUI, DAG visualizers, and knowledge graphs; these solutions being so “close to the code”, I am hopeful they’ll be solved.
- WillAdams 2y agoThe Haystack Editor has been mentioned here previously, and seems quite promising. It makes an interesting contrast to: https://leo-editor.github.io/leo-editor/ https://leo-editor.github.io/leo-editor/ I wound up using TeXshop/TeXworks with a Literate Programming setup I hacked together with a bit of help from A.X. on tex.stackexchange: https://tex.stackexchange.com/questions/722886/how-to-write-out-multiple-text-files-from-multiple-instances-of-latex-environmen https://tex.stackexchange.com/questions/722886/how-to-write-...
- andybak 2y agoMy first thought was "I didn't mean browser-based GUIs" but then I paused. It still feels wrong for the kind of apps I'm usually thinking of when people talk about node editors - none of them are web apps. But I guess convergence and all that.