3 ms·
AVFoundation is an apple library, which isn't on cocoapods meaning cocoadocs doesn't support it. Apple do their own documentation pretty well and I don't really
by orta 14y ago
AVFoundation is an apple library, which isn't on cocoapods meaning cocoadocs doesn't support it. Apple do their own documentation pretty well and I don't really see a need to duplicate that to be honest.
- 1qaz2wsx3edc 14y agoThey do provide great docs. But if you're solving a find-ability the drop down list could either include those results or provide a redirect. This would just be an easy workflow thing. Also, you're attempting to reflect the rubydocs ecosystem. An ecosystem which includes (core and stdlib) and gems. If you're reflecting that system accurately, you should include apple docs, and pods accordingly. Just my two cents.
- orta 14y agoI agree, I think redirecting to apple's libraries is a great idea! When the grand-parent said a lack of AVFoundation was a problem, I interpreted that as "you should document that" but I think linking to all of Cocoa/UIKit is a real useful feature. Thanks 1qaz2wsx3edc.
- geuis 14y agoAh I see. It wasn't clear (to me at least) that this wasn't meant to be globally inclusive. My initial take was that you were trying to make a better overall docs system for Obj-c. Having links back to the current definitive Apple docs would be great.