misoproject/dataset — pull request #180 by iros (2012-10-26 17:52:07+00:00)
Title: Making a blank Miso.Dataset (with no options) results in an undefined idAttribute

Comes up in the perlin noise example. In constructor if `options` are blank it skips the `_initialize` routine, thus leaving `this._idAttribute = undefined`. When adding rows to this blank dataset, `this._idAttribute` is `undefined` and as a result a new property called "undefined" with a value on the row being added, breaking the actual add routine, because there is no column called "undefined".

Fixing this in the `constructor.js` results in a load order problem because in the builds derived.js is created before any of the parsers, and we need to set the default parser to the strict parser. This is because derived.js creates a new Dataset to steal its prototype.

I am triggering initialization now regardless of options state and I moved the derived.js in the build order to the bottom after importers and parsers.

This one is a bit nutty.