Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a note about CocoaPods to the README #67

Merged
merged 1 commit into from Mar 29, 2014
Merged

Conversation

clemensg
Copy link

Add a small note about installing hoedown via CocoaPods.

I created the hoedown spec, because I use CocoaPods extensively in my projects and in the past weeks I really fell in love with hoedown, so I had to add it to CocoaPods/Specs ;)

See: https://github.com/CocoaPods/Specs/blob/master/hoedown/2.0.0/hoedown.podspec

Add a note about installing hoedown via CocoaPods.
devinus pushed a commit that referenced this pull request Mar 29, 2014
Add a note about CocoaPods to the README
@devinus devinus merged commit a4a1f64 into hoedown:master Mar 29, 2014
@clemensg
Copy link
Author

Hi, what are your plans on tagging a 3.0 version? For now I have to work with your 2.0.0 tag (can't set the CocoaPods podspec to git master)
Would be great to have a 3.x tag! Best regards, Clemens

@mildsunrise
Copy link
Member

We're looking into it, I'd like to at least do some cleanup and set up a styleguide (#15) before v3.

@clemensg
Copy link
Author

clemensg commented Apr 5, 2014

Ok, in the meantime I will work with the master branch and as soon as you tag a v3 I'll update the CocoaPods spec for hoedown.

Maybe a TODO.md file would be helpful to know what's planned or where others can jump in and help.

Regarding coding style conventions, the tool clang-format helped my team a lot: http://clang.llvm.org/docs/ClangFormat.html
Some styles are built-in (Google, Chromium, Mozilla, etc.) but you can also define your own.

@mildsunrise
Copy link
Member

Maybe a TODO.md file would be helpful to know what's planned or where others can jump in and help.

We need to set up coding style, and do some cleanup according to that. I think that's enough for v3.

Regarding coding style conventions, the tool clang-format helped my team a lot: http://clang.llvm.org/docs/ClangFormat.html
Some styles are built-in (Google, Chromium, Mozilla, etc.) but you can also define your own.

Wow, that's awesome! @devinus we definitively have to look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants