This document discusses using CocoaPods to manage development pods for iOS projects. It recommends putting source code in a Classes folder within the pod and resources like images in an Assets folder. Developers should avoid merging xcodeproj, xib, and storyboard files by maintaining their own copies. CocoaPods generates a xcworkspace file that locates bundled resources using the PodAsset library. This allows adding new files without merging the xcodeproj and cleaning the git repository of merges.
15. Let CocoaPods manage files
• Don’t use xcodeproj
• Use xcworkspace instead
• don’t commit xcworkspace
• put it in .gitignore
• Put files in development pods
• New files will be added to xcworkspace
• run pod install when files are added or removed
• don’t have to run pod install for file editing
• Regenerate xcworkspace after each pull
• by running pod install again
29. Other resources
• You can use the same method
to load
• json
• storyboard
• xib
• Check readme
• https://github.com/
haifengkao/PodAsset
• Send you pull requests!
31. Summary
• Avoid merge xcodeproj
• put files in Classes folder
• Avoid merge xib and storyboard
• each dev maintains his own storyboard files
• put resources in Assets folder
32. Q&A
• You can mix swift and objc in the same pod
• The pod is local (development pod)
• you don’t have to publish it to the Internet
• This method didn’t cover test case management
• yes, you still need to merge xcodeproj if you add new
test cases
• There are other options: use frameworks instead of pods