Checkpoint: parameter labeling.

I'm finally finishing this off.

Starting to work, but I need to handle array-type editors.
Cleanup, commenting, prefer parent editors when paths conflict.
Fix NPE.

If we skip adding certain components, then we need to tolerate
them being missing later. Durr.
Fire a property change when the entire object changes.

Jeez.
Maybe, since apparently everything existing seems to work
fine without this, I can just do this in the path editor
or something...
But c'mon: if the entire object changes that's the epitome of
a notification-worthy change. Maybe the manual update() calling
when a new object is set at the top level would be unnecessary...
Checkpoint.

- Fix mispelled class name.
- If an editor for the path isn't found, lop off the array-style bits
  at the end and try again. More TODO.
Remove debugging, fix bug with path stripping.
Do something reasonable for array types.

The path is adjusted until an editor is found, and any adjustment
portion of the path will be provided to said editor.

Most editors will expect "" for that additional info.
TableArrayListEditor will store the parameters in a Map
and assemble them into a label when needed.

Ship it!
Simplification.

Use the same variable for storing the parameter label for the
array-type editors. Recalculate it when a piece is changed.