Functions for managing the signal chain are no longer handled by
the EditorViewport, but by the SignalChainManager

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 DataThread shouldn't have a MML all the time, but it does need it
when signaling that the data source is not found.

Also fixed a line in the FilterViewport that was causing the enabled
status of editors to fail to update.

Processors used to have their sample rate and inputs/outputs set when
their source/dest nodes were set. Now, this step doesn't occur until
after the signal chains are constructed. So far, this seems to make
things run much more smoothly.

Since every processor now gets asked to enable() prior to the start of
acquisition, it's much simpler to move the steps involved in preparing
for acquisition into these methods. This the processor from beginning
acquisition when prepareToPlay() is called upon initialization.

In combination with an EventNode, a WiFiOutput node is able to send a
simple message to a hard-coded address via UDP. This is the first sink that
actually emits an output. It's obviously over-simplified, but as a
proof-of-concept, it seems to be working well.

The IntanThread was occasionally looking for data after acquisition was disabled,
which would trigger the SourceNode to attempt to manually disable callbacks.
The only negative effect of this was that if the user was currently viewing
a different signal chain, it would switch back to the Intan chain unexpectedly.
This is no longer the case, as the SourceNode checks to see whether or not
it received a proper disable signal from the ProcessorGraph before notifying
the UI that data may have been dropped.

There was a minor bug in the SourceNode code, which caused it to delay restarting
acquisition for about 1 second after acquisition was stopped. Now acquisition from
the Intan Board can be restarted almost immediately after it finishes.

Changes to the DataThread, SourceNode, and UIComponent classes allow data
threads to disable callbacks if they are no longer receiving input. So
far this has only been tested with the Intan Board, but it works really well.
Unplugging the board in the middle of acquisition allows the thread to exit,
and callbacks to be disabled, without any seg faults.

DataThreads (e.g. IntanThread, FileReaderThread, FPGAThread) are now created at
the same time as the source node, rather than at the start of data acquisition.
New methods for starting/stopping individual threads are required, although
only the appropriate methods for the IntanThread have been written.

Another important change is that the SourceNode now periodically checks for
an appropriate input source every few seconds while acquisition is not in
progress. It's the responsibility of the individual DataThreads to notify
the SourceNode if their input has disappears. In the case of the IntanThread,
this involves attempting to change the baud rate. If an error code returns,
it informs the SourceNode that the input is missing. This, in turn, informs
the FilterViewport that the source is no longer enabled, thus deactivating
that particular signal chain.