tweaked some things to get travis tests running... hopefully

Gulpfile.js

@@ -43,7 +43,7 @@ gulp.task('build', function () {
 
 gulp.task('localBuild', function(){
     'use strict';
-    
+
     gulp.src(['public/javascripts/app.js', './public/javascripts/components/**/*.js','!./public/javascripts/components/**/*_test.js'])
         .pipe(concat('app.js'))
         .pipe(jshint())
@@ -87,4 +87,4 @@ gulp.task('test', function (done) {
 //         .pipe(plumber())
 //         .pipe(concat('app.js'))
 //         .pipe(gulp.dest('public/javascripts/built/js/'));
-// });
+// });

package.json

@@ -4,7 +4,8 @@
   "releaseName": "Antonio Banderas",
   "private": true,
   "scripts": {
-    "start": "node app.js"
+    "start": "node app.js",
+    "test": "gulp test"
   },
   "dependencies": {
     "ejs": "*",

readme.md

@@ -1,9 +1,9 @@
 #Action!
+![build status](https://travis-ci.org/designfrontier/Action.svg)
 `Action!` is a front end sub/pub based framework for event based development. No more passing around dependencies, no more worrying about timing. Events free you to build apps that function they way the real world does: cause and effect.
 
 Need data? Ask for it. Need to do something with that data? Listen for when it is sent back to you and do it. Need to watch for the user to do something? Listen for it and react accordingly. `Action!` embraces the asynchronicity that is the world around us to create better front end experiences and code.
 
-
 ##Road Map
 So there are a variety of things that need to be completed for Action! to be ready for primetime. Some of them are basic (getting statemachine working), others are more complex (build tooling for troubleshooting event stacks). I am going to keep them here and make this a living document.