You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Talking about wild ideas... While reading through the Contributor Guide, I saw the link to Hledger compiled to JavaScript. 馃
This raises some interesting potential consequences. As I'm currently creating Cashier, a GUI app for entering transaction records in JavaScript, the prospect of having a JS version of hledger greatly increases the potential of the Progressive Web Applications (PWA) platform. So, before jumping to conclusions:
what are the capabilities of the JS-compiled version?
how official/supported is this version?
what are the intentions for the future?
Naturally, having the full Hledger available inside the app would be a great addition, providing immediate insights, although the transfer to the desktop would still be the main goal. As mentioned, this opens up possibilities too numerous to list here. At a minimum, I would look to use this as an engine for providing some basic reports (register, per period; account balances, etc.), if that turns out to be convenient.
Status: this was a one-time tech demo, which hasn't been touched since. It uses GHCJS, which still works but does not support recent versions of GHC. But on the upside, GHCJS is planned to be included in GHC's next major release, 9.6, so it could become quite viable again.
That's interesting information! Looking at GHCJS (finally), I see it is using emscripten, which converts c/++ programs to wasm runtime or Node.js. I actually created an issue to try that with Ledger, which is written in C++.
I'm actually now more keen on direct wasm implementation as that should be more direct and potentially more performant. However, let's see how that works out.
Talking about wild ideas... While reading through the Contributor Guide, I saw the link to Hledger compiled to JavaScript. 馃
This raises some interesting potential consequences. As I'm currently creating Cashier, a GUI app for entering transaction records in JavaScript, the prospect of having a JS version of hledger greatly increases the potential of the Progressive Web Applications (PWA) platform. So, before jumping to conclusions:
Naturally, having the full Hledger available inside the app would be a great addition, providing immediate insights, although the transfer to the desktop would still be the main goal. As mentioned, this opens up possibilities too numerous to list here. At a minimum, I would look to use this as an engine for providing some basic reports (register, per period; account balances, etc.), if that turns out to be convenient.
Resources:
The text was updated successfully, but these errors were encountered: