| commit | 1aa9ee92f8b413c79fe7d515de1fb94fe277e5f4 | [log] [tgz] |
|---|---|---|
| author | Bjorn Terelius <terelius@webrtc.org> | Tue Jun 11 15:39:38 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Tue Jun 11 16:41:50 2019 |
| tree | 6cba295175d305115bad9b2c3e14f38acf0c2269 | |
| parent | 370f93a34a2b0a3b86edf1d175174111a469e9ed [diff] |
Add string-based IDs for event log visualizer graphs and update command line flags. The IDs be more stable than the plot titles and could be used to identify specific graphs in scripts. Change event_log_visualizer command line interface to control which plots are generated. Old interface had one command line flag per plot as well as a set of 'profiles' that enabled of disabled sets of plots. New interface has a command line flag which takes a string of all the plot names or profiles that should be enabled. In some cases, there are also slight naming changes for the plots. For example, the former command event_log_visualizer --plot_profile=sendside_bwe --plot_incoming_packet_sizes <filename> | python is now event_log_visualizer --plot=sendside_bwe,incoming_packet_sizes <filename> | python The former command event_log_visualizer --plot_profile=none --plot_incoming_packet_sizes <filename> | python is now event_log_visualizer --plot=incoming_packet_sizes <filename> | python The former command event_log_visualizer --plot_profile=all <filename> | python is now event_log_visualizer --plot=all <filename> | python Bug: webrtc:10623 Change-Id: Ife432c1e51edfce64af565a769f1764a16655bb6 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/140886 Reviewed-by: Sebastian Jansson <srte@webrtc.org> Commit-Queue: Björn Terelius <terelius@webrtc.org> Cr-Commit-Position: refs/heads/master@{#28237}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.