michaelkirk/weiqi — pull request #11 by svevang (2012-12-07 18:29:14+00:00)
Title: Feature/unguessable urls import structure

Mike, I added a commit here that brings back the old import structure because I think that we should be consistent in our approach to the namespacing issue and start a conversation about it.

The advantage here is a pattern that provides a private/public namespace and provides a single way to define the weiqi models. If we flatten access to the models (that is `require` bits and pieces anywhere), it seem to me that there could be some complexity issues.

Re: require patterns, I think this style of cobbling together a namespace is like the way a library is defined, rather then how an end user ultimately `requires` that library.

Generally, how can we guarantee that a model behaves the same in all contexts?