>JSHint reports ... I created these way back when. The idea is to create debuggable cat'd files, using the typical eval() with //@sourceURL hack, so you can see the individual files in the debugger.
This didn't make much sense until iOS 6, on actual devices (but worked with desktops, most of the time). I believe I've tested these on iOS 6, so you load the big wad cordova.js, but see individual files in the debugger. Neat. But not sure it's worth it. Perhaps comment out the bits in the build, so we don't build them, but we know how to later if we need to. On Fri, Feb 8, 2013 at 6:21 PM, Filip Maj <[email protected]> wrote: > For initialization debugging methinks > > On 2/8/13 3:13 PM, "Jesse" <[email protected]> wrote: > > >Can someone explain the use/purpose of the generated > >pkg/debug/cordova.***-debug.js ? > >JSHint reports they are just large collections of bad-escapements ... are > >these still used for something? > > > >-- > >@purplecabbage > >risingj.com > > -- Patrick Mueller http://muellerware.org
