Flamework now uses Twitter Bootstrap for layout
Merge pull request #16 from grantmd/master

Flamework now uses Twitter Bootstrap for layout
always return a structured response from library functions that can contain db failures so the caller can actually see what went wrong
simplify caching for users library, using lib_cache functions
not sure where this pattern came from, but it's not one we actually use; display flags go in templates
more moving of nav tabs into tmeplates
generally safest to leave off the closing tag
added test for opening php tag at start of code and no closing tag. the latter tests generally fail, but i'm about to clean that up
just enable this until i refactor god perms
removed closing php tags from libraries
removing closing php tags - all tests now pass again
vastly simplified lib_cache
cleaner version of memcache library - desperately needs some tests
moved the libraries that are not being used by anything into an extras folders. they will stay here until they either get moved to another repo (like flamework-geo, flamework-aws, etc) or
are needed for something in the base distribution. the goal is to make the deafult webroot as lean as makes sense
create a new tests sunfolder for travis setup. include some extra config to allow connection to mysql
simple database tests to show we can connect and that tables got created
getting rid of stray random globals - `no_cache` can be a config var
we no longer have stray globals. added timing_keys for completeness
when running tests, allow parse errors to be shown
modified the cache libraries to return structured responses