Dark side of Xcode: iOS Framework
4 likes1,090 views
A brief history of the framework for iOS and practical advice on how to create your own native framework for iOS. My talk during Appsterdam TalkLab 03/20/2014
Dark side of Xcode: iOS Framework
- 1. Dark side of Xcode: framework A Rebel solution against the rigidity of Apple (maybe).
- 2. Library Vs Framework a hierarchical directory that encapsulates shared resources, such as a dynamic shared library, nib 鍖les, image 鍖les, localized strings, header 鍖les, and reference documentation in a single package.
- 3. Framework: the only way to distribute (easily) a static library with resources https://developer.apple.com/library/ios/technotes/iOSStaticLibraries/ Introduction.html#//apple_ref/doc/uid/TP40012554-CH1-SW1 https://developer.apple.com/library/ios/documentation/MacOSX/Conceptual/BPFrameworks/ Frameworks.html
- 4. Apple disallowing dynamically linked libraries in iOS and also removed iOS framework template in Xcode
- 5. An open source solution: iOS Universal Framework An Xcode project template
- 7. Embedded Universal Framework Stable version: M7 Remember to refactoring of open source libraries or sources in your framework to avoid con鍖icts with third-part applications.
- 8. A good solution, before Xcode 5.1
- 9. A new open source way: iOS-Framework How to create, develop, and distribute iOS Static Frameworks quickly and ef鍖ciently
- 10. iOS-Framework Fast iterative compilation times Easy distribution and packaging No modi鍖cations to Xcode No trickery with fake bundle targets Works with the latest version of Xcode (5.1)
- 11. How to debug? The only way is to use a project that implement the framework, cause a crash in the project and then put brake points. To debug the framework you need to use it in other application, but break points in the framework code, dosent work.
- 15. Thanks & the Native Side of the Force Be With You Alessio Roberto aka @darthpelo