Luca

Mainly because of the lack of configuration cursive gives us to programmatically modify the look of certain UI components. For example, we cannot change the color of the border around...

Hey @0323pin! Yes I'm getting closer. The app should now have all of the features it had before (and a few new ones). Originally, I wanted to rewrite the app...

## Decouple the backend from `cursive` (and make it cleaner) The first thing would be to decouple the wiki module fully from the `cursive` library. I've been seeing the following...

## Check ratatui for requirements We need to check if ratatui satisfies all of our needs. I'm collecting all of them below (additions are greatly appreciated!): - [ ] Work...

Yes of course and I definitely see your point. I'm planning on having different "layouts" that can be switched in the config. If you want I can notify you when...

Closing this since #220 already addresses the new UI

Hey @non-descriptive and thank you for your suggestion! I really like the idea of having an overview of available keybindings. Because our keybinding-implementations currently are a mess, I have at...

> Im not a huge fan of how zellij displays keybind hints due to how it uses screen space What we could do is implement a way of hiding the...

> I would personally enjoy expose all the keybinds through an XDG_CONFIG_HOME config file. Maybe provide a super explicit default config that makes it clear what all the keybinds are...

> Well, there are some general [keybindings](https://builditluc.github.io/wiki-tui/0.8.1%20(latest)/configuration/keybindings/) exposed as well as other params. But in [some special cases](https://builditluc.github.io/wiki-tui/0.8.1%20(latest)/getting-started/overview-keybindings/) it's hardcoded That is because we're still using the cursive event loop,...