-
Notifications
You must be signed in to change notification settings - Fork 15
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
Improve the Tree-Sitter inspector #62
Comments
Here is a proposal:
This is completely removing the current dialog, but better integrate TreeSitter into Knut. |
Sounds good overall. The inspector could definitely use some love. It's been working fine but it's UX isn't great right now. Side Note: .scm stands for scheme. Tree-sitter doesn't actually use scheme syntax, but it's close enough that highlighting, etc. should work fine. |
It does, and it's already in Knut... we should definitely try that before doing our own... |
The right view shows the TreeSitter tree, like in the inspector view. Related-to KDAB#62
The button will display the treeSitter inspector dialog. Related-to KDAB#62
The button will display the treeSitter inspector dialog. Related-to #62
This uses KSyntaxHighlighting::SyntaxHighlighter to enable a scheme-based syntax highlighting on the TreeSitterInspector. This still has a few issues, as e.g. #eq? produces a strange highlighting result and certain keywords are marked up without reason. But it's still a good improvement from no syntax highlighting. Part of KDAB#62.
This uses KSyntaxHighlighting::SyntaxHighlighter to enable a scheme-based syntax highlighting on the TreeSitterInspector. This still has a few issues, as e.g. #eq? produces a strange highlighting result and certain keywords are marked up without reason. But it's still a good improvement from no syntax highlighting. Part of #62.
This should make it more convenient to design queries and store them for later reuse. Fix KDAB#62
This should make it more convenient to design queries and store them for later reuse. Fix KDAB#62
More discussion, quite some changes as we did a 180° turn.
The text was updated successfully, but these errors were encountered: