Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of purplecabbage@gmail.com
 designates 74.125.82.43 as permitted sender)
References: 
 <CACAoQH2E3-ZnRhVJ0QKyi59zSLiB0=gCABDviMY3aNfnQSOGyg@mail.gmail.com>
 <CBC826B6.582F%fil@adobe.com>
 <CAE6O_-YYWoOA=T-7PwMYqUqJpmiY2deCusk8CoEnpTa8nHSc6g@mail.gmail.com>
 <CAP7NMPpGEzzgXZPPE3NOGX30EwUbUZ29tHbPTzdpEUJY=DKYbg@mail.gmail.com>
From: Jesse MacFadyen <purplecabbage@gmail.com>
In-Reply-To: 
 <CAP7NMPpGEzzgXZPPE3NOGX30EwUbUZ29tHbPTzdpEUJY=DKYbg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 3 May 2012 12:02:45 -0700
Message-ID: <-2541470670415484291@unknownmsgid>
Subject: Re: console / logging issues
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

console.assert(this.isCool, "not cool" );

To clarify, I think it's cool!

Cheers,
  Jesse

Sent from my iPhone5

On 2012-05-03, at 11:52 AM, Michael Brooks <michael@michaelbrooks.ca> wrote:

> Nice, thanks for kick starting this one Patrick!
>
> On Thu, May 3, 2012 at 2:29 PM, Shazron <shazron@gmail.com> wrote:
>
>> Thanks for taking this on Patrick!
>>
>> On Thu, May 3, 2012 at 9:12 AM, Filip Maj <fil@adobe.com> wrote:
>>> Cool, thanks for organizing this sensibly Pat!
>>>
>>> On 5/3/12 9:49 AM, "Patrick Mueller" <pmuellr@gmail.com> wrote:
>>>
>>>> I'm going to start in on the console/logger issues:
>>>>
>>>>   console object improvements
>>>>     https://issues.apache.org/jira/browse/CB-348
>>>>
>>>>   Logging levels
>>>>     https://issues.apache.org/jira/browse/CB-611
>>>>
>>>>   Debug Console registers itself with an error-prone name
>>>>     https://issues.apache.org/jira/browse/CB-617
>>>>
>>>>   Support DebugConsole plugin for all platforms
>>>>     https://issues.apache.org/jira/browse/CB-618
>>>>
>>>>   Document how to use logging levels from Debug Console
>>>>     https://issues.apache.org/jira/browse/CB-619
>>>>
>>>>   Logger functionality separated from (debug) console
>>>>     https://issues.apache.org/jira/browse/CB-623
>>>>
>>>> Here's the basic idea:
>>>>
>>>> - create a new module/object exposed on cordova called logger
>>>> - like log4j but smaller/simpler/sensible
>>>> - default implementation in common/logger.js that writes all output via
>>>> console.log()
>>>> - if a platform has something better to implement to, override logger.js
>>>> in
>>>> your platform subdirectory
>>>> - iOS has something better to implement to, so will use that as the first
>>>> 'native logger' implementation, and so the initial take at a Logger
>> plugin
>>>> interface (that other platforms could implement to).
>>>> - intended for use by plugin developers today, maybe we can expose it to
>>>> app developers later
>>>>
>>>> Then there's console.  Not every platform exposes a "global" console
>>>> object.  iOS and at least one of the blackberries.  We should provide an
>>>> implementation which matches the de facto standard Firebug Console API,
>>>> and
>>>> delegates to the logger if it's implemented.
>>>>
>>>> We'd never run into infinite loops with this.  Never. :-)
>>>>
>>>> I'll add some logic to the loggers/consoles so that we can ensure that
>>>> after they've been initialized, that both are not implemented as calling
>>>> into the other.
>>>>
>>>> --
>>>> Patrick Mueller
>>>> http://muellerware.org
>>>
>>