Namespace collision warnings

[wraithgar]

When registering things like subviews, the names in the hash are blindly applied to this, which could collide with things like props or session variables, it would be kind to the dev if there were some sort of order of precedence for those (i.e. props are always set, subviews throw if a prop exists in that namespace already).

This may also need to be functionality that's pushed down into ampersand-state (like having a safe-set internal function that ampersand-view can use when setting things like subviews to the local namespace).

[pgilad]

@wraithgar I've made an initial attempt at this: #128

Can you go over it?

[codepunkt]

Is it really necessary to access a subview named form as this.form?

Wouldn't it be appropriate to have a subviews prop (type: 'object') and to access a subview named form as this.subviews.form?