-
Notifications
You must be signed in to change notification settings - Fork 72
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
[VsCoq1] Added a rudimentary message panel #320
Conversation
Thank you for the comment. Yes, it seems that the existing message panels in the For the combined view, I suppose it can be achieved by somehow relaying all output messages to the new message panel. For example, relaying all messages originally shown in the Or, add more panels beside the |
Some update:
I did some simple local testing and it seems to work fine. Example: |
I'm sorry I haven't had time to take a look, but I remember talking with @MSoegtropIMC (and others) about how the dialog should best work? We should also assign somebody to review the code a bit — @thery, @huynhtrankhanh, do you think you could do that at some point, or would know who could? Without an expert reviewer, we should be willing to merge this after some testing. |
@zqy1018 BTW, do you have a fix for the conflict? If you haven't yet, we should probably test and review your branch. |
Conflict fixed. Now each query result will be either displayed as hovering text (due to the newly added hovering provider) or sent to the message panel. @Blaisorblade I found this Topic on Zulip to which I suppose you are referring. In summary, maybe the following features are desirable:
|
Great sleuthing, that's the thread :-) |
I can help implement this. You could focus on improving other aspects of the PR. This is important work as this PR vastly improves the user experience of VsCoq. |
I've experimented with this a bit and do indeed find it fairly useful !
|
Wait. https://github.com/microsoft/vscode-webview-ui-toolkit/blob/main/src/divider/README.md There must be a good reason behind this rule. Right now, we are abusing the divider to split the proof view into two pseudoviews. And if the official documentation says we shouldn't, maybe this means we are supposed to create a new webview for this. And thus we won't need to implement resizing ourselves. Well, it's not like implementing resizing ourselves is very hard to do, but the question is whether this is the right course of action. Right now, this is a cute prototype, but we need careful consideration. |
what is the status of this PR? |
Sorry, I have not been able to work on the pull request since I started grad school, and my current circumstances may prevent me from picking it up in the near future. 😢 I would greatly appreciate it if someone could take it forward! |
I'm closing this PR since vscoq has now its own repository: https://github.com/coq-community/vscoq-legacy |
Tried implementing a rudimentary message panel in the fashion of that in CoqIDE. Also including some modifications on the displaying style (see
html_views/src/goals/proof-view.css
).Screenshots:
Features:
client/src/HtmlCoqView.ts
)Some known issues:
Coq: Search
(possibly can be resolved by adding more panels and substituting them for the output channels)Technical details:
vscode-panel-view
showing messages (fromvscode-webview-ui-toolkit
) below the proof viewCommandResult
type (see the two changedprotocol.ts
)