Open petetronic opened 10 months ago
Draft UI treatments that demonstrate new controls, each control should be broken down into individual issues and their behavior and look and feel needs to be finalized.
Draft UI treatment of a Quarto extension example:
For now we'll leave the existing VSCode menu editor/title/run contribution as is, and focus on the new capabilities we require first.
This can be broken down into a few different areas, which I can create issues for
New editor menu action item types (UI components):
New extension API for adding the above action item types from an extension
Creating a new location for these editor action items, within the editor breadcrumbs bar
That's look amazing. I hope the feature will be soon considered to add for Positron
We want to add a new customizable toolbar or "action bar" to an Editor, likely best positioned to the right on the same line as the breadcrumb below the tabs.
Given extensions will have requirements to add interactive controls, modify visual state and register event handlers, we expect this will require a new programmatic API (beyond simple contributions that you may see in package.json).
An early use of this capability will be to improve the user experience in Quarto to expose common preview and rendering commands to the end user, similar to the easy access provided for these functions in RStudio today.
The initial set of controls will need to include:
Extensions may also need to customize the state of these controls based on information in the file being edited.