Shepard Test Stand

Between their beta version 2.0b7 and the official release of 2.0, Processing broke backwards compatibility with some core language elements that the graphical library we're using (controlP5) depends on. There were no deprecation warnings that came up in the compiler window that I ever saw. controlP5 hasn't been updated since December of 2012, and there are only three options I can think of for dealing with this:

1. Place a restriction in the documentation that says the software can only be run in Processing 2.0b7 and below.
2. Attempt to update the controlP5 library and commit the changes back.
3. Recreate only the graphical elements we need and dump controlP5.

I haven't delved into the source code yet, so I'm not sure how hard the second option will be. I would prefer that the software be compatible with newer versions of Processing, but we'll probably be switching away from Processing for Shepard 2.0. I don't want to sink a bunch of time into something that's going to be shelved. That would also exclude option 3, but after looking at controlP5 more closely it seems that it's LGPL licensed, which is only compatible in one direction with our Apache 2.0 licensing. If we want this (pre Shepard 2.0) version of the software to be used for a long time to come, option 3 is the best option in my opinion. If the software is going to be shelved once Shepard 2.0 is released, then we should probably go with option 1.