On Jun 4, 2016, at 12:44 , Alex Zavatone <z...@mac.com> wrote: > > I'm wondering if (man, I detest the term) method swizzling of the app > delegate would work or possibly modifying the methods of UIApplication at > runtime to pipe the methods to a class in the framework? > > Initially, i'm going to add them to the UIApplication but I'd like to have a > nice little self enclosed framework that is able to handle them.
So, in effect you want to perform a code injection attack on the app which you don’t control? Why not provide some initialization methods for the framework that are given the results of those delegate methods. That way you are being an honest citizen, because it’s explicit what functionality the framework is designed to control. It imposes the need for a few lines of glue code in the app delegate, but if that code doesn’t do it, it’s not your fault. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
