Re: Looking at moving part of our iOS app become an iOS framework to be used in other apps.

On Jan 15, 2016, at 4:56 PM, Jens Alfke wrote: > >> On Jan 15, 2016, at 1:31 PM, Alex Zavatone wrote: >> >> However, a good amount of app startup and config is triggered in the >> appDelegate, same as push notification, opening the app via URLs and other >> appDelegate related tasks would c

Re: Looking at moving part of our iOS app become an iOS framework to be used in other apps.

> On Jan 15, 2016, at 1:31 PM, Alex Zavatone wrote: > > However, a good amount of app startup and config is triggered in the > appDelegate, same as push notification, opening the app via URLs and other > appDelegate related tasks would conflict with the appDelegate of the app > using the fram

Re: Looking at moving part of our iOS app become an iOS framework to be used in other apps.

I created a singleton called “” that I moved all of that to. That way even my windows, my logging, my push, everything that is shared between my OS X and iOS code and extensions would use that instead of the App Delegate. With that in place, very little if anything calls the app delegate anymore

Looking at moving part of our iOS app become an iOS framework to be used in other apps.

And this framework would be utilized by other applications. However, a good amount of app startup and config is triggered in the appDelegate, same as push notification, opening the app via URLs and other appDelegate related tasks would conflict with the appDelegate of the app using the framewor