Shoot, sorry I missed that. It's used, so we keep it!
On Tue, Aug 6, 2013 at 8:10 PM, Jesse MacFadyen <[email protected]>wrote: > Windows phone does. Unless we can agree on guaranteed channel order of > firing on startup, I still need this. > > Sent from my iPhone > > > On Aug 6, 2013, at 5:08 PM, Gord Tanner <[email protected]> wrote: > > > > That channel used to be there for any platforms that needed some time to > warm up after the web view was initialized. > > > > I don't think any platforms require this anymore so I am ok with > removing it as well. > > > > Sent from my iPhone > > > >> On 2013-08-06, at 5:37 PM, Jesse <[email protected]> wrote: > >> > >> WP code: > >> > >> string nativeReady = "(function(){ > >> cordova.require('cordova/channel').onNativeReady.fire()})();"; > >> > >> @purplecabbage > >> risingj.com > >> > >> > >>> On Tue, Aug 6, 2013 at 1:45 PM, Ian Clelland <[email protected]> > wrote: > >>> > >>> I think that's a good idea. If there are no platforms actually using > this > >>> signal to indicate anything useful, then nobody should be listening > for it > >>> to fire. > >>> > >>> Deleting it now means that nobody ends up in a situation where they're > >>> implicitly depending on a feature that we don't support, don't test, > and > >>> which will probably break in the future without anyone noticing. > >>> > >>> > >>> On Tue, Aug 6, 2013 at 4:21 PM, Andrew Grieve <[email protected]> > >>> wrote: > >>> > >>>> All of the JS platforms fire onNativeReady in their platform.bootstrap > >>>> function (used to be bootstrap-$platform.js). > >>>> > >>>> Might as well just delete this channel, yes? > >>> >
