-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Point and click interface #277
Comments
I am happy consider and merge contributions in this direction, but this is unfortunately out-of-scope for myself to work on |
@joneugster I'm currently working on it but not sure how far I'll get |
Cool! You should consider using the |
@joneugster I was working on another issue and noticed that fixing it on main would probably result in merge conflicts later on. I would like to help as much as I can on getting the dev branch running. If you want to delegate any work just create an issue and tag me in it. I will definitely take a look and see what I can do :) |
@tautastic are you aware of the suggestion widget in Verbose Lean? You can see it in action in some gif in https://github.com/PatrickMassot/verbose-lean4/blob/master/README.md. The context is different, it uses the widget framework, but you could still take inspiration from that. |
@PatrickMassot Wow, this looks awesome, I will definitely check out the library. |
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: