xxfxxf / chromiumembedded

Automatically exported from code.google.com/p/chromiumembedded
0 stars 0 forks source link

Suggestion - allow using custom DevTools #390

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,

I want to modify the DevTools (to use larger fonts, for example), but in the 
new versions of CEF, the DevTools source files are packed in unknown .pak 
format.

How do I do that? Maybe provide a mechanism to use my custom DevTools? Or even 
better, you can point me to somewhere I can find a tool to generate the 
chrome.pak file from the source files extracted from devtools_frontend.zip 
which can be downloaded from the chromium project site. Thanks.

Original issue reported on code.google.com by edwin....@innovationgear.com on 26 Oct 2011 at 7:39

GoogleCodeExporter commented 9 years ago
You can use CefRegisterSchemeHandlerFactory() to override the internal handler 
for the chrome-devtools scheme and provide your own implementation that reads 
devtools resources from, for example, a folder on disk.

Original comment by magreenb...@gmail.com on 31 Oct 2011 at 5:27

GoogleCodeExporter commented 9 years ago
Thanks! That's good!

Original comment by MindVisualizer@gmail.com on 1 Nov 2011 at 7:19

GoogleCodeExporter commented 9 years ago
See the docs at: http://www.chromium.org/devtools

6. Run your back-end copy of Chrome with command line flag 
--debug-devtools-frontend=<full path to your unzipped devtools-frontend>.

Original comment by loi...@chromium.org on 1 Nov 2011 at 9:56

GoogleCodeExporter commented 9 years ago
I'm afraid cef doesn't have a mechanism similar to Chrome's command line 
parameter --debug-devtools-frontent?

Original comment by edwin....@innovationgear.com on 1 Nov 2011 at 10:10