> - Some features I'm interested in are being able to install libraries
Might be tricky to achieve, as I don't think we can load arbitrary files at runtime in Obsidian. What could possibly work, is loading libraries via HTTP and evaluate them in Wielder after that, but would be tricky is my guess. Worth looking into to though.
> or a recommended path for getting access to libraries via RPC to a less limited runtime. For example, lets say I want to use the hugginfaces API to do text extraction within my note. Clojure has some great tools for running arbitrary Python code from within it, but how can I leverage that code from within Weilder.
If you can run a HTTP server locally (via Python's http.server for example), with the right headers set regarding CORS, you should be able to just use JavaScript `fetch` to GET/POST/PUT stuff to locally running servers. In Wielder, you'd do something like `(js/fetch "http://localhost:8080/read-data")` and use it just like you'd use any JavaScript Promise.
> - Is there planned support for importing from a namespace in another note? My current workflows are everything goes into one note and then I just hide the sections with the code so they don't distract but sometimes there are pages worth of code. I expect over time I'll find a lot of things that have common implementations.
Yeah, I'm currently thinking and playing around with how to achieve this, hopefully via supporting Clojure's `ns` declarations directly, so you can do `(ns my-vault.a-page)` in one document and then simply `(ns another (:require [my-vault.a-page :refer [a-func]]))` in another.
Not the best UX directly, and looks bad, so hopefully the whole `ns` endeavor will work out instead, but will take some time before I can implement that correctly.
> Amazing work and thank you so much for making something so cool
Thank you! And thanks a lot for the feedback, it's very helpful.
Might be tricky to achieve, as I don't think we can load arbitrary files at runtime in Obsidian. What could possibly work, is loading libraries via HTTP and evaluate them in Wielder after that, but would be tricky is my guess. Worth looking into to though.
> or a recommended path for getting access to libraries via RPC to a less limited runtime. For example, lets say I want to use the hugginfaces API to do text extraction within my note. Clojure has some great tools for running arbitrary Python code from within it, but how can I leverage that code from within Weilder.
If you can run a HTTP server locally (via Python's http.server for example), with the right headers set regarding CORS, you should be able to just use JavaScript `fetch` to GET/POST/PUT stuff to locally running servers. In Wielder, you'd do something like `(js/fetch "http://localhost:8080/read-data")` and use it just like you'd use any JavaScript Promise.
> - Is there planned support for importing from a namespace in another note? My current workflows are everything goes into one note and then I just hide the sections with the code so they don't distract but sometimes there are pages worth of code. I expect over time I'll find a lot of things that have common implementations.
Yeah, I'm currently thinking and playing around with how to achieve this, hopefully via supporting Clojure's `ns` declarations directly, so you can do `(ns my-vault.a-page)` in one document and then simply `(ns another (:require [my-vault.a-page :refer [a-func]]))` in another.
For now (with a bit bad UI I'd admit), you can use the normal Obsidian including to reuse code from multiple pages, just uploaded an example here: https://wielder.victor.earth/Examples/Embed+code+from+other+...
Not the best UX directly, and looks bad, so hopefully the whole `ns` endeavor will work out instead, but will take some time before I can implement that correctly.
> Amazing work and thank you so much for making something so cool
Thank you! And thanks a lot for the feedback, it's very helpful.