e8063a2b13
Move the editor core out of the firmware crate (pinned to the xtensa target, so it can't run `cargo test`) into a standalone `editor` crate, with the panel framebuffer + geometry split into a `display` crate. Both depend only on embedded-graphics + keymap, so the editor is now host-buildable and unit-tested (8 characterization tests). Firmware links them and re-exports the geometry from epd.rs; behaviour is unchanged. The xtensa firmware build was not verified in this environment.
11 lines
525 B
TOML
11 lines
525 B
TOML
[package]
|
|
name = "display"
|
|
version = "0.1.0"
|
|
edition = "2021"
|
|
description = "The GDEY0579T93 panel's geometry plus an in-memory drawable Frame (an embedded-graphics DrawTarget), split out of the hardware driver so the driver and the host-testable editor crate share one framebuffer definition without pulling in esp-idf."
|
|
|
|
# Pure embedded-graphics — no esp/std hardware deps — so the editor crate that
|
|
# renders onto Frame stays host-buildable and testable off the xtensa target.
|
|
[dependencies]
|
|
embedded-graphics = "0.8"
|