Refactor Configuration.resolve() and general configuration binding

There are many objects in the GUI that need access to the Configuration to 
complete their setup. Currently it's up to the developer to make sure that any 
time these objects are created outside of the Configuration itself the creator 
then calls Configuration.resolve() so that the object can bind to the 
Configuration and get any additional information it needs.

This happens in particular with implementors of the SPI classes such as Feeder, 
Camera, Driver, etc.

This seems sloppy.

It may be that we want to move the listing of these available classes into the 
Configuration and then make Configuration responsible for creating instances of 
them. Another option could be some kind of DI framework.

Original issue reported on code.google.com by ja...@vonnieda.org on 11 May 2012 at 10:06

Cocuyo17 / openpnp

Refactor Configuration.resolve() and general configuration binding #6