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

IO: PR #4297, plus Fritzing drawings #4298

Merged
merged 2 commits into from Feb 14, 2016

Conversation

Projects
None yet
2 participants
@gohai
Contributor

gohai commented Feb 14, 2016

They are about 190kb each. I think documenting the hardware-aspect in such a visual way, close to the sketch (which then also includes the link to the datasheet) is a nice touch, but I am biased :)

gohai added some commits Feb 14, 2016

IO: Use GPIO numbers in examples
Even the Raspberry Pi Foundation used GPIO numbers over (congruous) physical pin numbers:
https://www.raspberrypi.org/learning/introduction-to-processing/worksheet-2/

Switch our examples as well, so that it they're more clear and hardware-agnostic.

benfry added a commit that referenced this pull request Feb 14, 2016

@benfry benfry merged commit 4ebc40c into processing:master Feb 14, 2016

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Feb 14, 2016

Member

I think that's fine. For future use, I recommend using optipng -o7 to make 'em as small as possible. But it doesn't make sense to do that now—we'd save 20% on the current size, while adding 80% of the image size to the repo (since the old files will still be part of the history).

Member

benfry commented Feb 14, 2016

I think that's fine. For future use, I recommend using optipng -o7 to make 'em as small as possible. But it doesn't make sense to do that now—we'd save 20% on the current size, while adding 80% of the image size to the repo (since the old files will still be part of the history).

@gohai gohai deleted the gohai:io-updates-with-imgs branch Feb 14, 2016

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