Skip to content
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

LSP/DAP provided UI #397

Open
Kuinox opened this issue Mar 4, 2024 · 0 comments
Open

LSP/DAP provided UI #397

Kuinox opened this issue Mar 4, 2024 · 0 comments

Comments

@Kuinox
Copy link
Member

Kuinox commented Mar 4, 2024

One of the problem the draco project will reach is that there are various IDE/Text Editors (I will bundle "Text Editors with IDE from now on for conciseness), and to add various features, like a debugger view of all the running Tasks in a .NET program, we would need to have specific code for each extensions.

Worse, IDEs rarely have nice API that allows to quickly extend it's UI.

I propose a "shortcut", by moving the UI logic in the common components: the LSP/DAP.

The LSP/DAP would send UI windows defined in HTML/CSS (which is sadly the most supported cross-programs way of displaying things) to the text editor/IDE, and communicate with a IDE specific client.

While this isn't a small task, it will allow to make trivial to add complex windows in the compiler or the debugger.

The server need to:

  • Send a first page, then send updates to that page.

The client need to:

  • Create the window and display the html content
  • Make the window elements somehow interact with the context of the IDE.

Other pending questions:
Do we want JS or not at all ?
How do we want to handle UI interactions (like animations) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant