incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Sims (JIRA)" <>
Subject [jira] [Commented] (CB-612) Add support for native remoteInspector logging
Date Wed, 30 May 2012 10:02:23 GMT


Steve Sims commented on CB-612:

I'd love to be able to see console.log (plus console.error and console.warn) message coming
out of the webkit remoteInspector.

My typical console.log calls are often something like this:
console.log("Current state is %o", stateObject);

Inside the webkit inspector the stateObject would be interpolated into the console output.
 Such log messages through Cordova's logging just end up being "Current state is %o", which
are fairly useless.

Unfortunately weinre isn't a good alternative to the inbuilt remote inspector for my needs
because all my JS code uses ES5 strict-mode, which weinre isn't compatible with.

At the simplest level, it would be nice to just have a way to disable cordova's console.log
> Add support for native remoteInspector logging
> ----------------------------------------------
>                 Key: CB-612
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Sub-task
>          Components: iOS
>            Reporter: Olivier Louvignes
>            Assignee: Patrick Mueller
>              Labels: debugging, ios
> Currently, when using the awesome remote debugger provided by apple (connecting on localhost:9999
with safari) with :
> // enable remote debugging
> [NSClassFromString(@"WebView") _enableRemoteInspector];
> #endif
> I do not get any console log/warn/error output. I guess it is caused by the Xcode logging
> The remote webinspector is really superior to Weinre currently as it does provide realtime
dom inspection (weinre only displays initial dom, not what was built by Sencha Touch for instance).
> Also I've seen that you have made some progress on error tracing (CB-535), this would
be also awesome as it is a really major issue. Since playing with api's that can't be debugged
via a desktop Webkit is a real nightmare today.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message