* Added feature to create plugins using VisualizerEditors;
* It's possible to manipulate with GUI content both of GenericEditor's
  plugin component and Visualizer canvas (in the tab or window);
* Created file templates for VisualizerEditor and Visualizer (Canvas);
* VisualizerEditor class minor improvements;
* Other minor improvements;
* Refactoring and stylystic fixes.

It was in the private section. Still is practically...
Motivation:
Whenever an editor is closed, it destroy it's DataViewport tab (if it exists)
I don't want my "shared" tab to be closed when any one editor is closed, and I can fool the
VisualizerEditor destructor now.

Implemented @sept-en's tip.
VisualizerEditor implements the listener class, with a dummy windowClosed() method.
Derivations of VisualizerEditor can optionally implement windowClosed().

This might be very Cyclops Stimulator specific addition, and there might be a better way to do this:
DataWindow is used only by VisulaizerEditors. So I added a callback to the editor whenever an (open) DataWindow is closed.
I don't know how useful this might be for plugins other than for Cyclops.

Motivation: Since the datawindow is also shared by CyclopsEditors, when a window is closed, only the editor which created the window would get it's windowSelector button toggled back to "off".

With this PR, the button toggles, and the editor's windowClosed callback is called, in which the message is passed to peers through an internally maintained structure -- so that they can toggle their buttons too.

These changes were made to primarily to accommodate for the cyclops-stimulator. Since buttonClicked manipulates the DataViewport via AccessClass, a sub-class of VisualizerEditor cannot functionally override the method.
Hence:

* Added protected methods which manipulate DataViewport (via AccessClass)
* moved the SelectorButtons into protected area, essential!
* All of the additions are essential to the cyclops-stimulator.
* There is NO change in the public interface.

Now, my buttonClicked method can access the SelectorButtons, manipulate (anything about!!) DataViewport.
Please remove the (new) comments from VisualizerEditor::buttonClicked (.cpp), they are not needed anymore.

* Added docs for the class. Override only buttonEvent (as for other non-visual editors)
* Started fixing other editors, a lot of redundant code can be removed.
* See comments in VisualEditor.cpp

To run this in the future, install astyle (sudo apt-get install astyle),
then enter the following from the top-level project directory:

astyle --options=astyle.options --recursive "./Source/*.cpp" "./Source/*.h"

This will convert tabs to 4 spaces and ensure that brackets are on
their own lines.

With new jucer, windows.h is not only unnecesary, but can cause conflicts with some definitions.
Also, OpenGL.h includes disabled, as it's no longer needed and it, by itself, needs windows.h

Use the following command to update the copyright year in all files,
starting in the Source/ directory:

find . -type f -print0 | xargs -0
   sed -i 's/Copyright (C) 2012/Copyright (C) 2013/g'

Works like a charm!

Uses the parameters array to create XML data for parameter settings on
each channel when saving.

This only works for processors that use the parameters array, though I
updated LFP and Signal Generator to update that in parallel (LFP seems
to have an unrelated bug in dealing with channels that is causing some
problems). Eventually, all parameters should be used in the parameters
array, since it opens up a lot of possible holes when using default
values (they need to be specified twice), and once loading is
implemented. I've fixed some of the problems with parameters, so this
should be easier to do.

As part of this, I also fixed the implementation of
addParameterEditors. The old way of implementing a custom parameter
editor was to rewrite the virtual function, but because it was called
in the constructor, this didn't work (constructors use the type of the
parent). Instead, all editors now also pass a bool
"useDefaultParameterEditors" which is used by addParameterEditors() to
determine whether to do anything. I think this is the best way to do
it. It's initialized to default as true, though I had some trouble with
it implicitly taking the argument and so had to add true to most of the
editor functions (which is probably good practice anyway).

I also fixed some of the functions for generic processor to get
parameter index and parameter name.

Obviously, this is of considerable less use without functions for
loading parameters, but I figured it'd be better to make available for
testing with just the loading in case the changes to Parameters broke
anything I missed.

Now, when the user clicks on a tab in the DataViewport, the corresponding Editor becomes
active. Likewise, when the user selects an Editor with a Visualizer, the corresponding
tab becomes active in the DataViewport.

Modified the VisualizerEditor to allow for custom width. Everything can now be scalled off this width including the selector buttons. This update is backwards compatible. I simply added a 2nd constructor in which the width is passed as an integer

Three important changes:
- The FilterList is now the ProcessorList
- The FilterViewport is now the EditorViewport
- Any classes that need to access important UI objects have become subclasses
  of the "AccessClass". Such objects automatically obtain pointers from
  the UIComponent and register the MessageCenter as an ActionListener. This
  will make it much easier to allocate pointers to objects.

The LfpDisplayNode/LfpDisplayCanvas are more stable now, although there's
still a bug in the DisplayNode causing small gaps to appear in the buffer.