Vaxis sadly cannot be used for applications which want to serve their contents via ssh to the (remote) user.
Instead I wrote my own tui library zterm, which this tui application now uses. This will serve two purposes:
implement the tui application and be servable through ssh (see wish-serve)
serve as documentation and showcase of an example application for zterm
Vaxis sadly cannot be used for applications which want to serve their contents via ssh to the (remote) user.
Instead I wrote my own tui library [zterm](https://gitea.yves-biener.de/yves-biener/zterm), which this tui application now uses. This will serve two purposes:
1. implement the tui application and be servable through ssh (see [wish-serve](https://gitea.yves-biener.de/yves-biener/wish-serve))
2. serve as documentation and showcase of an example application for **zterm**
- split structure for better inclusions
- create PlainRenderer to render contents to the terminal
- simplify events
- clearify what structs are created on the heap and which are on the stack
- quit event is now emitted from the main event loop and not the input loop (see helper function `App.quit`)
- rename several variables and/or functions for easier understanding
- introduce `App.interrupt` to stop the input thread and start a new sub TUI which takes over the entire screen (i.e. 'hx', 'nvim', etc.)
Layout is a simple pane without any restrictions, which should be
implemented next to see if the interfaces are stable and usable enough.
As for example the interface for `Widget.content()` has changed to
return a `[]u8` and not a `*std.ArrayList`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Vaxis sadly cannot be used for applications which want to serve their contents via ssh to the (remote) user.
Instead I wrote my own tui library zterm, which this tui application now uses. This will serve two purposes: