Skip to content

Conversation

@brianignacio5
Copy link
Collaborator

@brianignacio5 brianignacio5 commented May 16, 2025

Description

This PR aims to introduce vscode styles in our web views to match vscode aesthetics by updating webviews style to match vscode settings UI.

project_configuration
newProject1
newProject2
partition-table
app-trace
menuconfig
nvs-partition-table
welcome
size1
size2
cmakelistsEditor

Type of change

  • New feature (non-breaking change which adds functionality)

Steps to test this pull request

Provide a list of steps to test changes in this PR and required output

  1. Click on "ESP-IDF: SDK Configuration Editor" and see the new style. Should resemble more of vscode settings UI.
  2. Execute action.
  3. Observe results.
  4. Repeat for each other feature.
  • Expected behaviour:

  • Expected output:

How has this been tested?

Manual steps above. Changes in this PR are UI so take a look and see if this feel like a vscode UI.

Test Configuration:

  • ESP-IDF Version: Doesn't matter
  • OS (Windows,Linux and macOS): Should be same in all ?

Checklist

  • PR Self Reviewed
  • Applied Code formatting
  • Added Documentation
  • Added Unit Test
  • Verified on all platforms - Windows,Linux and macOS

@brianignacio5 brianignacio5 self-assigned this May 16, 2025
@brianignacio5 brianignacio5 changed the title menuconfig test new vscode tree vscode elements test May 19, 2025
@github-actions
Copy link

github-actions bot commented Jun 4, 2025

Pull request has been marked as stale since there are no activities, and this will be closed in 5 days if there are no further activities

@github-actions github-actions bot added the stale Stale PR or Issue label Jun 4, 2025
@github-actions github-actions bot closed this Jun 9, 2025
@brianignacio5 brianignacio5 reopened this Jun 11, 2025
@brianignacio5 brianignacio5 added ongoing Ongoing Issue or PR, this label will be used for issue or PR which is to be excluded by stale bot and removed stale Stale PR or Issue labels Jun 11, 2025
@github-actions
Copy link

github-actions bot commented Jun 11, 2025

Download the artifacts for this pull request:
You can test these changes by installing this VSIX by click menu View -> Command Palette..., type Install from VSIX and then select downloaded esp-idf-extension.vsix file to install the extension.

@brianignacio5 brianignacio5 force-pushed the enhance/vscode-elements branch from 80147a1 to 27eea99 Compare June 20, 2025 07:36
@brianignacio5 brianignacio5 changed the title vscode elements test Update webviews to vscode style Jun 24, 2025
@brianignacio5 brianignacio5 marked this pull request as ready for review June 25, 2025 02:41
@brianignacio5 brianignacio5 added this to the v1.11.0 milestone Jun 25, 2025
Copy link
Collaborator

@radurentea radurentea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work! It looks much better and I think we can push it as it is.

If we want to spend more time on this UI changes, I do have some feedback for small improvements to make the style identical to vs code's regarding SDKMenuconfig as well as some personal preferences on the "Welcome Page".

Personal Prefferences:

Welcome page:

  • Remove bottom border from header (picture-1)
    picture-1

  • Remove double sidebar (picture-2)
    picture-2

Must based on VS Code style

If we want to copy style from "Preferences: Open Settings (UI)" Vs Code

SDK Config MENU

  • On the left side list of categories (collapsible event should be triggered also on text, currently is just on the icon)
  • Elements on the left side list should not have padding
  • "Replace ESP-IDF and project paths in binaries" option not working
  • Clicking on the categories on the left side list is not accurate, the scroll with have an offset(this will make the category above to be bold)
  • Parent elements on the right menu do not have hover effect. Ex: Enable C++ exceptions (picture-3)
    picture-3
  • Main categories' font should be 26px, sub categories' font 22px, sub-sub categories' 18px. Our subcategories' font is 26px
  • Categories and subcategories should have a padding: 10px 10px 10px 15px. We don't have padding, we have a bottom margin of 0.25em
  • Dropdowns' height should be 26px and inputs' height should be 25px
  • Elements should have margin top or bottom of 9px. We have 0.5em (on .form-group) + [0.75em (.field:not(:last-child)) or +0.5rem (.field)]
  • Search bar should be active when opening the menu
  • Scroll bar has different style from vs codes' which does not have arrows and it's slimmer
  • When scrolling to sdk config editor, main categories, sub-categories and sub-sub-categories should be sticky, just like in the vscode terminal
  • Search bar's height should be 26px
  • Padding inside dropdowns should be 2px (for top and bottom, currently is set to 4px)
  • On the right menu elements, information icon could be vertically centered to be aligned with the text next to it

If you want to make some of these changes, but they are unclear, we can have a quick call.

@brianignacio5 brianignacio5 force-pushed the enhance/vscode-elements branch from aa4e4ad to 999131f Compare July 7, 2025 09:44
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Show examples command was removed correct? Should be removed on the qemu.rst file as well. Note that the "New Project" command should refer to "New Project Wizard".

@Fabricio-ESP Fabricio-ESP self-requested a review July 10, 2025 14:26
Copy link
Collaborator

@Fabricio-ESP Fabricio-ESP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed new deign working as expected. tested on muitliple OS.

@brianignacio5 brianignacio5 merged commit cbf7222 into master Jul 11, 2025
7 checks passed
@brianignacio5 brianignacio5 deleted the enhance/vscode-elements branch July 11, 2025 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ongoing Ongoing Issue or PR, this label will be used for issue or PR which is to be excluded by stale bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants