search

posit-dev / positron

Positron, a next-generation data science IDE
https://positron.posit.co
Other
2.59k stars 79 forks source link

Positron outputs panel is overwhelming to new users #5063

Open jthomasmock opened 1 week ago

jthomasmock commented 1 week ago

System details:

Positron and OS details:

Positron Version: 2024.11.0 (Universal) build 49 Code - OSS Version: 1.93.0 Commit: 10183fa8d9a8495b5d52cafd252cfa5a44b05599 Date: 2024-10-15T02:46:25.482Z Electron: 30.4.0 Chromium: 124.0.6367.243 Node.js: 20.15.1 V8: 12.4.254.20-electron.0 OS: Darwin arm64 24.0.0

Interpreter details:

Describe the issue:

There is a wealth of debugging and logging information in the Output panel, however there is an overwhelming amount of information/options:

Image

Steps to reproduce the issue:

Open the Output panel.

Expected or desired behavior:

We should split up, add context, insert breaks or otherwise guide the user towards the most important processes for debugging. This may be splitting out the Positron-specific outputs into their own section or otherwise guiding the user towards the most useful information.

Were there any error messages in the UI, Output panel, or Developer Tools console?

testlabauto commented 1 week ago

Moving to triage for prioritization.

DavisVaughan commented 4 days ago

I tend to disagree on having a "positron specific" section. I think we have discussed in the past that we should not really be differentiating between vs code features and positron features in this output pane - i.e. they are all positron features!

To that end I think we wanted to put a little more effort towards removing the Positron prefix from a lot of these channel names, I think @juliasilge originally noted this. Instead we'd use the language name as the leading identifier to group things, like R: or R 4.4.1:, kind of like how its mostly done for Python already. Candidates for this are:

jmcphers commented 3 days ago

Ideas from @jthomasmock and others in triage: