yinxianwei / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

dev tool support for webGL debug #104

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
SDK/Debugger version: N.A.
Eclipse version: N.A.
Google Chrome/V8 Embedder + version: Any
[For WebKit (WIP) protocol] Backend version: Any
OS + version: Any

What steps will reproduce the problem?
1. Load a webgl webapp in chrome
2. Open Dev Tools
3. Search for ways to inspect shaders

What is the expected result?
Browser debugging support to allow me inspect, trace, snapshot, debug the gl 
app. It would provide insights into the shader language, openGL traces, similar 
to what we have for javascript/css debugging in devtool. See below section for 
more info.

What happens instead?
There is no way for a developer to debug the shader language.

Please provide any additional information below. If possible, attach a 
(reduced) test-case.
Related to https://code.google.com/p/chromium/issues/detail?id=367739, but we 
want more features:
1.Snapshot of a sequence of frames with gl trace info
2.Allow stepping through shader language
3.Chrome engine trace info similar to the javascript trace feature available in 
latest chrome canary dev tool.

Tools available in firefox today: 
https://developer.mozilla.org/en-US/docs/Tools/Shader_Editor, and 
https://hacks.mozilla.org/2014/03/introducing-the-canvas-debugger-in-firefox-dev
eloper-tools/

Tool available in android today: 
http://developer.android.com/tools/help/gltracer.html

Today people use webgl-inspector(http://benvanik.github.io/WebGL-Inspector/) on 
Chrome to debug webGL apps. But there is limitations, i.e. it doesn’t support 
live edit of the shader languge; it cannot capture a sequence of frames; it 
doesn’t show the real openGL calls resulted from the webgl code; it doesn’t 
support stepping through the shader language.

Original issue reported on code.google.com by ni...@amazon.com on 17 Dec 2014 at 11:37

GoogleCodeExporter commented 8 years ago
Wrong project. This one is about the Chrome DevTools for Java, which is no 
longer maintained. Please file a bug against built-in devtools at 
http://crbug.com/new.

Original comment by apav...@chromium.org on 18 Dec 2014 at 7:48

GoogleCodeExporter commented 8 years ago
Thanks for your update. I have moved the issue to 
https://code.google.com/p/chromium/issues/detail?id=443670

Original comment by ni...@amazon.com on 18 Dec 2014 at 6:59