Editing Touch Panels
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]]. | A bunch of folks worked on getting the touch panels working. Then another bunch of folks wanted to setup some sort of crazy control Noisebridge in case of a fire thing with it, [[SCADA]]. | ||
Fast forward a few months, the touch panels really haven't gotten that much use out of them. Currently the boot image for the panel starts up linux, runs Iceweasle full screen and points to a URL on [[Pony]]. All that's left is whipping some HTML together to make a neat interface that provides information and control regarding things we currently have in the space. | |||
Currently the boot image for the panel starts up linux, runs | |||
==Requirements== | ==Requirements== | ||
===Back end=== | ===Back end=== | ||
* | * Web apps! | ||
** | ** Can Apache host it? Then you can write it. | ||
===Functionality=== | ===Functionality=== | ||
Line 59: | Line 42: | ||
* Scroll bars are going to be tricky | * Scroll bars are going to be tricky | ||
* Navigating to pages outside of the panel site might lead to the browser getting into a weird state. The dumb fix is to kill and restart the browser session every once in a while (3 hours sounds good). | * Navigating to pages outside of the panel site might lead to the browser getting into a weird state. The dumb fix is to kill and restart the browser session every once in a while (3 hours sounds good). | ||