Dheepak Krishnamurthy

I do like the idea of having the rect names next to the constraints, i.e. ```rust do_layout!(rect; x == 1, y >= 2, z =2,

We will need `area` to be part of layout as well, then, right? I think we can get this syntax working: ```rust let [a, b] = layout!(area, [==50%, ==50%]); ```

Thanks to @deifactor we have a simpler implementation. I've updated the PR with it. For now, I'm planning to maintain `ratatui-macros` and use it for my projects to see how...

I think the implementation now is easy to understand ( thanks to @deifactor ) but I want to point out a couple of things. 1. This works fine: ```rust vertical![...

I wrote a very simple test: ```rust #[test] fn render_tab() { let span = Span::styled("a\tb", Style::default()); let mut buf = Buffer::empty(Rect::new(0, 0, 15, 1)); span.render(buf.area, &mut buf); } ``` And...

More context: https://github.com/unicode-rs/unicode-width/issues/6

> `let table = Table::new(rows, widths).theme(ratatui::style::themes::material::slate_blue::TABLE_THEME);` It is possible we wouldn't need widget specific themes. I think it would be possible to have an API like this: ``` let table...

My understanding is that it is a series of transformations to go from hsluv to rgb, and I'm assuming we wouldn't want to maintain that.

I believe in CSS `Alignment` uses `Start` and `End` to account for two things: 1. You can align across a vertical or horizontal axis 2. You can align left or...

For more context for future readers, from this article https://hsivonen.fi/string-length/: > This is because the base emoji is wide (2), the combining skin tone modifier is also wide (2), the...