Skip to content

Split displayio into displaycore, externalframebufferio, framebufferdisplayio and epaperdisplaypio (names TBD) #7667

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
tannewt opened this issue Mar 1, 2023 · 5 comments · Fixed by #8493
Closed

Split displayio into displaycore, externalframebufferio, framebufferdisplayio and epaperdisplaypio (names TBD) #7667

tannewt opened this issue Mar 1, 2023 · 5 comments · Fixed by #8493
Assignees
@tannewt
Labels
breaks api displayio enhancement
Milestone
9.0.0

Comments

@tannewt
Copy link
Member

tannewt commented Mar 1, 2023

This will save space on boards that have an existing display and are unlikely to have an external epaper display (like pew pew m4).
@tannewt tannewt added this to the 9.0.0 milestone Mar 1, 2023
@tannewt tannewt self-assigned this Oct 2, 2023
@tannewt tannewt changed the title Split epaperdisplay from displayio Split displayio into displaycore, externalframebufferio, framebufferdisplayio and epaperdisplaypio (names TBD) Oct 2, 2023
@tannewt
Copy link
Member Author

tannewt commented Oct 2, 2023

We should go further with this as we have more boards with displays that aren't supported by displayio.Display(). (Dotclock displays use FramebufferDisplay for example. We should split displayio.Display out as well as Epaperdisplay.

@tannewt
Copy link
Member Author

tannewt commented Oct 2, 2023

displayio.Display support LCD and OLED displays that have driver ICs with onboard framebuffer RAM. We should rename it to reflect that.

Also, should we split out the different display busses as well?

@makermelissa makermelissa mentioned this issue Oct 3, 2023
Open
@makermelissa
Copy link
Collaborator

Also, should we split out the different display busses as well?

That makes sense because paralleldisplay is already split out unless it would be more overhead.

@deshipu
Copy link

deshipu commented Oct 3, 2023

Can we use busdisplay instead of externalframebufferio?

@tannewt
Copy link
Member Author

tannewt commented Oct 4, 2023

Can we use busdisplay instead of externalframebufferio?

Ya, totally open to different module names.

@tannewt tannewt mentioned this issue Oct 20, 2023
Merged
dhalbert pushed a commit that referenced this issue Oct 25, 2023
@tannewt
Split displayio hardware support from core
e1df598 
These are moved:
* Display -> busdisplay.BusDisplay
* FourWire -> fourwire.FourWire
* EPaperDisplay -> epaperdisplay.EPaperDisplay
* I2CDisplay -> i2cdisplaybus.I2CDisplayBus

`paralleldisplay` is now `paralleldisplaybus` (and registered as
`paralleldisplay` too).

Bus related helpers are split out of display_core into bus_core.
It is in still displayio since it is a dependency of both
busdisplay and epaperdisplay.

Fixes #7667
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tannewt tannewt

Labels
breaks api displayio enhancement
Projects
None yet
Milestone
9.0.0
Development

Successfully merging a pull request may close this issue.

Split displayio tannewt/circuitpython
3 participants
@tannewt @deshipu @makermelissa