You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to have some kind of mouse interaction for typical basic operations? I mean actions such as:
separate a goal that is a conjuction (that is, call fconstructor)
separate a hypothesis that is a conjunction (that is, call choose or cases')
Create two goals from a hypothesis that is a disjunction (that is, call cases)
introduce the first part of a goal that is an implication (intro)
introduce arbitrary objects for a goal that is of the form ∀ x,... (again intro)
choose the corresponding objects from a hypothesis of the form ∃ x, ... (choose`).
There are other situations where this kind of approach could be used, but I just listed the most evident ones.
I am thinking on something like this: if you have a situation like the ones before, you can right-click on the corresponding part, and a menu shows up proposing the corresponding action (maybe with some fields to fill with the names of the hypothesis/objects that will appear), and a button to trigger the action. When the button is pressed, the corresponding tactic is written and executed.
The rationale for this request is that these are actions that are repeated a lot, and writing them once and again ends up being very boring. Also, maybe this approach could encourage users to explore the proof status with more attention (or maybe not).
The text was updated successfully, but these errors were encountered:
Would it be possible to have some kind of mouse interaction for typical basic operations? I mean actions such as:
fconstructor
)choose
orcases'
)cases
)intro
)intro
)∃ x, ... (
choose`).There are other situations where this kind of approach could be used, but I just listed the most evident ones.
I am thinking on something like this: if you have a situation like the ones before, you can right-click on the corresponding part, and a menu shows up proposing the corresponding action (maybe with some fields to fill with the names of the hypothesis/objects that will appear), and a button to trigger the action. When the button is pressed, the corresponding tactic is written and executed.
The rationale for this request is that these are actions that are repeated a lot, and writing them once and again ends up being very boring. Also, maybe this approach could encourage users to explore the proof status with more attention (or maybe not).
The text was updated successfully, but these errors were encountered: