Allow running separately run or check commands

[GoogleCodeExporter]

When the models are large, it is better to be able to choose which run or
check command should be launched.

Maybe one possibility would be to have a specific view with all the
commands that allow to run each of them or all of them.

Original issue reported on code.google.com by daniel.l...@gmail.com on 26 Feb 2007 at 1:26

[GoogleCodeExporter]

I done the command view those days:
There is one page for all alloy file (not one for each)
and the view display command after a file is saved.
I will try to make the view multipage (one page for one file with commands)

Original comment by AntoineB...@gmail.com on 2 Mar 2007 at 9:37

[GoogleCodeExporter]

I just took a look at it. That's great. Good job!

Just one comment: it would be nice to display the issue of the command in that 
view.
the outcome of a check command is expected to be UNSATISFIABLE while the 
outcome of a
run command is expected to be SATISFIABLE.

However, the user can define the expected outcome (expects 1 or 0 for SAT or 
UNSAT).

It would be nice to have green/blue/red icons as in Junit view to show:
- green: UNSAT answer on a check command, SAT answer on a run command
- red: not expected SAT answer on a check command, not expected UNSAT answer on 
a run
command
- blue: expected SAT answer on a check command, expected UNSAT answer on a run 
command.

Original comment by daniel.l...@gmail.com on 3 Mar 2007 at 9:06

[GoogleCodeExporter]

The font or background color could change instead of using new icons.
That should be simpler to implement.

Original comment by daniel.l...@gmail.com on 3 Mar 2007 at 2:54

[GoogleCodeExporter]

Andrew's comment:
This is quite nifty, but has a bug at the moment where the commands are only 
shown
after a file is saved.  i.e. I can switch windows and the list is not updated.

Original comment by daniel.l...@gmail.com on 5 Mar 2007 at 6:32

[GoogleCodeExporter]

Commands are now colored after execution.

Original comment by AntoineB...@gmail.com on 16 Mar 2007 at 7:12

[GoogleCodeExporter]

The icon stuff is great!

There is currently one problem with the command view:
- suppose file A contains types and predicates/assertions
- suppose file B contains the commands (with an open A statement).

When opening file B, the commands are parsed correctly.

However, when trying to run the commands, an error message appears, saying that 
the
types or predicates are not found.

Original comment by daniel.l...@gmail.com on 17 Mar 2007 at 10:25

[GoogleCodeExporter]

Original comment by daniel.l...@gmail.com on 17 Mar 2007 at 10:26

• Changed state: Started

[GoogleCodeExporter]

The problem in the command view was coming upstream from Alloy 4 and has been 
fixed
in RC3.

Original comment by daniel.l...@gmail.com on 20 Mar 2007 at 8:26

• Changed state: Fixed