* Refactoring and stylystic fixes of RecordEngine class (and one
  dependency).
* Refactoring and stylystic fixes of DataThread class and all
  appropriate dependent classes.

* Added possibility to select and generate the plugins of appropriate
  available types (Processor, RecordEngine, DataThread, FileSource).
  Now it's only generates appropriate lib files and selects some types
  in processor. However, we should generate different processor files
  for each plugin type later.
* Added possibility to select processor type;
* Some refactoring of existing code and minor fixes;
* Still needs some refactoring of newer code with some improvements.

* Refactoring applied mostly because we need to satisfy the new state
  of GenericProcessor after refactoring;
* Also there were a lot of stylystic fixes applied, some minor
  improvements using C++11.

* Appropriate dependencies also have been changed.

* Now the plugin will be displayed with friendly name in the GUI;
* Hided some future functionality which is WIP now in
  jucer_ProjectType.h file.

* Basic implemntation of Open Ephys Plugin Generator.
  Now it generates empty processor & editor. To compile plugin with
  current plugin build systems we just need to copy "Source" folder
  of our plugin into plugin-GUI/Source/Plugins/ and give it some
  valuable name.
* ExampleProcessor, ExampleEditor classes refactoring and stylystic
  fixes.

On OS X, the default directory for files explicitly saved/loaded by the user is now ~/Documents/open-ephys.  Added CoreServices::getDefaultUserSaveDirectory(), which returns ~/Documents/open-ephys on OS X and the current working directory on other platforms.

this should reduce the impact of the remaining 1px plot issue until we
track it down

non plugin specific class defs should not go into the plugin specific namespace

this range makes saturation bounds visible, useful for testing if
behavior rigs work etc.

the correct value seems to be 6389 for this gain setting etc. 2do:
double check that

though there is still a small display issue if the end of the display
buffer is hit because now only 1-2samples are associated with the pixel
and this causes the min/max and histogram displays to look odd.
shouldn’t be a big issue in real applications but worth fixing when we
inevitably refactor this whole plugin.

* LinearButtonGroupManager class now have the same functionality as
  ButtonGroupManager class had before.
* ButtonGroupManager now is the base class for all other button group
  managers.
* Appropriate fixes in the CAR plugin.