search

catapult-project / catapult

Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..
https://chromium.googlesource.com/catapult
BSD 3-Clause "New" or "Revised" License
1.93k stars 562 forks source link

Edit and annotate traces #2806

Open benshayden opened 8 years ago

benshayden commented 8 years ago

Currently, once a trace is recorded, it is read-only. If you want to draw attention to a part of a trace, then you can either take a screenshot and annotate the screenshot, or try to describe how to zoom into the interesting part. Searching is currently a hit-or-miss experience, but improving it would still leave room for this opportunity.

What if we could manually annotate traces to point out interesting parts? Ideally, metrics could find interesting parts automatically, but they'll never be able to keep up with experts and Chrome's changes. This could look like the old Alerts idea, or a side-panel of text and analysis-links, or something in the top controls bar, for example.

What if we could delete uninteresting events so that it loaded faster and was easier to read? We could finally delete the events caused by clicking away from and back to chrome:tracing, so we could focus on the interesting tab. We could delete the renderers for our Inbox, Docs, and Hangout tabs and stop worrying about leaking product codenames.

Once you finish editing a trace, click the existing Save button, upload it to Drive as usual. If you forget why you saved it, don't try to search your email for a link to it, just open it and click the Annotations side panel.

Would editing traces be useful? Maybe an intern project? :-)

benshayden commented 8 years ago

Wikipedia would be interested in commenting on specific time ranges and slices/events. Maybe surface in the analysis panel? @paulirish https://github.com/ChromeDevTools/timeline-viewer/issues/5