readme: List display drivers tested by the community#155
Conversation
5b54c83 to
e8e47b5
Compare
j-g00da
left a comment
There was a problem hiding this comment.
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
|
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, I forgot about eink drivers, I'll add them . |
|
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. |
df6d482 to
79daaf9
Compare
|
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. |
|
Yup, I'd be fine with that. Not a big deal imo |
79daaf9 to
694f1ac
Compare
|
In the meantime, I took your suggestions and made clippy happy |
Closes #154