You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I generally browse programming documentation offline, which makes accessing and searching it much more comfortable. I use Dash on macOS and Zeal on Linux. Dash has docsets for many things (including Python, numpy and astropy) but something that's missing so far is the LSST user guide.
Would it be possible to generate an official LSST "docset" for Dash?
Given that the documentation is Sphinx-based, this should be a streamlined/automatable process using the existing doc2dash framework. The steps are all outlined in the Dash Docset Generation Guide.
This would be a great community resource to have!
The text was updated successfully, but these errors were encountered:
As an additional request: it would really be nice to have the Doxygen as a docset too. It's often much more detailed than the Sphinx documentation, and easier to find and browse classes and methods, as well as source code snippets.
We're in the process of sunsetting the Doxygen documentation, so we won't be making a Dash docset of it. The good news is that all the content that was formerly available in Doxygen, including C++ documentation, will be available from the Sphinx documentation once that transition is complete.
I generally browse programming documentation offline, which makes accessing and searching it much more comfortable. I use Dash on macOS and Zeal on Linux. Dash has docsets for many things (including Python, numpy and astropy) but something that's missing so far is the LSST user guide.
Would it be possible to generate an official LSST "docset" for Dash?
Given that the documentation is Sphinx-based, this should be a streamlined/automatable process using the existing doc2dash framework. The steps are all outlined in the Dash Docset Generation Guide.
This would be a great community resource to have!
The text was updated successfully, but these errors were encountered: