Major Description
I've written an additional BlockingDialog class which can host any Dialog outside of the normal HostFrame.
This way, awt is used to do the
in a blocking way,
i. e. the flow of control doesn't return before the content Dialog is closed.
The content can be set in the constructor or (e. g. via bxml) using
{@link #setContent(Dialog)}.
A small change to DesktopApplicationContext is necessary: static class HostDialog has to be given package access.
