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

There is no ios(objective-c) docsets? #680

Closed
1987skywalker opened this issue Jan 10, 2017 · 14 comments
Closed

There is no ios(objective-c) docsets? #680

1987skywalker opened this issue Jan 10, 2017 · 14 comments

Comments

@1987skywalker
Copy link

I can't find it in zeal. Can I download it and add it to zeal manually?
https://developer.apple.com/library/downloads/docset-index.dvtdownloadableindex

@OKNoah
Copy link

OKNoah commented Jan 13, 2017

I was going to say it might be because Apple distributes their documentation right in the OS help files, but looks like you do have some kind of link to them. Dash also asked you to install Xcode and install the docs on the system to get the docs in the app (it just looked in the system folders for them rather than download again).

@trollixx
Copy link
Member

trollixx commented Jan 25, 2017

We neither support any Apple's docsets, and nor running on macOS. No changes about that in the observable future.

@RJVB
Copy link

RJVB commented Feb 17, 2017

Zeal runs just fine on OS X (dunno about macOS, aka 10.12+ O:-) )

https://github.com/RJVB/macstrop/tree/master/devel/zeal

@trollixx
Copy link
Member

@RJVB And looks super ugly :)

Anyway, while supporting different documentation formats is interesting, I doubt we'd ever get into Apple's proprietary stuff. There are just too many other things to do.

I'll leave this issue open for a bit, just a reminder for myself to create a wiki page on different formats.

@RJVB
Copy link

RJVB commented Feb 25, 2017

@trollix: super ugly? When code uses only Qt's standard choices for font and widget sizes the result will never look good anywhere, but will always remain some kind of lowest common denominator. This is worse on Mac than elsewhere because you end up with the huge default system font in more places than you should, but the Macintosh widget style also uses too much spacing.
I don't mind, I have KF5 installed properly and use a personal QtCurve theme. With that Qt applications look as good on Linux as they do on Mac O:-)

@RJVB
Copy link

RJVB commented Feb 25, 2017 via email

@tomaspinho
Copy link

tomaspinho commented Mar 1, 2017

I've spent 2 evenings (not a C/C++/QT dev) trying to build Zeal on macOS (Sierra, 10.12), and managed to do it. I updated the instructions for homebrew on the relevant pages in the wiki. 😄

I was just wondering if choosing to not support OSX is out of respect for Kapeli, due to the explicit usage of their docsets, or if it is for some other reason, technical or otherwise (OS fanboyism 😛 ).

@trollixx
Copy link
Member

trollixx commented Mar 1, 2017

@tomaspinho Please see #24.

@tomaspinho
Copy link

tomaspinho commented Mar 1, 2017

@trollixx thanks 👍 and sorry for not seeing the link right in the wiki page itself. What about users like me and @RJVB who may be maintaining or publishing their build scripts?

@trollixx
Copy link
Member

trollixx commented Mar 1, 2017

Keep them to yourself :) I think we are fine as long as Zeal stays out of popular software distribution channels like Homebrew.

@trollixx
Copy link
Member

trollixx commented Mar 7, 2017

Copied link to the wiki.

@trollixx trollixx closed this as completed Mar 7, 2017
@RJVB
Copy link

RJVB commented Sep 13, 2018

Because the question came up once more (for me): Objective-C is not an exclusive-to-Apple language. In other words, having a docset for it (just as there's a docset for C and for C++) shouldn't be a problem at all and it should thus be perfectly legitimate to ask for (or provide) such a docset.

@trollixx
Copy link
Member

trollixx commented Sep 13, 2018

@RJVB IIRC on macOS Dash shows docs from XCode, and not its own docsets.

@lock
Copy link

lock bot commented Mar 12, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Mar 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

5 participants