On-Pipe Broadcasted App

open-eio / Open-Pipe-Kit-Project

Documentation and planning for the Open Pipe Kit. An OPK is a device that pipes data from sensors to anywhere you want, no programming required.

8 stars 0 forks source link

On-Pipe Broadcasted App #4

Open rjcorwin opened 9 years ago

rjcorwin commented 9 years ago

The App will be a User Interface to make easy the following...

Find a Device in the area
Configure a Device's network settings
Create multiple Pipes on a Device
For each Pipe...
- Import a thing driver
- Choose a thing driver
- Configure a thing driver
- Import a reservoir driver
- Choose a reservoir driver
- Configure a reservoir driver
- Set the Pipe's frequency
- Enable/disable a Pipe
- Delete a Pipe
Review available software updates
Apply software updates

The Device will broadcast an HTTP API that publishes endpoints that will make all of those functions possible, the Pipe App just needs to provide the UI for interacting with that HTTP API. Hosting the Pipe App directly from the Device is an option but bundling it in a Phonegap App would allow the App to search for the Device's IP address on the network. That would be awesome!

rjcorwin commented 9 years ago

A good example to look at is the Fido UI (see here for the HTML/JS/CSS) which is kind of what we are aiming for on the Pipe App except the Pipe App will be able to configure multiple Pipes and Fido was always just one.

rjcorwin commented 9 years ago

Thinking about names for this... Pipe Control Room?

dwblair commented 9 years ago

Pipe Control Room is good! Although 'Control Room' seems less cute than the pipe metaphor we've been running with ... have we invoked the 'valve' metaphor here, yet? Could be: 'Valves' or 'Valve Room' or 'Valve Central' or 'Valve UI' or something?

On Tue, Feb 10, 2015 at 7:06 PM, R.J. Steinert notifications@github.com wrote:

Thinking about names for this... Pipe Control Room?

— Reply to this email directly or view it on GitHub https://github.com/open-eio/Open-Pipe-Kit/issues/4#issuecomment-73811593 .

rjcorwin commented 9 years ago

Screen flow for creating a new Pipe command

connect to wifi, change hostname (runs pirateship)
choose a device driver (runs install)
configure sensor pull, pull test
choose a database driver (runs install)
configure database, pull and push test
configure interval, send built command to crontab with command that ends in #opk so that we can tell what OPK commands are in crontab

Screen flow for editing existing Pipe commands (one screen)

list opk commands, ability to edit and delete

rjcorwin commented 9 years ago

The client-side exec function I wrote was just accepted into the web-terminal project. https://github.com/rabchev/web-terminal/pull/17

rjcorwin commented 9 years ago

Behold! The first web form built using help from the command line. screen shot 2015-04-21 at 4 15 05 pm

rjcorwin commented 9 years ago

Version 0.0.1 has dropped. Here's a screenshot of the first watch command being run that pulls data from a device and pushes it to a database, all driven by the GUI. screen shot 2015-04-22 at 8 50 09 am

rjcorwin commented 9 years ago

Taking a different direction, renaming this the Jack-In-The-Box App for now. Building a template to create JITB -> https://gist.github.com/rjsteinert/32c43313cf80e4ce6c10