Moving the contents of chrome://gpu Profiling to chrome://tracing.

chrome/browser/resources/tracing.js

+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+<include src="gpu_internals/browser_bridge.js"/>
+<include src="tracing/overlay.js"/>
+<include src="tracing/tracing_controller.js"/>
+<include src="tracing/timeline_model.js"/>
+<include src="tracing/sorted_array_utils.js"/>
+<include src="tracing/timeline.js"/>
+<include src="tracing/timeline_track.js"/>
+<include src="tracing/fast_rect_renderer.js"/>
+<include src="tracing/profiling_view.js"/>
+<include src="tracing/timeline_view.js"/>
+
+var browserBridge;
+var tracingController;
+var profilingView; // made global for debugging purposes only
+
+/**
+ * Main entry point. called once the page has loaded.
+ */
+function onLoad() {
+  browserBridge = new gpu.BrowserBridge();

[nduca, 2011/08/04 00:50:48]

I think we can ditch the browserbridge... or copy the little bit of dependant
browserbridge functionality [which i think is a "debugmode" check] into
tracing_controller.js...

[dominich, 2011/08/04 16:55:28]

TracingController saves the clientInfo and gpuInfo in the trace file so needs
the browserBridge for that.

+  tracingController = new tracing.TracingController();
+
+  profilingView = $('profiling-view');
+  cr.ui.decorate(profilingView, tracing.ProfilingView);
+}
+
+document.addEventListener('DOMContentLoaded', onLoad);