Realm apis should follow JS Conventions

[alazier]

@appden :

I think it's best to follow JS conventions and use the Realm constructor as a namespace for the other ones (i.e. Realm.Type, Realm.Object, and a future Realm.Array). JavaScript devs will appreciate this and it'll make it easier to modularize with ES6 modules as well.

@appden feel free to suggest alternatives here.

[alazier]

@appden, would the Realm object be Realm.Realm or just Realm under this convention?

[appden]

It would be still just be Realm. This is kind of like jQuery where it's a constructor that also has static properties like jQuery.get(), etc.

[alazier]

So I changed RealmType to Realm.Type in #35 . Not sure what if anything we need to change for Object or List since users can't create these explicitly and can only get them from methods on existing objects. Would using the namespacing in our documentation be sufficient?

[appden]

Maybe this is a good time to rename the type from Array to List. Also, it looks like we still create RealmObject as a global property even though it isn't useful. We should just remove it then, right?

[alazier]

We can remove the global RealmObject. Will add the List rename to the other pr.