-
Notifications
You must be signed in to change notification settings - Fork 347
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
feature: UI layout to maximize display of trace events #429
Comments
Hey! Thanks for the comments 😃 Information density is something that comes up a lot and I'm sympathetic to the 'small porthole' effect, it's something we want to improve. Re the specific comments:
|
UI density is also something we'd like very much now that we are embedding the Perfetto trace viewer inside of Flutter DevTools. We have even less vertical space than ui.perfetto.dev since we have headers and footers that belong to the Flutter DevTools web app as well as other content on our performance page. I saw another prototype of embedding Perfetto in an IDE tool window, and I suspect a more dense UI would also be a requirement there. |
There's been a significant increase in density of displaying all the data we do so today but I think more work to be done on showing less data in the first place (and more specific to the problem in the trace). |
In the latest autopush UI, density of information has gone up a lot. We believe this (along with features like track filtering and nested tracks) should make it possible to represent information more compactly than it's possible when this bug was created. Therefore, will be closing this outl. |
When I am using perfetto, I want to devote as much of my screen to the actual tracing events as possible. Today, however, I feel like I am viewing the tracing events through a small porthole because so much of the screen is taken up with other things. A significant portion of the screen is taken up on the top by the overall timeline, and on the left by the thread name. Both are inefficient uses of space. The overall timeline height could be much smaller and still convey the same information (with my data sets, anyway). And the thread name is a huge block of space with very little in it. See attached screenshot.
It would be great if the UI allowed users some control over both of these spaces, i.e., allowed me to grab and drag to adjust the height of the overall timeline, and grab and drag to adjust the width of the box holding the thread name. By allowing users to adjust these layout boundaries, even if these areas are useful for some people in some circumstances, I can minimize them for my purposes.
Minor additional observation, related to this: the "folding" icon that toggles the display of the trace events (the up and down chevrons on the very left side of the attached screenshot, just above where it says "Process 5") takes up display space across the entire width of the screen. The UI would be much better if this icon were not full-screen-width, again allowing more room for trace events to be displayed, and allowing the timestamp display to be closer to the trace events.
The text was updated successfully, but these errors were encountered: