finally able to use data_mapper to pull data from an sqlite database
using a slim template because that is what the tutorial used
this will be fixed later
http://www.sitepoint.com/just-do-it-learn-sinatra-ii-2/
finally able to use data_mapper to pull data from sqlite db
using a slim template because this is what the tutorial suggested
http://www.sitepoint.com/just-do-it-learn-sinatra-ii-2/
Able to output a list of devices + add a new on each refresh due to
code in main.rb, understanding of C in crud essentially
Able to output attributes, devices, and routers from db in settings
Can now list avps routers and devices in the webui from the database
dang yo
Trying to do a post w/ a slim template + cleanups
tried using fucking sequel orm, does not work so far
Moved from using datamapper to using sequel as an ORM

also moved settings into its own file, separate from the database bits,
I also moved the settings erg and associated values into “keys” as it
really is just a key value store.
Fixed links in settings views for lights, blinds, etc ...
added some more test data to the database
changed the header to say "Keys Devices Routers", till I clean that up
Lots of cleanups

1. html cleanups in the ergs
2. added router port and protocol to the router table
3. defaulted to keys page when selecting settings
4. removed unused table class “dashboard”
5. added table-bordered class to the settings tables
6. pointed everything to cloverleaf.css vs lights.css (except lights)
added support for router_type
able to manually insert using Keys.insert(:key => 'Sharon', :value => rand * 100)
W00t! able to add keys via the web interface. Need to clean up the erb
and add portions for the devices and routers
before I try using the delete http method
initial support to delete a key via the web interface

The buttons are ugly, the tables look dumb, but they work. Goodnight.
moved navbars to included files

It was silly to be maintaining these on individual pages.
1 introduced bug is I can no longer set the active class for the links
because they are all using the same navbar, have to sort that out.
working example of dynamically setting class=active based on requested url
sorted things so that the navbar would dynamically set class=active
for active link based on requested url