Use code propperty instead of set_code
Merge branch 'master' of github.com:vispy/vispy

* 'master' of github.com:vispy/vispy:
  Docstrings and minor cleanup.
  More subtle name for cient buffer example. See issue #56
  DataBuffer.set_shape allows omitting the dtype
  Some refactoring of buffer.py   * The Buffer class is now data agnostic for real.   * Got rid of size attribute; use shape instead (which is richer)   * Implemented set_shape, set_data, set_subdata, to match with Texture     and RenderBuffer   * Data can be set at any time, overriding both shape and dtype   * VertexBufferView cannot set data.   * Split ClientBuffer in ClientVertexBuffer and ClientElementBuffer.     (and these can also not set data)
  ElementBuffer needs DTYPE2GTYPE mapping. For consistency also give VertexBuffer such a mapping. Refactored the Texture a bit so it uses the same names.
  Make Progam.set_vars() a bit smarter so it can ignore elements that are not used.
  Fixed up some examples. Some where just too big to fit on my screen, which is anoying.
  Allow 3D textures in shader.
Merge branch 'master' of github.com:vispy/vispy

* 'master' of github.com:vispy/vispy:
  Refactored buffer.py according to the discussion with Nico We had a chat yesterday to discuss the API of the buffer. We decided on two attributes: count: the number of vertices vsize: the number of elements in the vector (like float, vec2, vec3, vec4) Dtype, vsize and stride are fixed on initialization. Count can be changed afterwards using set_count or set_data. I like this approach. The code is now much cleaner and shorter. NOTICE: some demos still fail, as well as some unit tests. I will fix these next week. At least it should be better than previous commit.