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

Installing some Dash feeds results in docsets without names #514

Open
k3rni opened this issue Mar 18, 2016 · 6 comments
Open

Installing some Dash feeds results in docsets without names #514

k3rni opened this issue Mar 18, 2016 · 6 comments

Comments

@k3rni
Copy link

k3rni commented Mar 18, 2016

https://gitlab.com/k3rni/pxdoc is a docset for the Phoenix Framework.

When my PR to add it to Dash was rejected, I learned that Dash already has one, but it works only with Dash's special Hexdocs support, and is thus not available for Zeal.

Currently, the CI process on gitlab builds it, and generates a zipfile with build artifacts, which in turn contains Phoenix.tgz, the proper end product.

Works fine when unpacked into Zeal's docset directory (or symlinked into, after building from source). How do I proceed with having it added? Where do I host it properly? I see #315 is still not resolved, and Zeal's documentation on that topic is rather scarce.

@trollixx
Copy link
Member

You could utilise a Dash XML feed for sharing your docset, but other than that there's no way to add new docsets to Zeal.

I am currently working on adding more sources of docsets, that will allow to resolve #315.

For now maybe I should create a wiki page with a list, and point to it from the website...

@k3rni
Copy link
Author

k3rni commented Mar 21, 2016

Added feed and download, hosted on free-tier Heroku: http://pxdoc.herokuapp.com/, original repo also points there. Observations:

  • installing via docset link works, but only via http and not https. In the latter case downloads never finish, and one needs to click Cancel or restart zeal.
  • installed docset has blank title, even though it's set both in meta.json and Info.plist; it unpacks itself to a blank (.docset) directory as well

How do I fix the latter? The former is probably some Heroku issue I can live with.

@trollixx
Copy link
Member

I completely forgot about this one :(

If you are still interested, a quick fix would be renaming feed file to follow <Docset>.xml pattern, e.g. Phoenix.xml. Obviously Zeal should not care how the feed is named, but there's a lot yet to change to make it smart enough for that.

@trollixx trollixx changed the title Phoenix docset. How do I proceed with submitting it? Installing some Dash feeds result in docsets without names Nov 15, 2017
@trollixx trollixx changed the title Installing some Dash feeds result in docsets without names Installing some Dash feeds results in docsets without names Nov 15, 2017
@trollixx trollixx added this to the 1.0.0 milestone Jan 22, 2018
@x-ji
Copy link

x-ji commented Oct 5, 2018

@k3rni Thanks for providing the Phoenix feed, but it doesn't work anymore (HTTPError: HTTP Error 410: Gone). Guess it has something to do with Phoenix changing how their documentation is hosted?

@k3rni
Copy link
Author

k3rni commented Oct 8, 2018

Haven't touched that in a long time. I think the 410 is due to the file disappearing from Heroku itself, but the docs don't build - something must have changed upstream. Will give it a shot.

@malaire
Copy link

malaire commented Oct 5, 2020

Today I noticed that if I add feed using URL https://zealusercontributions.now.sh/api/docsets/Elm it's saved without name as .docset, but if I use URL https://zealusercontributions.now.sh/api/docsets/Elm.xml it's saved correctly as Elm.docset.

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

No branches or pull requests

4 participants