Get console errors

[lodle]

Whats the easiest way to get the errors that would normally print to the console. Im trying to debug a javascript extension and thus cant run the code in a normal browser.

Also is there a way to use or attach the webkit inspector as it would be very handy to use.

'

[magreenblatt]

Whats the easiest way to get the errors that would normally print to the console.

You can create a console application that uses CEF or you can redirect stdout/stderr to somewhere else (to a file, for instance). See http://support.microsoft.com/kb/58667 for details on the latter approach.

Also is there a way to use or attach the webkit inspector as it would be very handy to use.

There is already a thread on this topic. viewtopic.php?f=10&t=69&start=10#p284

Regards,
Marshall

[lodle]

Redirecting stdout and stderr is a very hacky method. As CEF is used as part of a bigger program there should be a nice way to get the console msgs. Also how long is CEF2 going to take to come out? Is it worth submitting patches for things like cookies and useragent?

[magreenblatt]

Redirecting stdout and stderr is a very hacky method.

Not really. It's a standard approach for intercepting messages written to the console in GUI applications. If you disagree with Chromium's use of console messages for debugging purposes then you're welcome to bring up the issue with the Chromium developers on the chromium-dev mailing list.

Also how long is CEF2 going to take to come out?

The initial version of CEF2 is under active development. As with most volunteer projects, it will be available when it is ready.

Is it worth submitting patches for things like cookies and useragent?

I don't know what issues specifically you're referring to, but good patches that improve CEF are and will continue to be welcome. I plan to continue development of CEF for as long as reasonably possible because CEF2 will not be an appropriate replacement for CEF in all use cases.

[lodle]

In regards to the console errors, in most apps its not the only thing writing to stdout/stderr so it would be nice to separate them.

I added an interface to set cookies and also the user agent. Ill make patches and hope to commit them. Is cef2 going to stay private till ready or is there a chance to get beta/dev access to it?

[magreenblatt]

I added an interface to set cookies and also the user agent. Ill make patches and hope to commit them.

Please create issues in the CEF issue tracker and attach your patches there.

Is cef2 going to stay private till ready or is there a chance to get beta/dev access to it?

CEF2 development will become public once the implementation details have settled down and basic functionality is in place. That means, at a minimum, being able to embed the browser window and control navigation. Releasing it sooner would just result in a lot of people building it and wondering why it doesn't do anything .

[lodle]

Added a ticket to issue tracker that allows for host app to get console errors