JP Simard

Results 706 comments of JP Simard

No progress to report. One way to improve performance _might_ be to avoid ruby when generating the Mustache templates or Markdown. Then again, these libraries are broadly used and have...

I agree, we should make that work. The reason it doesn't today is that we replace `@note` to `- note:` and treat it as a Markdown list to combine our...

This has two implications: ## 1. Per module ![image](https://cloud.githubusercontent.com/assets/474794/4870572/fdb18436-6171-11e4-883f-ff5ea02466a6.png) ## 2. Per token ![image](https://cloud.githubusercontent.com/assets/474794/4870573/198ac622-6172-11e4-97e2-4047025ae3d7.png)

No one's done any work on this as far as I can tell.

Still needs to be done.

Awwww, thanks 😍. This makes my day x 💯 . I'd close this as "won't fix" but that'd just be a shame.

Ideally, you'd only ever need a single set of output documentation, which would indicate which parts are available under which conditions (e.g. platforms & versions).

By the way, generating docs with `--podspec` will generate them for all supported platforms and merge them together, which is what you see on http://cocoadocs.org.