-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
I'm admittedly not too familiar with the UI code, but it is associated with graphics.rs, view.rs, and tree.rs. graphics.rs contains the layout primitives. view.rs contains the View struct which is the view state of each Document; it is often used to find the Document currently in focus. tree.rs is complex and it handles the actual layout. How this is rendered is up to the dependent crate, but in helix-term we define a Component trait which is registered with the Compositor. It iterates over each Component and renders it.
We were also considering https://crates.io/crates/rhai. Ultimately, we don't want to face the burden of maintaining a language should it get abandoned.
Do you have a plan how to make all configurations of the editor introspectable (or ideally editable and storable for later lookup [say for project-specific bindings/language-specific ones])? This is a big pain in neovim, where default bindings are not searchable. For inspiration: https://github.com/nvim-telescope/telescope.nvim is extremely useful, since it provides introspection into many things.
From my experience, I've enjoyed using https://github.com/rune-rs/rune. Sadly it has the same issues as Rhai in that it has a higher chance of it being abandoned relative to a lisp / Lua.
One good choice might be RustPython, which compiles to WASM.