Decide on UserInterface hierarchy

[ctrueden]

The LegacyUI currently implements SwingUI. This causes it to detect as compatible for things like the SwingTableDisplayViewer, which tests ui instanceof SwingUI. However, we also have a LegacyTextDisplayViewer which does nothing else but override isCompatible to test ui instanceof LegacyUI. So it seems this LegacyTextDisplayViewer is unnecessary, since the superclass (SwingTextDisplayViewer) test of ui instanceof SwingUI will already return true.

Should we:

• Make LegacyUI not implement SwingUI?
  • We would lose extensibility, since we would then need to add a LegacyTableDisplayViewer and potentially other viewers.
• Remove the superfluous SwingTextDisplayViewer?
  • This is the option I'm leaning toward. Then all SwingUI stuff will automatically work in the legacy UI.

[ctrueden]

@hinerm Thoughts?

[hinerm]

@ctrueden did you mean, remove the superfluous LegacyTextDisplayViewer? If so, yeah I'm in favor of that as well...

I wish I had documented why I thought I needed it in the first place!