added rst page skeleton

- added rough structure of workshop agenda and rst page layout
- indicated my understanding of who will /lead/ content addition for
each section by adding "(TBC - Sol, Jon, or Jon and Sol)" to each
section.

Let me know what you think.

Thanks!
Revert "added rst page skeleton"

This reverts commit 92b5ca13abdc7ad24db7cbf136b670c84a7a5648.
ENH: Added getPosition() to eye tracker device

equiv. of getLastGazePosition(), but is device independent. i.e. any
device that can report a current screen location will have a
getPosition() method.
ENH: basic hooks and standalone dependencies to run ipython notebooks

The notebook works with psychopy, and can generate windows, collect
responses etc

BUT it can't be shut down and wx ceases to respond, so the app has to
be reset! So it's currently disabled, pending someone spawning it from
a thread or process. But the dependencies (tornado and pyzmq) are now
included
Merge pull request #352 from jeremygray/master

RF: hardware.iolabs, and demo
DOCS: updated manifest so that yaml.part files are distributed with demos
DOCS: changelogs
Merge branch 'master' of git://github.com/psychopy/psychopy
BF /ENH: see desc.

- BF: Removed left over ref's to FullScreenWindow
- ENH: Modified keyboard and mouse example with timeouts from no device
event activity
- ENH: Modified eye tracker example to use ioHub / DataStore conditions
file so hdf5 file can be used for analysis (ECEM workshop driven update
to demo)
- BF: Added back iohub version of pylink files to
iohub.devices.eyetracker.sr_research.eyelink. I think the newer version
packaged with psychopy is causing the issue of busy-waiting and longer
iohub round trip delays previously reported)
Merge pull request #354 from isolver/master

BF and ENH. See commit info for details
BF: Added missing getActiveConnection() method.

Not sure how I missed this one. ;(
Merge pull request #355 from isolver/master

BF: Added missing getActiveConnection() method.
BF: proper sorting of events accessed via device

+ BF: Add 0.1 /msec/ to KeyboardChar Event time so that when it is
retrieved from a list of events, it just follows the KeyboardRelease
event that generated it. Previously, the two event types had the same
time, and the sort alg would always put the KeyboardChar event just
/prior/ to the KeyboardRelease event that generated it, which is kind of
incorrect.
Merge pull request #356 from isolver/master

BF: proper sorting of events accessed via device
DOC: contains() not implemented for GratingStim

- could test if the mask has non-zero alpha at that point
- could test if the point is a sensible closeness to pos given texRes
  (define a circle of vertices and use normal .contains algorithm)