yuriy0
commented
8 years ago After some discussion, these plans have been mainly scrapped. If ECA in the future will require these features (checkboxes, etc) they can be implemented fairly easily, if ECA somewhat works that is. The focus for now is getting things to run properly, and getting test cases to work.
The frontend still needs to completed, but will consist ECA running automatically and producing log messages, and potentially other messages, for example in the title bar as many operations currently do.
After some discussion, it is clear that the front end interface is not as simple as it first appeared to be.
It may be necessary to allow the user to enable and disable individual ECA rules. This can probably be achieved by way of some check boxes on the web page (where should they go?). In autocommit mode, the enabled ECA rules will run, while disabled ones will not. If an ECA rule fixes the same invariant as an ExecEngine function, then the ExecEngine should only fire if that rule is disabled.
There should be an option to disable/enable ECA generation in the Ampersand command line program. There should also probably be an option in the prototype to enable/disable ECA globally.
When autocommit is turned off, the user should be provided with a series of options, based on which ECA rules are about to run. Then the user can choose to run one or more of those rules to see their effects individually. This is separate from the "enabled" rules previously mentioned.
Implementation wise, the following things need to be done: