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

RFC docset has no title and icon #186

Closed
cweiske opened this issue Aug 5, 2014 · 4 comments
Closed

RFC docset has no title and icon #186

cweiske opened this issue Aug 5, 2014 · 4 comments

Comments

@cweiske
Copy link

cweiske commented Aug 5, 2014

Installing the RFC docset from https://willnorris.com/2014/03/rfcs-for-dash-app via options -> docsets -> add feed dash-feed://https%3A%2F%2Fraw.githubusercontent.com%2Fwillnorris%2Frfcdash%2Fmaster%2FRFCs.xml gives me the guid as docset name: e61c42d8-eea9-11.....

This uuid is shown in the tree view docset list and the docset list in the options.
Also, there is no tree and no icon shown.

@k3rni
Copy link

k3rni commented Sep 25, 2014

On recent Zeal (after #190 was merged), the title does show. As for the icon:

put a favicon.ico or icon.png file into a docset's Contents/Resources/Documents directory. Restart Zeal and now it does show. Maybe create an issue on willnorris/rfcdash for that, it already has a suitable icon in tools.ietf.org/images.

@willnorris
Copy link

I'm finally getting around to fixing this upstream. Does zeal really require that the icon be in the Contents/Resources/Documents directory? According to Dash's docs, it expects it to be in <docset name>.docset/icon.png. It'd be great if zeal could just read it from there as well.

Also, what size does zeal expect it to be? Judging by b4fcfb7, I'm guessing 32px? (which would be consistent with Dash also)

@trollixx
Copy link
Member

@willnorris Zeal expects 16x16 icon in icon.png and 32x32 in icon@2x.png for high resolution screens. That should be consistent with Dash.

@lock
Copy link

lock bot commented Sep 16, 2018

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 Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

5 participants