What's next ?

[mindoodoo]

Now that we have settled on a logo, release day as well as version number, we would love for everyone to share their ideas regarding what the future may hold for ratatui. At the beginning of the forking process a lot of ambitious and interesting ideas were flying around, hopefully there are many more to be pitched !

A couple points of discussion to kick things off :

• Integrating third party crates into the base ratatui crate
• Integrating third party crates into another extension crate
• Look at open feature PRs
  • feat(paragraph): allow word-break in wrapped paragraphs #33
  • feat(chart): add Histogram chart type #34
  • feat(block): support placing the title on bottom #36
  • feat(widgets/chart): add option to set the position of legend #25
  • and many others...
• Support for Test Driven Development for library users #78

Update: Those interested in discussing it live in a meeting, please mention your availability: https://calendly.com/d/y2h-b3c-n7s/ratatui-3

[nidnogg]

As a newcomer to ratatui in general (I've never used tui-rs before in any project), would anyone have any tips on where to start contributing/grokking the codebase? The current open issues seem kind of broad in a sense that I can't settle on a good candidate to look into first.

I've seen on Discord that @orhun has a pretty good template that's pending maintenance, perhaps that would make for a good one?

[orhun]

I've seen on Discord that @orhun has a pretty good template that's pending maintenance, perhaps that would make for a good one?

Sure! We can update the template for possibly simplifying the codebase and adopt a better approach for newcomers. Come to think of it, it would be nice to move that repository to this organization. What do you think? @mindoodoo @sayanarijit

[mindoodoo]

Yeah definitely, I also think it might be worth discussing potentially separating templates from the main repo. Like making a ratatui template repo, where we can maintain orhun's and then add other ones. Food for thought.

[Nickiel12]

I definitely think that having template projects would make it easier on newcomers. And with the way that this crate is used, there can be several different design philosophies explored by using different templates.

What I mean by that, is that some of the examples are single file programs, while others are separated into four or five files minimum. Exploring the pros and cons of each of them and explaining the thought process behind the different structuring would be beneficial for new users coming from different frameworks.

[mindoodoo]

Depending on the amount of people interested in contributing, as there will be quite a bit of work. We could create a second repo where we could maintain a set of templates for ratatui projects. We could also start working on a cookbook similar to the rust cookbook, which I think would be quite fitting for a ui library.

[mindoodoo]

A very easy way to prioritize what to add first would be to add an entry to the readme that links to an issue to gather the main pain points beginners are encountering.

[conradludgate]

A feature we've been hoping for is fdehau/tui-rs#552 as a lot of our users in atuin have been asking for it

[mindoodoo]

Since it was draft it wasn't imported, could you reopen it ?

[rishadbaniya]

Is there any plan to add non text stuff like Gauge into things like Table?

[mrjackwills]

Just want to ask, is it worth thinking about submitting a PR about EnableMouseCapture, or maybe trying to add a new feature in ratatui.

There's an open PR in Crossterm, crossterm-rs/crossterm#640, but I don't see any movement on it.

Basically, by default, EnableMouseCapture captures every single mouse movement, which can have performance impacts, but it can be adjusted easily to only listen to clicks, scrolls, and/or drags

[Nickiel12]

If it isn't that hard to create a PR for, I would definitely be all for it. One of the advantages to this crate is the flexibility to choose exactly what you need, and it would be really annoying to suffer performance hits just because you needed to detect a scroll event.

[mindoodoo]

Yeah for sure, it's always worth it to submit a PR. Just make sure it's a change that's coherent with the purpose of the crate.

[gibbz00]

Just wanted to let you all know that I'm experimenting with viewport scrolling! I'm sending in an RFC as soon as I get a prototype working :)

[dzfrias]

To follow up #116, I'd love to see tui-rs-tree-widget considered in the meeting. I don't think I'll be able to make it to the meeting itself, but it would be cool to see it represented still!

[mindoodoo]

Will definitely be discussed. Another contributor also mentioned adding aditional widgets he had built, so we'll keep you posted !

[sayanarijit]

Those interested in discussing live in a meeting, please mention your availability: https://calendly.com/d/y2h-b3c-n7s/ratatui-3