gfx VS esp-adf

Thx, interesting. Made me G**gle it: https://github.com/codewitch-honey-crisis/gfx

The graphics library to drive the display is htcw_gfx, as I mentioned, https://honeythecodewitch.com/gfx/ which includes true type font and jpg support built in.

Also just as importantly, this runs the htcw_gfx graphics library through its paces, so it's a good starting example of how to use some of the core features like JPGs and Truetype fonts.

As some of you may know I'm the author of the htcw_gfx library for IoT. The library supports TrueType fonts, JPGs, alpha blending, automatic color matching for indexed devices like color e-paper displays, X11 colors, arbitrary pixel and bitmap formats and automatic conversion between different pixel formats. It was designed as a bit more high level of a library than something like TFT_eSPI, and is built using C++isms and Generic Programming, so templates are what's for dinner.

It *is* possible to use htcw_gfx with this API, as long as you're willing to draw to a bitmap and then send that bitmap to the display. It's pretty easy to do from platformIO under arduino or the ESP-IDF.

htcw_gfx makes heavy use of templates and metaprogramming to allow for things like arbitrary binary pixel formats that wouldn't be feasible to compute and manipulate at runtime. The documentation covers what it looks like to use it.

If you're getting started, the ESP8266Audio library makes it easy to play audio with the Arduino toolchain. For more advanced use cases, Espressif's own ESP-ADF has a lot of useful features and examples.