preparing to write LCM documentation
proposed cleanup (finally) of the lcm coordinate frame stack.  should have done this a long time ago.
almost missed the java lcm coder wrapper
a little more lcm doc
avoid over-subscribing (handles the singleton case)
more support for the singleton case
missed a file
JLCMCoder coordinateNames() method converst java string array to cell array
Merge pull request #1 from kuindersma/lcm-cleanup

JLCMCoder coordinateNames() method converts java string array to cell array
Merge pull request #41 from RussTedrake/lcm-cleanup

Cleans up LCM Coordinate Frames

For a long time we've had a slightly broken/redundant set of lcm coordinate frames:
LCMCoordinateFrame - which did java reflection on an lcmtype and automatically created effectively an LCMCoder, and
LCMCoordinateFrameWCoder - where you hand in the coder explicitly (which is the dominant use, especially in the drc code).
I've finally cleaned this up, where there is a single LCMCoordinateFrame class which takes an LCMCoder, or if you pass it in an lcmtype, then it makes an LCMCoderFromType.

I wanted to do this to clean up some confusion for some new external users. It is almost backwards compatible, since I have a stub LCMCoordinateFrameWCoder which prints a "deprecated" warning and then calls the new interface. But I did need to add a coordinateNames() method to the java LCMCoder interface, which will need to be populated by derived classes.