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
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) ?
The text was updated successfully, but these errors were encountered:
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:
The client need to:
Other pending questions:
Do we want JS or not at all ?
How do we want to handle UI interactions (like animations) ?
The text was updated successfully, but these errors were encountered: