tests: fixed one of the seg faults in tests (caused by pygame)
app: improved splash screen but breaks unit tests
app: trying to add a showSplash=True arg to app to get around test crashes

but it still doesn't seem to help!!
app: started making widget for a list of dicts
lib: added HSV colorspace to stimuli
lib: ElementArray now using colors, rather than rgbs and can use HSV colors too
Don't know if I should have posted this on dev-list for discussion before submitting pull-request? Anyway, the problem I try to solve here is that I always find myself timing things using:

for frame in range(3):
   stim.draw()
   win.flip()

With the multiFlip() method, this can be done like this:

stim.draw()
win.multiflip(3)

... which is also more efficient, since it does not draw the stimulus to buffer on every frame. Another advantage is, that this method is easier to understand for first-time users, who often have difficulties understanding the range()-method and hence revert to core.wait()-based methods for timing.

Best,
Jonas
Updated formatting and added sanity checking. Thanks Jeremy for feedback.
Fix typos
builder: disable Esc key (new exp setting). closes #108

- new param / checkbox in settings, disable escape
- should not affect existing scripts (same as before: allow quit)
int instead of abs in sanity check
feature: enable escape (just reverse the logic)
bumped version number
NF: Component parameters now support a 'label'

When available this will be displayed instead of the parameter name.
Names need to stay fixed for compatibility, but the label is simply used
for creating the dialog box and can change trivially as we think of better
ways to describe parameters.
DOCS
ENH: improved layout of the ExperimentSettings dlg in Builder
ENH: ExperimentHandler.getAllParamNames isn't needed by user - make private
DOCS
NF: Builder now saves data using ExperimentHandler, including a wide-csv file by default
Add Filename Collision Handling to Trial and ExpHandler