Cannot edit Properties from Navigator - Project - Properties expando, and other things
Hello --
I have a couple of things I'd like to present here:
After having been sent 'Ready! API' when purchasing what I though was 'SoapUI Pro', I'm trying to adapt to it's interfaces. Perhaps some forewarning is in order here given how totally different the two tools are.
Anyways, SoapUI enabled the editing of Project properties from the Properties expando viewable from the Projects -> Project navigator view. Easy and well within accessibility range. With the new platform, these properties are now read-only? Seemingly the only way to edit them is to use the Project -> Project Settings -> Properties. That's alot of additional navigation now. Is this correct? Seems like a step back if it is.
When selecting a Service from the Navigator pane the 'Service Viewer' view is immediately generated and opened. The 'WSDL Definition' and 'Definition Parts' links that were generated do not respond to mouse clicks. Hovering over them causes the pointer to indicate they should be navigable, but clicking on them does not cause anything to occur. A right click does not yield anything either. Is this some sort of configurable behavior I need to set up?
After having sat idle for a few hours minimized, I selected the application again and my Project expando in the Navigator view was totally empty, and the arrow indicating open/closed was missing as well. The other context menues however indicated the project was open and ready to go. None of my services, resources or methods were visible however. I had to restart the application for the view to become usable again.
Some other assorted comments:
* Way too much advertising for other components designed to define the Ready! platform. I only wanted SoapUI, not all the other stuff.
* The Start page is not useful for an experienced user. Allow me to disable/hide it. And it should not be the startup page if I don't want to use it.
* The header of the working window is huge. It takes up loads of screen realistate before it leads into anything usable. Please look to making the display more effecient in its use of space.
So I'm still plowing through this new tool-turned-framework-and-platform. OK, SoapUI is under there in part, but it's now marred by things I have no use for, and do not plan on purchasing no matter how persistent the ads and links become.
Any comments on my observations are welcome, and certainly on the issues I've experienced.
Thanks you.
=bwh=
I have a couple of things I'd like to present here:
After having been sent 'Ready! API' when purchasing what I though was 'SoapUI Pro', I'm trying to adapt to it's interfaces. Perhaps some forewarning is in order here given how totally different the two tools are.
Anyways, SoapUI enabled the editing of Project properties from the Properties expando viewable from the Projects -> Project navigator view. Easy and well within accessibility range. With the new platform, these properties are now read-only? Seemingly the only way to edit them is to use the Project -> Project Settings -> Properties. That's alot of additional navigation now. Is this correct? Seems like a step back if it is.
When selecting a Service from the Navigator pane the 'Service Viewer' view is immediately generated and opened. The 'WSDL Definition' and 'Definition Parts' links that were generated do not respond to mouse clicks. Hovering over them causes the pointer to indicate they should be navigable, but clicking on them does not cause anything to occur. A right click does not yield anything either. Is this some sort of configurable behavior I need to set up?
After having sat idle for a few hours minimized, I selected the application again and my Project expando in the Navigator view was totally empty, and the arrow indicating open/closed was missing as well. The other context menues however indicated the project was open and ready to go. None of my services, resources or methods were visible however. I had to restart the application for the view to become usable again.
Some other assorted comments:
* Way too much advertising for other components designed to define the Ready! platform. I only wanted SoapUI, not all the other stuff.
* The Start page is not useful for an experienced user. Allow me to disable/hide it. And it should not be the startup page if I don't want to use it.
* The header of the working window is huge. It takes up loads of screen realistate before it leads into anything usable. Please look to making the display more effecient in its use of space.
So I'm still plowing through this new tool-turned-framework-and-platform. OK, SoapUI is under there in part, but it's now marred by things I have no use for, and do not plan on purchasing no matter how persistent the ads and links become.
Any comments on my observations are welcome, and certainly on the issues I've experienced.
Thanks you.
=bwh=
