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
The current Show Running Extensions experience lays out a list of running extensions similar to how it is laid out for extensions shown in the side bar. There is left and right-aligned text as well as secondary information for certain extensions. Actions in the top-right include Run code, Save extension host profile (disabled until profiling is finished), Debug extension host, and Start extension host profile.
After you start and then stop the extension host profile, the profile time populates in the list underneath the activation time and the save profile icon is enabled. The saving and viewing experience includes a few steps. The default extension the file is saved as is “.cpuprofile.txt”. If you want to open the file in VS Code to inspect after you save the file, you have to manually change the extension to “.cpuprofile” and open it in VS Code.
Once the file is opened, you can click on the flame view which opens up an additional file that has the same name as the original file opened.
Idea
Show.running.extensions.mov
A proposed change is that we could display the running extensions in a grid. The icons in the top-right corner have also been changed. Debug extension host is using the debug icon rather than the green triangle icon to better differentiate from the Run code icon. I also made a small tweak to the Start extension host profile icon for visual consistency and weight across the icons. There is also no save profile icon because once the profiling is finished, an untitled file could automatically show up in a new tab to view. I was also wondering if we can switch to flame view within the same file rather than opening up another tab for this view. From here, a user could save the file with the extension they prefer.
The text was updated successfully, but these errors were encountered:
On hover ellipsis shown in the first column for context menu.
Info icon and on-hover information for cells with Startup activation within the Activation column
CPU Profile:
Updated layout of information
Included percentage with self and total time
In the video, the text in the time columns are right-aligned. Some other explorations include left-aligning all columns and left-aligning all columns with the highlight. I'm wondering which is the most readable.
Summary of current experience
The current Show Running Extensions experience lays out a list of running extensions similar to how it is laid out for extensions shown in the side bar. There is left and right-aligned text as well as secondary information for certain extensions. Actions in the top-right include Run code, Save extension host profile (disabled until profiling is finished), Debug extension host, and Start extension host profile.
After you start and then stop the extension host profile, the profile time populates in the list underneath the activation time and the save profile icon is enabled. The saving and viewing experience includes a few steps. The default extension the file is saved as is “.cpuprofile.txt”. If you want to open the file in VS Code to inspect after you save the file, you have to manually change the extension to “.cpuprofile” and open it in VS Code.
Once the file is opened, you can click on the flame view which opens up an additional file that has the same name as the original file opened.
Idea
Show.running.extensions.mov
A proposed change is that we could display the running extensions in a grid. The icons in the top-right corner have also been changed. Debug extension host is using the debug icon rather than the green triangle icon to better differentiate from the Run code icon. I also made a small tweak to the Start extension host profile icon for visual consistency and weight across the icons. There is also no save profile icon because once the profiling is finished, an untitled file could automatically show up in a new tab to view. I was also wondering if we can switch to flame view within the same file rather than opening up another tab for this view. From here, a user could save the file with the extension they prefer.
The text was updated successfully, but these errors were encountered: