Just to be clear: there are costs involved with using the console plugin. Aside from performance, which is likely negligible, it misreports line numbers since the call to the actual native console.log comes from within the plugin's wrapper. If you are using safari remote inspector to debug anyway, where the console plugin doesn't buy you anything, this is just a terrible price to pay.
If the vast majority of ios developers are doing dev for ios 5 or debugging exclusively using console.log and never need remote inspector, then maybe I would see the importance of this here. Perhaps if the plugin was re-written to not clobber by default, or detect when inspector is attached somehow and disable itself automatically, I would be more impressed with seeing this added by default always. As it stands, please don't do this in a way that isn't trivial to disable. -Michal On Wed, Dec 4, 2013 at 11:21 AM, Wargo, John <john.wa...@sap.com> wrote: > I was surprised to see it pulled out into a plugin and I constantly forget > to add it when I'm testing applications. +1 to it being default in the > container. It's default in browser after all. > > John M. Wargo > > > -----Original Message----- > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of > Brian LeRoux > Sent: Wednesday, December 04, 2013 3:21 AM > To: dev@cordova.apache.org > Subject: logger / console.log redux > > We talked a while back about this. I'm wondering if ppl feel its important > to having logging capability as a default installed thing. Also, we > probably would want this available to the CLI workflow somehow. > > I know I find logging helpful for development! > > Thoughts? >
