P.s. I know you've mentioned ATAC already. You might also be interested in two other Ratatui based apps - openapi-tui and slumber - for some UI ideas in the same space.

51:22 pro-tip, take a look at the docs on the type when the docs on methods don't make sense (i.e. layout::Layout)

8:30 we've added better constructors for Layout in later versions of ratatui (Layout::horizontal and Layout::vertical)

3:14 unfortunately ChatGPT data cutoff dates for most models is before ratatui was forked from tui-rs. It's grown something like 50K LoC since the fork (with about 10K of that being docs)

the app evolved quite a bit! congrats on that

54:34 We've gone through a bunch of iterations of what a good approach for apps and state looks like, and in particular whether to make a ui method that accepts frame or to think in terms of Widgets. The JSON editor was one of the first tutorials that were written after the tui -> ratatui fork, so it hasn't yet been updated / made more idiomatic. Tui-rs was really built around the idea that the widgets were constructed for each frame and then discarded (because the render function in the widget trait consumes self). A few months ago we relaxed that and introduced the WidgetRef trait, made all the built-in widgets non destructive to their state when rendering, which made it possible to store them between frames. This enables things like you see in the tabs example `impl Widget for &App`, which says if you have reference to an App, then you can render this directly instead of building up the widgets to render on each frame. There's another similar approach for tabs in the Demo2 example which is probably worth looking at too. That one pulls each tab into its own type, and lets the type handle rendering the contents (via the widget trait). Strum is a pretty neat crate that adds some missing pieces to make it easy to do things with enums easily (iterate, add display strings, convert from a number to the specific item, etc.), But I can see the mind explode meme happening when you saw it, so it might be too much magic for the example code. It either needs some good comments or perhaps to be replaced with the manual versions of things (which are just a bunch of match statements in a function). If you want to highlight that you're streaming Ratatui content next time, feel free to advertise this on our discord server (which is bridged to matrix too for those that don't discord).

51:11 It's set by the `#[derive(Default)]` on `App` and on the `SelectedTab` (where the #[default] is mentioned)

48:35 Yeah, implementing widget on your app instead of manually calling methods on frame is a pretty nice way of encapsulating your rendering logic into the struct that you care about.

46:52 LOL, sounds we need to ditch strum from the examples :D (or at least document that a bit better)

30:35 rustfmt is what you want (run cargo fmt)

4:44 there's some good docs on the website about using color-eyre for handling errors nicely (and we're probably going to migrate most of the examples to use that)

Please go on, it's awesome to see i'm not alone struggling while learning Rust :)

i'm very glad that, i'm not the only one who was lost in the same particular way. i appreciate the work of ratatui a lot but damn the difference from the counter to the json editor is like switching a game from easy to hardcore mode for a rust beginner ^^

I have a similar approach to learning new things. But i tend to use different ollama models. It used to be codellama, now it's usually llama3.

Thanks for the tutorial! I don't know if it's just me who has this preference, but would you consider doing normal tutorial videos (i.e not livestreams)? As interesting as live streams are, sometimes I don't really have the time to go through the whole discovery process and just want to skip ahead to how i actually do the thing. That said, you speak very clearly and explain things well and it looks like you're just getting started with your youtube channel. So hopefully if you try both formats out, you can see which one gets you more viewers... Oh, and also posting a link to source code is always a plus :) Anyway, thanks again for the content and best of luck with the channel! You got +1 Like & Subscribe - Keep up the good work :)

Hey! Been following and enjoying the content. If I may suggest some future content maybe you can lookup bevy and maybe make a simple game like pong, space invaders, asteroids, to name a few but using a TUI interface, I think that would be interesting to watch and follow. Anyway, one thing at a time, and keep up the good work. <3

Keep coding more stuff bro 💪 You have my support

If code could be zoomed in it would help viewers a lot, since this kind of "coding together" video - means split screen - for those without multiple monitors... Thank you very much for the content!

'PromoSM'

This video was loaded! Fire 🔥

its funny that I recently started with doing the same idea of a project, a couple of days ago

Such an underrated channel. I love rust, use it everyday and I always learn thing from your videos. Thank-you.

best of luck man

So the OS keeps a cache of the ARP requests, but also can listen on the network for other people requesting APR resolution. Additonally network gear like switches and APs can intercept ARP requests and respond directly (if they know)

side note it called ARP not A R P. (say 'park' without the k and the p at the end 😂)

There are alternatives to the match on the unwrap. For example, unwrap_or() which returns an alternate on fail. The unwrap_xx() are a little finicky, but can make things a bit less verbose and easier to read. Raw unwraps are discouraged unless you know that it cannot fail.

I love this kind of calm code only focused videos, keep doing it super helpful

It's working! 😄