overturetool
Review toolbar buttons and menus in default setup
The following bug was originally reported on Sourceforge by nick_battle, 2013-05-29 20:14:16.682000:
Eclipse perspectives are very configurable regarding the toolbar and menu contents, but the buttons and menus that we have by default don't always make sense for the perspectives concerned. Can this be reviewed? The toolbars shouldn't offer buttons that aren't relevant to the perspectives (and include those necessary!), and the menus should ideally offer the Overture perspectives and views by default.
Comment by nick_battle, 2013-05-29 20:59:01.141000:
Another example: at least in Linux, the Debug view defaults to not having the debug icons showing (Resume, Step over, Step into etc). To turn these on, you have to select the tick box on the view's configuration. But this is basic stuff - it must be enabled by default.
Comment by nick_battle, 2013-08-09 09:21:48.122000:
- Release: v2.0.0beta2 --> v2.0.0beta4
- Priority: 5 --> 7
Comment by nick_battle, 2013-08-09 09:21:48.657000:
Also, in 2b4 there is a big gap to the left of the debug/run/external - between these and the print icon (in VDM perspective). Can this not be removed? I don't seem to be able to do it via Eclipse itself.
Low priority though.
Comment by joeycoleman, 2013-10-15 07:15:17.730000:
I'm assigning this to PGL, on the basis that before action can be taken in code, we have to first define what it should look like overall. I understand the complaint, and I think it's valid, but we need specific input on this from the user side.
I've now assigned this to milestone 2.1.0, and tagged it as an enhancement. @pglvdm needs to drive this.
The main Overture/VDM perspective: The New button, and save, save all, print are fine. Then there is a curious gap, which is sometime even bigger, so I'd like to know what that is. Next the Debug, Run and Run external are fine (you can set up external commands to run). Then there is "Skip all breakpoints" which we don't need in VDM. The Search is good. The up/down annotation buttons are fairly standard and do work (they move to the next Error or Warning in a file). The move to last edit works, and is also fine. Similarly the backward and forward buttons move to the last/next location that you placed the cursor, which is fine. The Pin Editor button doesn't seem to work, so we should remove that. The Error Log view is of little use to ordinary developers. Annotations don't always work. They will work if you create a non-VDM file name (like X), enter some spec, and then rename it to X.vdmsl without closing the editor. Then error/warning markers appear in the file and can be navigated with the buttons. But if you close and re-open the editor, the buttons are disabled. Addional buttons for functionality that users often would like to carry out such as POG (it would have the same effect as if one would right-click on the selected project and select proof obligation generation) and similar for Pretty Printing (PP).
The Debug perspective: The New button, and save, save all, print are fine. Then we have the strange gap again. The Debug/Run/RunExt are probably fine here, though a non-debug "Run" would be rarely used? Skip all breakpoints is fine in Debug. Then there are nine buttons before the search that shouldn't be here - they are debugging buttons, but they appear at the top of an executable in the Debug view when they are needed, which is sufficient. The Search, annotations and fwd/back buttons are fine (caveats above about annotations). PIN Editor is broken again.
The Combinatorial Testing Perspective: The New button, and save, save all, print are fine. Arguably, none of the Debug/Run/RunExt buttons should be present in CT because you don't run specs, you run/debug traces. None of the nine debugging buttons should be there - if you debug, you drop into the Debug perspective in any case. Search and the annotations, fwd/back are fine (caveats above about annotations). Pin Editor doesn't work again.
The Proof Obligation Generation View: This looks about right in fact. It is essentially the same as VDM, which is reasonable as you might want to do normal work while looking at the POs.