pix, deg, cm, norm unit types supported

- mouse supports pix, deg, cm, norm unit types (win32 tested; need to
test other OS's)
- Tobii and SMI support pix, deg, cm, norm unit types, still need to do
EyeLink and Eyegaze.
- Restructured project layout and created initial setup.py (although it
fails to install with easy_install as of committing. ;(
- Improved how ioHub Display class cooperates with psychopy Monitor
config file.
- Addressed issues #69, #66, #67, #60, #29, #17
Update README.rst
Update README.rst
updated EyeLink Common Eye Tracker Int. Imp.

- renamed README
updated license info
Updated project description.
Fixed issue #51
fixes issue # 73
fixed issue #72
EyeLink imp. supports multiple display coord types

- now supports providing data online and to dataStore in pix, deg, cm,
norm coordinate units.
fixed issue when using non default scalar
improved ioHubAccessDelayTest example

- ENH: ioHubAccessDelayTest graphics optimization (Jeremy Gray)
- ENH: added some missing files required for Linux keyboard support
(dropbox sucks sometimes)
EyeGaze now supports various coord types
fix #63
ioHub - psychopy integration work, new docs theme

- ioHub and psychopy now use the same high resolution time logic (ioHub
imports clock.py from psychopy if psychopy is installed, otherwise uses
a trimmed down version of the existing code.)

- new ioHub Experiment Device type added called LogEvent. Integrates the
psychopy logging capabilities with ioHub.
a) The ioHub server can create LogEvents, which are saved to a log event
table in the dataStore, and when the experiment script gets experiment
device events (by calling io.getEvents() or io.experiment.getEvents()),
any new log events are sent to the experiment process as well as the
already existing Message Event type. Prior to the user script receiving
the experiment event reply, the log events are removed from the
experiment event list, each is submitted to the psychopy logging.log
function, and the remaining Experiment Message events (if any) are
passed to the user script as before.
b) (Needs further testing) A user script can also use the iohub
experiment device as the logging mechanism by using io.experiment.log
(or .warning, .error, .critical, etc, all the same ease of use functions
psychopy logging provided). If the iohub experiment is used for logging,
then a log event is sent from the experiment to ioHub, processed and
saved to the dataStore in the log table, and also sent back to the
experiment process as described in a) so it is logged by the psychopy
logging module as well.

- Updated the ioHub html documentation theme to something cooler. ;)
finished log file integration testing

Added two examples:
- psychopyIntegrationTest/run.py: shows the logging and time base
integration as it stands now. Also has some updates to the
iohubQuickConnection function to make it more useful for a wider set of
applications (so other script only examples may be broken right now).
The example also tests that the integration is working as expected to a
degree.
- dataStore/saveDataStoreLog.py: Example of how to select a dataStore
HDF5 and save out the events for a given iohub device event type along
with the per session data. In the example, the experiment.LogEvent event
type is used, so the example saves out the experiment log entries that
the iohub either generated or received from the experiment.
examples retested, tweaked, + comments updated.