Skip to content

Conversation

@lbrendanl
Copy link
Contributor

Opening this for discussion before continuing to build the samples. A few things to discuss:

  • Do we like the split between Tutorial and Samples?
  • I currently have the library in its own folder at the base of the repo. This means that the developer should run a web server from root as well, rather than directly from the sample folder.

After we get this skeleton in, we can parallelize the sample work. I'll do the four samples in the samples folder, @sdesmond46 you got the tutorial?

@lbrendanl lbrendanl requested a review from sdesmond46 October 2, 2017 17:33
Copy link
Contributor

@sdesmond46 sdesmond46 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it looks good overall. I like the idea of having the tutorial and the samples as separate folders. Would we then just have one more folder for docs?

Follow these instructions to run any of the samples in the Samples directory. The only exception is the React Tutorial, that sample has its own README and setup instructions.

### Pre-requisites
* You must have Node.js or Python installed (or other software which can serve the contents of this folder over http). You can get Node.js from http://nodejs.org and Python from https://www.python.org/downloads/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these links need to be marked as links?

* You must have Node.js or Python installed (or other software which can serve the contents of this folder over http). You can get Node.js from http://nodejs.org and Python from https://www.python.org/downloads/

### Setup
1. Copy the `.trex` files of the sample you wish to run to `~\Documents\My Tableau Repository (Beta)\Extensions` so they are available to Tableau.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think maybe we should just have node / npm be a requirement of our sdk? Then we could just tell people to run things like node start for the test server or node run setup to copy the .trex files to the right place?

I think it might make things simpler in terms of docs and shouldn't be too painful for anyone

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would definitely prefer that. This was just copy paste from existing. The setup idea is really good.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me play around with that and getting existing samples fleshed out.

@lbrendanl lbrendanl merged commit 150f2b8 into dev Oct 2, 2017
@d45
Copy link
Contributor

d45 commented Oct 2, 2017

For GitHub pages, we also have a few other directories at the root level in addition to /docs:
/_includes, /_layouts, and /assets.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants