-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Recreate structure of documentation #2800
Conversation
51fa5f9
to
dad0f14
Compare
Okay: I think this refactor is ready for review. cc @incanus |
Taking a look now @tmcw.
Ordinary consumers of GL link it into their app as a static library. For development, we actually integrate the source of GL right into the source of the test app, for compilation speediness reasons. More here: https://www.mapbox.com/ios-sdk/#source
I'm running |
I'm not sure about the approach of so many files, particularly |
We should probably bring in Node-specific instructions here as well, as "Linux on Linux" could be desktop, could be Node. /cc @mikemorris |
Otherwise I'm 👍 here @tmcw. |
Node.js docs have lived in https://github.com/mapbox/mapbox-gl-native/blob/master/platform/node/README.md for mostly historical reasons, we should consistify this between platforms - either break all platform implementations into |
@mikemorris are there any instructions for building the node module from source? The instructions in README.md are
Which would install it from npm, right? |
@tmcw |
Okay so this is trying to use "GL" as a stand-in for "the library". I'll improve this sentence. |
I wrote a section for the node.js bindings, documenting |
Better API documentation, for all bindings, should be a second pass. This PR is just reorganizing our current build-stage docs. |
Cleaned up Node.js docs a bit, looks good to me now 👍 |
rebasing into one commit & merging. |
Great work @tmcw. We've gone through some solid iterations of all this mess o' docs and this is the best yet. |
Fixes #2799
Trying to refactor this as much as possible, I'll record quibbles here:
What does this mean? "compiles the source to GL"... does this JIT compile anything, or is it just saying "compiles mapbox-gl-native instead of using a bundle".
This links to a closed ticket that doesn't give a clear answer. Is this statement still true?