Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

V8net #16

Merged
merged 12 commits into from
Jan 17, 2018
Merged

V8net #16

merged 12 commits into from
Jan 17, 2018

Conversation

threepistons
Copy link

@threepistons threepistons commented Jan 17, 2018

Addresses sudo dependency and dependency on "pi" user, to more gracefully handle multi-user environments. See #15.

Briefly:

  • Scratch GPIO now works without sudo.
  • Scratch GPIO tidies up the GPIO handler on exit.
  • Sample projects are with the rest of the package and are copied to the user's home folder on launch.
  • A Pibrella test program is the default sample project.
  • The installer doesn't need the pi user account to exist.
  • The build can be done no matter where the repo is.
  • I removed the desktop icons as I could not figure out how to make them for all users, they are now in the menu for all users.
  • The package is installed into /opt.
  • The Scratch GPIO Plus icon and launcher are no longer created as I couldn't see how they differed from the Scratch GPIO icon and launcher.

@cymplecy cymplecy merged commit 82ad2bb into cymplecy:v8net Jan 17, 2018
@cymplecy
Copy link
Owner

cymplecy commented Jan 17, 2018

[edit] Note: Users should run ScratchGPIOPlus versions when working with addon boards. The basic version sets 11,12,13,15,16,18 as outputs and most of the other pins as inputs (with pull-ups) - this is useful if jsut using breadboards (as we did in the initial days) The plus version doesn't default any pins to any state and is the one to be used when using addon boards.

@cymplecy
Copy link
Owner

On pedagogical grounds - I don't think including a full working example of a Pibrella on launch of the program is a good idea - it sort of defeats the point of learning how to do something :)

@threepistons
Copy link
Author

Users should run ScratchGPIOPlus versions when working with addon boards.

Ah, I didn't know about the pullups. I didn't notice any problems with the Pibrella without them. I can reinstate the commented-out blocks.

On pedagogical grounds - I don't think including a full working example of a Pibrella on launch of the program is a good idea - it sort of defeats the point of learning how to do something :)

I discussed this with the class leader. He took the view that having the Pibrella test sample launching on default was useful as it allows the supervisors to easily check the Pibrella's functioning prior to letting the students loose, and he showed me that dragging the code blocks to the left would delete them. Perhaps this is something that I should do locally in post-install, as I can see that it would be counter-productive in other cases.

@threepistons
Copy link
Author

The first Pibrella session this morning "all went perfectly" according to the class leader. Thank you so much for your help.

@cymplecy
Copy link
Owner

cymplecy commented Jan 19, 2018 via email

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants