Skip to content

readme: List display drivers tested by the community#155

Merged
orhun merged 1 commit intoratatui:mainfrom
deadbaed:readme-displays
Feb 2, 2026
Merged

readme: List display drivers tested by the community#155
orhun merged 1 commit intoratatui:mainfrom
deadbaed:readme-displays

Conversation

@deadbaed
Copy link
Copy Markdown
Contributor

Closes #154

Copy link
Copy Markdown
Member

@j-g00da j-g00da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Hmm display compatibility is already guaranteed by embedded-graphics so it will always be pretty much 1:1 with exclusion of quirky drivers (that use custom colors). In such case I think it makes more sense to list only drivers, and not precise displays, because as long as the driver is supported, all displays compatible with this driver should just work.

The list then should also include epd-waveshare and weact-studio-epd drivers (with features that enable these).

cc: @orhun

@deadbaed
Copy link
Copy Markdown
Contributor Author

Absolutely, I did not think of that!

I am tempted to show example of displays for each driver, to help newcomers know if their display is supported or not (for example, mipidsi supports ILI9341 and ST7735).

I forgot about eink drivers, I'll add them .

@orhun
Copy link
Copy Markdown
Member

orhun commented Jan 30, 2026

Showing example of displays for each driver makes sense to me! Sometimes it's hard to find out which driver to use for which display.

@deadbaed deadbaed force-pushed the readme-displays branch 2 times, most recently from df6d482 to 79daaf9 Compare February 1, 2026 17:34
@deadbaed deadbaed changed the title readme: List displays that was tested by the community readme: List display drivers tested by the community Feb 1, 2026
@deadbaed
Copy link
Copy Markdown
Contributor Author

deadbaed commented Feb 1, 2026

The markdown linters yells when lines are over 100 chars.

I split my content over multiple lines to make the markdown linter happy, but now clippy is yelling.

Would you be open to remove the limit of 100 chars for markdown files? I feel this limits us more than helps us.

Personally I'd prefer to allow markdown on long lines, instead of chunking it to multiple lines to please a linter.

@orhun
Copy link
Copy Markdown
Member

orhun commented Feb 1, 2026

Yup, I'd be fine with that. Not a big deal imo

@orhun orhun requested a review from j-g00da February 1, 2026 19:58
@deadbaed
Copy link
Copy Markdown
Contributor Author

deadbaed commented Feb 1, 2026

In the meantime, I took your suggestions and made clippy happy

Copy link
Copy Markdown
Member

@j-g00da j-g00da left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Copy link
Copy Markdown
Member

@orhun orhun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx for this

@orhun orhun merged commit cf8156b into ratatui:main Feb 2, 2026
26 checks passed
@github-actions github-actions bot mentioned this pull request Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a list of supported/tested displays

3 participants