Petr Portnov | PROgrm_JARvis

Here are some good news: `examples/gui` is now `#![forbid(unsafe_code)]` and also has additional functionality: - it now uses queue to exit on `BACK` key; - it now has a timer...

Another update here with enhanced XBM support: 

Hi, @dcoles! Since you've added `gui` as an explicit module ni your recent commits, should I migrate current code to it? **UPD**: just moved `gui` to `flipperzero` crate

As a small status update on this PR: I'm out for my holidays thus I'm taking some rest from development (also, I don't have my flipper with me for testing...

Actually, callbacks are already implemented for some components here. For example `ViewPort` uses the solution based on dispatch-function.

It can be replaced with singular callbacks (in fact, current Callbacks structure is not that different). Moreover, we can add a struct implementing `ViewPortCallbacks` which would allow specifying callbacks via...

> So you'd still need to store the callback environment in either main or using on the heap using Box. Using stack location is problematic since we would need a...

@str4d, apologies for the late reply. The approach I currently use is the following: - a single trait represents all callbacks of the domain (such as `ViewVallbacks` trait representing the...

@dcoles, @str4d, hi there! Since most of the other PRs involving other APIs have been merged successfully, I guess it is the moment we get back to the discussion of...

> I think this is a good solution that balances ergonomics with efficiency. I'm happy if you want to move forward with this approach. @dcoles, Thanks for your review! in...