His GitHub says this:
"This might sound like a convoluted way to generate the calendar, but I'm doing so mainly because (i) it's easier to
format the calendar exactly the way I want it using HTML/CSS, and (ii) I can better delink the generation of the
calendar and refreshing of the eInk display. In the future, I might choose to generate the calendar on a separate
RPi device, while using a ESP32 or PiZero purely to just retrieve the image from a file host and update the screen."
Its easy to design something nice looking in html and css and compute is cheap. Seems like a fine solution to me. Maybe even better since you can push the image generation somewhere else and just have the RPI update the screen with an image which would save lots of power.
I've tried making nice interfaces with GUI toolkits and its a nightmare.
He has a valid point, generating the image on a separate device (heck, you could do that on AWS Lambda for free) and only grabbing the resulting image could vastly improve battery life. Then you could also switch from a power hungry Pi to a simpler choice like an ESP32.
https://github.com/speedyg0nz/MagInkCal/blob/main/render/ren...
Its easy to design something nice looking in html and css and compute is cheap. Seems like a fine solution to me. Maybe even better since you can push the image generation somewhere else and just have the RPI update the screen with an image which would save lots of power.
I've tried making nice interfaces with GUI toolkits and its a nightmare.