SoapUI Interface

IainJames wrote:
The SoapUI interface exists within its own managed space. There are two major issues with this: 1. This inhibits usability by providing a unique custom user space with its own rules and peculiarities. For example, if the user uses the tabs on the initial window within the SoapUI window, then they may navigate web pages in a forward only manner. Click the wrong thing? Soldier forth or start over.

Could you please explain this with screenshots? Are you talking about the startpage?

IainJames wrote:

2. This space is not effective managed by SoapUI. The "Navigator" drawer makes no note of its current size when hidden and seems to return to view at some predetermined size. The main window has no concept of its own size, when resizing this window (the larger window in which the application is contained) the smaller managed window does not resize to fill the newly available space. If the smaller managed window is resized to be larger than the larger application containing window it must be scrolled to view the content (or if the containing window is resized to be smaller than the contained window). None of the contained windows make use of the operating system's (neither Windows nor OS X) built in window management. You cannot use alt-tab or command-tab to navigate between these windows.

Most of this is restrictions of Swing/Java and we can not change the behavior. Which windows can't you alt-tab between? Please provide screenshots.

Note that soapUI Pro uses an improved internal windows manager which is more similar to browser tabs.

Regards

Henrik
SmartBear Stockholm