p5-serial.github.io

About

This repository is part of the p5-serial project, created in 2015 at New York University's Interactive Telecommunications Program by Shawn van Every, Jen Kagan, and Tom Igoe.

This project is a beginner-friendly library for adding serial communication capabilities to projects using p5.js, that can run on any modern browser.

Similar projects with different scopes and strategies include p5.webserial.js and p5.web-serial.

For a list of more p5.js libraries please visit https://p5js.org/libraries/.

Structure

The p5-serial project's repositories are part of the GitHub organization at https://github.com/p5-serial, which includes these 3 active repositories:

• https://github.com/p5-serial/p5.serialserver: a server side library.
• https://github.com/p5-serial/p5.serialport: a client side library.
• https://github.com/p5-serial/p5-serial.github.io: this repository, with info about the contributions, articles, and an overview of the project.

Additionally, these are currently archived repositories:

• https://github.com/p5-serial/p5.serialcontrol: a desktop app that runs a p5.serialserver for use with a p5.serialport client, built with Electron.

Grants awarded

This project has been supported by the following grants:

• 2019 Google Summer of Code, grant awarded to Jiwon Shin and mentored by Shawn van Every, summary here
• 2022 Processing Fellowship, grant awarded to Aarón Montoya-Moraga and mentored by Shawn van Every, summary here

Contributors ✨

Thanks goes to these wonderful people (emoji key):

Shawn Van Every 💻	Jen Kagan 💻	Tom Igoe 💻	Jiwon Shin 💻	Wenqi Li 💻	aarón montoya-moraga 💻	Lisa Jamhoury 💻
Lachlan Campbell 💻

Contributing

This project follows the all-contributors specification. Contributions of any kind welcome!

If you find a problem or want to propose an addition in any of our repositories, we ask you to please create an issue on the corresponding repository, following these guidelines:

• Specifiy the serial device, computer, operating system you are using.
• Specify the versions of the software you are using.
• Include any other relevant info you think is important.

If you want to work on an existing issue, we welcome pull requests!