search

voorkant / voorkant-core

https://voorkant.org/
MIT License
2 stars 3 forks source link

logging #28

Closed Habbie closed 2 months ago

Habbie commented 6 months ago

Right now we dump all kinds of debug logging to stderr, which is very useful during development. Eventually, we would want some more functional logging. For client-cli, stderr is fine. For FTXUI, logging to stderr destroys the interface/makes it blink, etc. For LVGL users, stderr is great -if- they have a console, but our eventual target environments (say, Toon1) won't have that.

So, we need to handle logging in a saner way. I'm thinking a vector or deque of log messages, that a frontend class can dip into. In FTXUI, we'd usually have room for a pane (not too narrow) to show a few messages in, perhaps even scrollable. For LVGL, maybe a separate screen for looking at logging, and some notification icon with a number on it for new messages above a certain severity?

cyclops1982 commented 2 months ago

We have fixed this with #55 and also have a logbox now with #72