-
Notifications
You must be signed in to change notification settings - Fork 7
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
Location of samples #40
Comments
I'm all for having a curated sub-package of samples/examples within the project itself. I have two main reasons for including them:
|
Both good reasons for within the project itself. |
Do you have some samples you'd like to contribute? If so, I'm sure we'd like to see them. Perhaps you could, in your fork of the repository, put them where you think they should go. |
I'd also vote for |
Have some samples/examples that show how to use the original API in Python 2, will tidy up, PEP8, make Python 2 and 3 etc and add over next few days when get time. Will put in |
Thank you. I look forward to seeing the examples. |
Have added some samples here: The samples were initially used to teach programming using minecraft and the original api, hence the large number of comments. Works with old api and new api at this commit and covers most functions in the old API. There are a couple of examples where commented out sections are there in preparation for block type and color/colour enums which might possibly be added. |
Separating out into separate issue from #10.
Question : Where should sample usage of the API be located?
Option 1: separate folder at top level of project
or Option 2 : within the minecraft folder
or something else?
A teacher/user of the API will want to get quick access to the samples to show how to use the different aspects of the API. Raspbian package in repo would be most common distribution method for most people I would have thought. An alternative might be like the PyGame stuff on the Pi where it is in the Raspbian image already?
The text was updated successfully, but these errors were encountered: