I think this one pulls up a key issue.

We want to get away from the concept of "Dialogs" since we really are trying not to have them.

Instead we have "panels" that might be embedded or might be floated in a dialog. That's why the swatches dialog was using that instead of hooking directly into dialog widgets. The idea is to encapsulate things so that they are container agnostic. If something is needed to function properly, it can just be added to the Panel API.

That also will get a lot of common code moved into a single Dialog-that-holds-a-Panel class, and remove a lot of redundancy.

Again, a "Dialog" should be a "top level window that can float around" where as a "Panel" should be a "container of a set of things for a common purpose".