New project post: AnotterKiosk
AnotterKiosk is another full-page web-browser OS for Pi's and other PCs, displays a webpage in full screen 24/7.
It has support for multi-touch input, a watchdog/heartbeat feature, local webserver, fully read-only root FS (won't kill SD cards, ever!), manual EDID overrides, configurable caching, reverse SSH tunnel support...
Can be used for signs, conference info screens, dashboards, home automation, etc.
@gittaca Yes, it'll cause a bit of an ugly flicker, because it'll reboot the whole box eventually.
Just the timeout= flag alone might be nicer for this usecase.
The most elegant solution for this would be a custom piece of HTML with an iFrame, but this is forbidden by that energy-charts.info site.
It would be a pretty useful feature, though.
I'll add it as a feature request -- no promises, though.
@manawyrm In the end, a custom datavis script to create an optimized image for that display was the way to go.
Still: Thank you for providing the impulse to start implementing this idea :-)
Along the way, I also saw that Pimoroni recommends https://github.com/fitoori/squirt for #webScraping.
@gittaca No worries. If you‘re going the diy script route, you could totally mod AnotterKiosk, though, if HTML rendering would help you.
If you started a python script in the background in the openbox/autostart file and then screenshotted the video output from time to time, you might get a useful result.
@gittaca If you wanted to get this to work, you'd need some magic piece of code that would look at the screen content, compare it with the previously displayed content and then make a decision on whether or not to send it to the display (and make it flicker/blink/update, etc.).
This is very much in the custom code territory.
Can be down, no question, but it's very much out of scope for AnotterKiosk, sadly.
@gittaca Oh, sadly, this isn't very straight forward at all.
With Pi's in general (not just with AnotterKiosk).
The displays you've linked aren't really Linux displays in the normal sense.
Rather, they can be talked to using custom code that is manually written by the user (this makes sense because eInk displays need to be updated manually and it takes a while).
So you can't just display random content on them.
