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've been traveling a lot lately and have wished there was a good way to get Particle's docs in an offline format. I use Dash on a Mac and LovelyDocs on Android (which uses the same file format as Dash) for viewing documentation for other projects/languages/frameworks offline.
It'd be rad if someone would create a Particle API docset for Dash and submit it to their contrib directory. It shouldn't be too hard for an MVP/POC, but it also probably wouldn't be trivial to make it be up to Particle's high standards.
Dash has some docs here on how to generate a docset and there's a 3rd party tool called Dashing that might simplify some things. (I tried it late last night on a whim, but ran into npm install issues that I didn't have time to sort out.)
I'll also request the Dash team create it as an officially-supported docset, but I figured I'd ping both groups.
The text was updated successfully, but these errors were encountered:
I've been traveling a lot lately and have wished there was a good way to get Particle's docs in an offline format. I use Dash on a Mac and LovelyDocs on Android (which uses the same file format as Dash) for viewing documentation for other projects/languages/frameworks offline.
It'd be rad if someone would create a Particle API docset for Dash and submit it to their contrib directory. It shouldn't be too hard for an MVP/POC, but it also probably wouldn't be trivial to make it be up to Particle's high standards.
Dash has some docs here on how to generate a docset and there's a 3rd party tool called Dashing that might simplify some things. (I tried it late last night on a whim, but ran into
npm install
issues that I didn't have time to sort out.)I'll also request the Dash team create it as an officially-supported docset, but I figured I'd ping both groups.
The text was updated successfully, but these errors were encountered: