> On Feb 26, 2016, at 5:25 PM, Alex Zavatone <z...@mac.com> wrote: > > Yeah, I remember someone (was it you?) asking about a guide for writing > frameworks a while ago.
Oh, I’ve got tons of experience building frameworks! But it’s still a never-ending source of frustration. (Just today we found that our iOS framework ends up lacking bitcode, causing errors for devs trying to submit their apps…) > Tell you what, I have to mess with trying to package up the storyboards and > images and see how I can use those to encapsulate a storyboard and classes > that will serve as the UI launching point for a proof of principle module. I don’t know what these “storyboard” or “image” things are … I haven’t dealt with any UI-level stuff in years, feels like :-p Just getting the code together is troublesome enough. Srsly, you’re talking about a dynamic framework, right? Static frameworks (on iOS) are barely supported and Xcode doesn’t know anything about resources in them; the app developer has to write a custom build step to copy those into the app bundle. —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
