facultymatt

Kinect/ projector calibration and mapping:

Map Projections to moving objects in real time.

Uses the Kinect to track and locate objects. Might be overkill for this project since the table doesn't move. However might be cool to use in reverse to NOT project onto people who are interacting with the table: http://chparsons.com.ar/#camara_lucida

Kinect projector calibration

Another example that might be overkill since the table is static.

facultymatt

{
  "directory": "components"
}

facultymatt

ACL / Roles + Permissions

https://github.com/djvirgen/virgen-acl Simple and elegant, create your own checks. No middleware?

https://github.com/OptimalBits/node_acl Use as middleware, create your own roles and access. Great choice.

https://github.com/tschaub/authorized Similar to connect roles... but a bit more robust? you can create roles and action, and associate many roles with that action

facultymatt

web: node server

facultymatt

<?php

date_default_timezone_set('America/New_York');

/*
 *---------------------------------------------------------------
 * APPLICATION ENVIRONMENT
 *---------------------------------------------------------------
 *
 * You can load different configurations depending on your

facultymatt

/**
* Add express to package.json
* Keep the app.get('*') for nice sinlge page app support
*
*/

var express = require("express"),
  app = express(),
  port = parseInt(process.env.PORT, 10) || 4567;

facultymatt

Workflow

• Make changes on develop. Commit and push to origin.
• Swtich to master, pull and merge from orgin.
• IMPORTANT: You'll need to commit the build files since the build process times out on Heroku and so you need to do it locally.
• From your Master Branch, change your .Procfile to web: ./node_modules/.bin/grunt build optimize && node server/server
• Run $ foreman start which will simulate building on Heroku.
• You should now have a bunch of new files in your build folder. Commit those. DONT COMMIT THE PROCFILE!
• Now, back to normal...
• Wait! Make sure to test the app as building and minification often breaks stuff!

facultymatt

function ImagesController($scope, $routeParams, $location, Global) {
  
	// get global settings
	$scope.global = Global;
	
	// set filepicker key
	filepicker.setKey('Akpol0G7ZQ7ODgRPSZPJRz');
	
	// define our empty image object
	$scope.newImage = {};

facultymatt

// A design pattern for a mean.io notifier module

var transport = null; // will store our connection to nodemailer
var actions = ['generate_quote', 'generate_application', 'submit_application']; // actions allowed to email

// There is no model
exports.initModel() {}

// There are no routes
exports.initRoutes() {}

facultymatt

Emailer / Notifier Best Practices

• Supports any protocol, ideally by just setting a config option or function.
• Supports sendgrid, which is a Heroku based app, making it super simple to get running on develop.
• Won't fail, or catches errors, if any variables are missing.
• Checks for development and testing environments, and prevents email send (console.log instead)
• REUSABLE! The library itself, and maybe even the template, should be resuable across projects.

Good Looking Approaches