Thread on the intent to deprecate Debug Console: http://apache.markmail.org/thread/nipqmsmq5ucryxrn
Another issue, which explains why Debug Console is still there: https://issues.apache.org/jira/browse/CB-623 On Wed, Aug 1, 2012 at 12:49 PM, Jesse <purplecabb...@gmail.com> wrote: > I would like to clean up the numerous issues around console logging. > > Some Jira issues related to console.log [0][1][2][3] > > iOS requires it's own custom js because it registers the plugin as 'Debug > Console' [4] > iOS specific js has a bunch of extra cruft for stringify'n objects passed > to it, and pretty printing. > iOS has multiple LogLevels that determine which messages actually make it > through. > > WP7, Win8Metro have what I consider to be a clean, only when required > implementation in js that we should mimic on other devices. [5] > ( as a replacement/shim for non-existent console.log platforms. ) > > cordova-js common also has a logger plugin which has much of the same > functionality. [6] > However, it is not completely clear how dependencies are resolved between > the existence of console.log and logger.logLevel > > > [0] https://issues.apache.org/jira/browse/CB-617 > [1] https://issues.apache.org/jira/browse/CB-618 > [2] https://issues.apache.org/jira/browse/CB-619 > [3] https://issues.apache.org/jira/browse/CB-611 > [4] > https://github.com/apache/incubator-cordova-js/blob/master/lib/ios/plugin/ios/console.js > [5] > https://github.com/purplecabbage/incubator-cordova-js/blob/master/lib/win8metro/plugin/win8metro/console.js > [6] > https://github.com/purplecabbage/incubator-cordova-js/blob/master/lib/common/plugin/logger.js > > > > -- > @purplecabbage > risingj.com
