Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C4EECDE6 for ; Wed, 30 May 2012 17:57:49 +0000 (UTC) Received: (qmail 42053 invoked by uid 500); 30 May 2012 17:57:49 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 41912 invoked by uid 500); 30 May 2012 17:57:49 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 41864 invoked by uid 99); 30 May 2012 17:57:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 17:57:49 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates 64.18.1.208 as permitted sender) Received: from [64.18.1.208] (HELO exprod6og107.obsmtp.com) (64.18.1.208) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2012 17:57:43 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob107.postini.com ([64.18.5.12]) with SMTP ID DSNKT8ZfghwTRggY/EQO7eFr/SaRsM9EzcDK@postini.com; Wed, 30 May 2012 10:57:23 PDT Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q4UHvKX9013875 for ; Wed, 30 May 2012 10:57:21 -0700 (PDT) Received: from nacas01.corp.adobe.com (nacas01.corp.adobe.com [10.8.189.99]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q4UHvKvm010994 for ; Wed, 30 May 2012 10:57:20 -0700 (PDT) Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nacas01.corp.adobe.com ([10.8.189.99]) with mapi; Wed, 30 May 2012 10:57:20 -0700 From: Filip Maj To: "callback-dev@incubator.apache.org" Date: Wed, 30 May 2012 10:57:22 -0700 Subject: Re: cordova.logger Thread-Topic: cordova.logger Thread-Index: Ac0+jafwmdHWzKFSRbuU/oTdRLcf9g== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Just catching up on emails while I was away. Except some threads to be resurrected! Did a scan of our implementations. Other than iOS, WP7 and BlackBerry have native loggers. We should set up issues to get those two platforms using your common logging plugin, Pat. Relevant source code: - Windows Phone 7 [1] - BlackBerry [2] & [3] [1]=20 https://github.com/apache/incubator-cordova-wp7/blob/master/framework/Cordo va/Commands/DebugConsole.cs [2]=20 https://github.com/apache/incubator-cordova-js/blob/master/lib/blackberry/p latform.js#L15-L25 [3]=20 https://github.com/apache/incubator-cordova-blackberry-webworks/blob/master /framework/ext/src/org/apache/cordova/util/Logger.java On 5/21/12 10:05 AM, "Patrick Mueller" wrote: >I've added some doc on the new logger bits to the wiki, here: > > http://wiki.apache.org/cordova/LoggingPlugin > >The relevant issues are grouped under as sub-issues of: > > https://issues.apache.org/jira/browse/CB-348 > >Additional things I plan on doing: > >- deprecating the old iOS Debug Console plugin >- replace usages of the iOS Debug Console plugin with the new Logger >plugin >- remove the iOS Debug Console >- implement a new "console-via-logger" bit of functionality for platforms >that don't have a working console object, but do have a Logger plugin. > Basically, a shim for the Firefox Console API [1] that writes the >messages >via the Logger. > >If any other platforms need a native "logger", or want one, let me know, I >can tell you how to proceed. > >One thing I don't have an answer for is "how can I shim the FireBug >Console >API over an existing console object that only has console.log()" kinda >thing. A lot of the console objects on platforms are lame-ish, and it >would be nice to shim the remaining function over the top. As I start >working on the "console-via-logger" bits, it may become clear to me how we >can do this also. > >[1] http://getfirebug.com/wiki/index.php/Console_API > >--=20 >Patrick Mueller >http://muellerware.org