Being a big fan of avoiding dependency hell wherever possible, I was overjoyed to discover CocoaPods. CocoaPods is a dependency manager for Cocoa projects. Instead of manually downloading and adding frameworks and components to a Cocoa project, CocoaPods does it for you.
Specify the libraries for your project in an easy to edit text file. Then use CocoaPods to resolve all dependencies, fetch the source, and set up your Xcode workspace.
To use ACEView with CocoaPods, add it to your project’s pod file, follow the instructions for adding a pod to your project on the CocoaPods site.
As a step on the journey towards becoming a first-class Cocoa citizen, ACEView has attained its very own documentation!
I’ve documented the publicly-accessible classes as best I can, using the wonderful appledoc tool. One may view the ACEView documentation online, in the relevant header files, or build it for use within Xcode. If ACEView is included via CocoaPods and appledoc is installed, the documentation will be generated automatically!
I wanted to use Connection Kit for my current project, but ran into issues as it requires a few other frameworks to function. Many months ago I worked around this by copying the internal framework’s source files directly into Connection Kit.
Everything went well until I updated Connection Kit. Suddenly it required more internal frameworks, and copying their source became impractical.