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

Process explorer: adopt table widget #118407

Closed
bpasero opened this issue Mar 8, 2021 · 7 comments
Closed

Process explorer: adopt table widget #118407

bpasero opened this issue Mar 8, 2021 · 7 comments
Assignees
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code workbench-diagnostics General VS Code built-in diagnostic issues

Comments

@bpasero
Copy link
Member

bpasero commented Mar 8, 2021

I think the process explorer could benefit from the new table widget:

image

//cc @joaomoreno

@bpasero bpasero added the workbench-diagnostics General VS Code built-in diagnostic issues label Mar 8, 2021
@Tyriar
Copy link
Member

Tyriar commented Apr 1, 2021

I'm not sure we actually want to do this since the process explorer is at its core a tree, and even supports collapsing/expanding (as it should) just the twisties are invisible right now.

@bpasero
Copy link
Member Author

bpasero commented Apr 5, 2021

Yeah I was assuming that the tree like behaviour could preserve but a table used on top for the columns. Not sure our new table widget supports this though.

@bpasero
Copy link
Member Author

bpasero commented Apr 8, 2021

My preferred UI to copy from (Chrome Task Manager), really like it:

image

@Tyriar
Copy link
Member

Tyriar commented Apr 8, 2021

Sure, but I'd hate to lose the tree. I was thinking more process explorer with the tree inside the first column:

image

@bpasero
Copy link
Member Author

bpasero commented Apr 8, 2021

Yeah for sure we want to keep the tree, just imagine my screenshot with a tree.

@pixieaka
Copy link

@bpasero @Tyriar See also #120391.

@RMacfarlane RMacfarlane added the feature-request Request for new features or functionality label May 6, 2021
@RMacfarlane RMacfarlane added this to the Backlog milestone May 6, 2021
@RMacfarlane RMacfarlane assigned Tyriar and unassigned RMacfarlane May 13, 2021
@Tyriar Tyriar added the *out-of-scope Posted issue is not in scope of VS Code label Dec 12, 2023
@VSCodeTriageBot
Copy link
Collaborator

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code workbench-diagnostics General VS Code built-in diagnostic issues
Projects
None yet
Development

No branches or pull requests

6 participants