Architectural Refinement

In order to ease further development, the architectural refinement needs to 
progress in the following way:

Remove all glue-code from the SpyController and shift it to a platform-specific 
module. The only instance of which I can think at present is the loading of the 
Stranger names.

Replace all logging code. We will instantiate and manage logging objects in an 
implementation of an abstract class that is separate from the core code. This 
is because commons-logging may not be available on all platforms.

Refine the state reporting capabilities of the SpyController. For all the 
awesomeness of replacing the code-based UI declaration with the YAML required 
by swing java builders, there is still a shit-ton of unnecessary 
state-maintenance done in the UI class.

Separate the protocol code from the communication code. No matter what platform 
we're on, the protocol code will remain the same, but the communication code 
will definitely change.

Create separate projects for the platform dependent code (e.g. communication, 
UI, and logging in one project) and the core omeglespy-z code (e.g. controller 
and protocol code in another project).

Original issue reported on code.google.com by darkimp...@gmail.com on 4 Apr 2012 at 3:25

Eyez0nly / omeglespy-z

Architectural Refinement #21