EdJoPaTo
EdJoPaTo
im not entirely sure I entirely understand what you are trying to accomplish so my answer might not perfectly fit. But this is what came to mind when reading it:...
> In a related note my tree could be very large and I noticed that when I have to copy it in Tree::new() during every render this would be very...
Just as a side note, I added colorisation to the json stuff b0387798c9ac7d2b7649fc33604f08ba3ccc95ef (still unreleased and probably not the best for performance yet)
To give an update on this issue: With the upcoming `TreeData` trait (#34) not all identifiers are known to the Tree anymore, only the ones currently open. (which speeds up...
SVGs can be rendered pixel perfect for monitors and will always look sharp. Thats my main reason to prefer SVG wallpaper when possible/available. [Gnome also delivers their wallpapers as SVG...
I have the same issue with my tree widget and a lot of data. Especially scrolling was really sluggish. I delayed that problem with debounced input events. Only render every...
My `TreeItem` trait idea [from earlier](https://github.com/ratatui-org/ratatui/issues/1004#issuecomment-2027200475) turns out as a huge improvement. When rendering the `cargo metadata` JSON as a Tree this ends up in a 5 time performance improvement....
The currently allowed lint clippy::missing_panics_doc catches a bunch of these cases and requires to write a panic documentation. Then we just need to seek documentation including this panic section. Also,...
`Buffer::index_of` could get an alternative `Buffer::index_of_opt` returning `Option` instead. Same with `Buffer::get(_mut)` → `Buffer::get(_mut)_opt` returning `Option`. The methods potentially panicing should be deprecated in favor of the `_opt` methods. See...
This forces someone to migrate everything at once. Also, I am not sure what happens with dependencies. My widget is in a different crate, it enables a feature. What about...