feat: Add web rendering of the TUI application#1742
Conversation
Renders the initial page but the navigation and auto-refresh are disabled Made with AI
Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
Still WIP: there is an issue with RefCell<App> mutably borrowed
The overcomes the problem with using mutable RefCell inside spawn_local()
Use 0/epoch as a fallback timestamp when parsing Prometheus samples in WASM32
This renders the TUI app in a <canvas> HTML element and it looks much more like the terminal one.
|
can't wait to see |
|
btw show |
|
|
|
|
The Web TUI uses the ballista-logo.svg as a banner. I just modified the text color to be white. I also tried with ratatui-image for the TUI but it cannot render SVGs, only bitmap formats, and the PNG does not look good on Ghostty (my terminal app). So, the TUI will continue using tui-big-text. |
|
Failed jobs correction: just plan cant be shown and there is no reason why job failed |
…rics This makes it consistent with all other tables
In WebTUI we use only the default config, without loading files and env vars
|
|
||
| router.with_state(scheduler_server) | ||
| let cors = CorsLayer::new() | ||
| .allow_origin(AllowOrigin::exact("http://localhost:8080".parse().unwrap())) |
There was a problem hiding this comment.
Should we make this configurable or permissive and let any Ajax client able to connect ? As long as it can reach the Scheduler address
martin-g
changed the title
| cargo clippy --all-targets --package ballista --all-features -- -D warnings | ||
| cargo clippy --all-targets --package ballista-cli --no-default-features --features cli,tui -- -D warnings | ||
| #cargo clippy --all-targets --package ballista-cli --no-default-features --features web -- -D warnings | ||
| cargo clippy --all-targets --package ballista-examples --all-features -- -D warnings |
There was a problem hiding this comment.
It seems running clippy on ballista-examples crate concretely exposes some problems:
error[E0432]: unresolved import `ballista_core::object_store`
--> examples/examples/custom-client.rs:19:20
|
19 | use ballista_core::object_store::state_with_s3_support;
| ^^^^^^^^^^^^ could not find `object_store` in `ballista_core`
For some reason those are not reported when running Clippy on the whole workspace (line 21).
Fixes a Clippy error: ``` error[E0432]: unresolved import `ballista_core::object_store` --> examples/examples/custom-client.rs:19:20 | 19 | use ballista_core::object_store::state_with_s3_support; | ^^^^^^^^^^^^ could not find `object_store` in `ballista_core` ``` Signed-off-by: Martin Tzvetanov Grigorov <mgrigorov@apache.org>
2 participants
Which issue does this PR close?
Closes #1660
Rationale for this change
Be cool :-)
Seriously, I don't expect someone to prefer use the web-tui than the TUI app.
What changes are included in this PR?
Added a WASM32 start method for the web app.
Implement custom event bus for the tick updates and key events.
Are there any user-facing changes?
The TUI application should behave the same way.
The Web TUI is completely new way to interact with it.