Ref ticket #2 - Added browser support

[OscarGodson]

This makes it so you can do jake build and it'll generate a browser version including a minified version.

[polotek]

I don't really want to land this just yet. Do you plan to use it for something right now? You should use your fork and let me know how it goes.

[OscarGodson]

@polotek I want to add the orm stuff for collections. I prefer to code in a browser (im just more comfortable with it). Once that's added probably build out a demo app. Oh, and ORM stuff would be a diff thing like: orm.ctor.js. Just extending it.

[polotek]

I don't think we want the orm stuff here. This is a simple library that can be used for lots of different things. If you're gonna do an orm type thing, make it another library that uses this as a dependency.

var Model = require('model');
var Person = Model.extend({ })

Where Model is an extension of ctor but adds a bunch of orm type functionality.

[OscarGodson]

Yeah, read 2nd sentence of my message above :)

[polotek]

I did. I just read it wrong I guess. Sounded like you were going to send a pull request adding that to this package. Carry on.

[OscarGodson]

Also, I don't want to do the word model. I've been meeting more developers who dont look at apps as MVC, but components with data. I mean, I prefer models, but i'd like it to be more of an object store than a model store.

[polotek]

An object that comes from persistent storage and has behaviors (e.g. methods) on it, is a model :) But I hear what you're saying. I'll be interested to see what you come up with.

[OscarGodson]

I totally agree. It's just semantics, but, you know. Developers.