comment about Enum.toArray()
Move client only code (phantomjsCompat.js) to client

Add some iron:router extensions so that we can more easily handle data() and waitOn()
adding templating dependency
remove debugger
comments and check to see if the template functions are being called by the iron:router code.

Also comment that the initialization code present is being run too early, so for now that init code needs to be copied to whalepath-server
expect use of one(), many(), and data()
don't require many(), data()
put toJSONValue/fromJSONValue on the constructor function so just the ctor function needs to be provided on { toJSONValue: ctor, ... } not {toJSONValue:ctor.prototype }
make the additional properties not enumerable so that when looking at keys we only see the property values themselves.
up versin
enum toJSONValue() was expecting that the first argument is the value to be converted. DbObjectType.toJSONValue() is expecting the this value to be the object converted to the json.

Enum.toJSONValue() also need to handle nulls and arrays.

So now Enum.toJSONValue() determines if if the first argument is to be converted or if the this value is the correct value to be converted
skip attributes that are null when converting to json
1.0.7
private properties that will not be saved to the database, nor special handled in anyway
1.0.8
regression: handle a null or undefined
handle being called from the template not just the route code
TO_DMR : better handling of possible user errors
1.0.9
remove debug