renamed source directory pyvis -> vispy
Update address of our mailing list
Improvements to backend system for Canvas.
More window stuff is supported. Clear names to indicate what the backend
should make a _vispy_* function do. There is only one getter (geometry).
The rest is all setting stuff or doing an action on the backend widget.
Almost all backend-to-canvas communication occurs through events.
Made canvas.geometry a get+set property.
This kind of gives an idea of what I think would be a very friendly
interface (we got rid of two setter methods in this case.
Made a first version for a backend for glut.
Added some docs on what events a backend should emit for the canvas.
Made backends more the same.
Also made Application/Canvas/Timer backends more similar.
Application, Canvasm, and Timer all have a 'native' attribute.
And the backend is in all cases stored as _backend.
Made a start with auto-generated API documentation.
Also improved docs a bit and filled in a few missing docstrings.
I made a hook to readthedocs, so these API docs should be auto-updated
on each commit/push to vispy.readthedocs.org.
Docs: refer to vispy.org in API docs.
Added link to wiki and API docs.
Event API change:
  - accept() and ignore() are replaced with handled property, which is _not_ enforced
  - added Event.blocked property, which is enforced
Documentation updates for event system
Event: Added MouseEvent and KeyEvent.
But not sure how to "use" them yet.
Also some minor fixes.
Modifications to event API:
  - Event base class requires source and name arguments
  - Removed EventEmitter.__init__ connect argument
  - Removed EmitterGroup__init__ event_names argument
  - EmitterGroup.add accepts multiple event specs as keyword arguments
  - Added stub Event subclasses
Merge branch 'master' of github.com:vispy/vispy

Conflicts:
	vispy/event.py
minor updates to Event class
Modifications to event system to make Events more strict.
After discussions between Luke and me. Events keep track of
the source of the event (responsibility of EventEmitter) and
always have a 'type' attribute that tells the user what kind
of event it is (e.g. mouse_press, key_release, paint, etc.).
Experimental: demonstrating alternative for custom Emitters.
EventEmitters have become a bit more 'heavy' with the previous
changes, with the EmitterGroup doing the heavy lifting. In effect,
creating custom emitters feels a bit clumsy. This commit demonstrates
that custom EventEmitters may not be necessary, but we may introduce
event emitter extensions or something like that.
Couple of small fixes to event system.
Improved docs for event.py.