├── CONTRIBUTING.md ├── ISSUE_TEMPLATE.md ├── Images ├── Point.png ├── Skeleton_Tracking.png ├── deep.png ├── kinectv1.jpg └── threshold.gif ├── LICENSE.md ├── README.md └── _config.yml /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | When contributing to this repository, please first discuss the change you wish to make via issue, 4 | email, or any other method with the owners of this repository before making a change. 5 | 6 | Please note we have a code of conduct, please follow it in all your interactions with the project. 7 | 8 | ## Pull Request Process 9 | 10 | 1. Ensure any install or build dependencies are removed before the end of the layer when doing a 11 | build. 12 | 2. Update the README.md with details of changes to the interface, this includes new environment 13 | variables, exposed ports, useful file locations and container parameters. 14 | 3. Increase the version numbers in any examples files and the README.md to the new version that this 15 | Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/). 16 | 4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 17 | do not have permission to do that, you may request the second reviewer to merge it for you. 18 | 19 | ## Code of Conduct 20 | 21 | ### Our Pledge 22 | 23 | In the interest of fostering an open and welcoming environment, we as 24 | contributors and maintainers pledge to making participation in our project and 25 | our community a harassment-free experience for everyone, regardless of age, body 26 | size, disability, ethnicity, gender identity and expression, level of experience, 27 | nationality, personal appearance, race, religion, or sexual identity and 28 | orientation. 29 | 30 | ### Our Standards 31 | 32 | Examples of behavior that contributes to creating a positive environment 33 | include: 34 | 35 | * Using welcoming and inclusive language 36 | * Being respectful of differing viewpoints and experiences 37 | * Gracefully accepting constructive criticism 38 | * Focusing on what is best for the community 39 | * Showing empathy towards other community members 40 | 41 | Examples of unacceptable behavior by participants include: 42 | 43 | * The use of sexualized language or imagery and unwelcome sexual attention or 44 | advances 45 | * Trolling, insulting/derogatory comments, and personal or political attacks 46 | * Public or private harassment 47 | * Publishing others' private information, such as a physical or electronic 48 | address, without explicit permission 49 | * Other conduct which could reasonably be considered inappropriate in a 50 | professional setting 51 | 52 | ### Our Responsibilities 53 | 54 | Project maintainers are responsible for clarifying the standards of acceptable 55 | behavior and are expected to take appropriate and fair corrective action in 56 | response to any instances of unacceptable behavior. 57 | 58 | Project maintainers have the right and responsibility to remove, edit, or 59 | reject comments, commits, code, wiki edits, issues, and other contributions 60 | that are not aligned to this Code of Conduct, or to ban temporarily or 61 | permanently any contributor for other behaviors that they deem inappropriate, 62 | threatening, offensive, or harmful. 63 | 64 | ### Scope 65 | 66 | This Code of Conduct applies both within project spaces and in public spaces 67 | when an individual is representing the project or its community. Examples of 68 | representing a project or community include using an official project e-mail 69 | address, posting via an official social media account, or acting as an appointed 70 | representative at an online or offline event. Representation of a project may be 71 | further defined and clarified by project maintainers. 72 | 73 | ### Enforcement 74 | 75 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 76 | reported by contacting the project team at [INSERT EMAIL ADDRESS]. All 77 | complaints will be reviewed and investigated and will result in a response that 78 | is deemed necessary and appropriate to the circumstances. The project team is 79 | obligated to maintain confidentiality with regard to the reporter of an incident. 80 | Further details of specific enforcement policies may be posted separately. 81 | 82 | Project maintainers who do not follow or enforce the Code of Conduct in good 83 | faith may face temporary or permanent repercussions as determined by other 84 | members of the project's leadership. 85 | 86 | ### Attribution 87 | 88 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4.1, 89 | available at [http://contributor-covenant.org/version/1/4][version] 90 | 91 | [homepage]: http://contributor-covenant.org 92 | [version]: http://contributor-covenant.org/version/1/4/ 93 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ### Posting rules 2 | 3 | 1. **Fill** the **Your System Configuration section (all of it!)** if you have some kind of error or performance question. 4 | 2. **No duplicated** posts. 5 | 3. **No** posts about **questions already answered / clearly explained in** the **documentation** 6 | 4. Set a **proper issue title**: add the OSX/Ubuntu/Windows word and be specific (e.g. do not simple call it: `Compile error`). 7 | 5. Only English comments. 8 | Issues/comments which do not follow these rules will be **ignored or removed** with no further clarification. 9 | 10 | ### Issue Summary 11 | 12 | ### Executed Command (if any) 13 | 14 | ### Processing Output (if any) 15 | 16 | ### Type of Issue 17 | You might select multiple topics, delete the rest: 18 | - Compilation/installation error 19 | - Execution error 20 | - Help wanted 21 | - Question 22 | - Enhancement / offering possible extensions / pull request / etc 23 | - Other (type your own type) 24 | 25 | ### Your System Configuration 26 | **Operating system**: 27 | -------------------------------------------------------------------------------- /Images/Point.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/totovr/Processing/c270e83579a3b39ce5c60eed855c1be487ca9e6e/Images/Point.png -------------------------------------------------------------------------------- /Images/Skeleton_Tracking.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/totovr/Processing/c270e83579a3b39ce5c60eed855c1be487ca9e6e/Images/Skeleton_Tracking.png -------------------------------------------------------------------------------- /Images/deep.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/totovr/Processing/c270e83579a3b39ce5c60eed855c1be487ca9e6e/Images/deep.png -------------------------------------------------------------------------------- /Images/kinectv1.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/totovr/Processing/c270e83579a3b39ce5c60eed855c1be487ca9e6e/Images/kinectv1.jpg -------------------------------------------------------------------------------- /Images/threshold.gif: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/totovr/Processing/c270e83579a3b39ce5c60eed855c1be487ca9e6e/Images/threshold.gif -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2018 Antonio Vega 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: 6 | 7 | The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. 8 | 9 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. 10 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Processing 2 | 3 | Processing is a flexible software sketchbook and a language for learning how to code within the context of the visual arts. Since 2001, Processing has promoted software literacy within the visual arts and visual literacy within technology. There are tens of thousands of students, artists, designers, researchers, and hobbyists who use Processing for learning and prototyping. 4 | 5 | For more information check [Processing.org](https://processing.org/reference/) 6 | 7 | This repository contains Processing programs for different applications, change of branch depending of your currently version: 8 | 9 | * Programs using Processing [V2.2.1](https://github.com/totovr/Processing/tree/Processing-2.2.1) 10 | 11 | * Programs using Processing [V3.3.6](https://github.com/totovr/Processing/tree/Processing-3.3.6) 12 | 13 | * Programs using Processing [V3.3.7](https://github.com/totovr/Processing/tree/Processing-3.3.7) 14 | 15 | ## Getting Started 16 | 17 | These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system. 18 | 19 | ### Prerequisites 20 | 21 | * Processing IDE 22 | * A computer with OSX, Windows, Linux 23 | 24 | Alternative: 25 | 26 | * Kinect V1 27 | * Kinect V2 28 | * Arduino IDE 29 | * Arduino board 30 | * Atom 31 | 32 | ### Installing 33 | 34 | Install the last stable version of Processing IDE, you can download it from this page: 35 | 36 | * [Processing IDE](https://processing.org/download/) 37 | 38 | For OSX you just need to unzip the folder and paste the App in the applications folder. 39 | 40 | ## Test a program sample: 41 | 42 | Open Processing IDE and upload the next example: 43 | ``` 44 | void setup() { 45 | size(480, 120); //Create a window of 480*120 46 | } 47 | 48 | void draw() { 49 | if (mousePressed) { 50 | fill(0); 51 | } else { 52 | fill(255); 53 | } 54 | ellipse(mouseX, mouseY, 80, 80); //If we pressed the mouse a Ellipse will be draw 55 | } 56 | ``` 57 | This is one simple example of how to draw a Ellipse in the sketch window. 58 | 59 | ## Also you can use the next IDE to build programs: 60 | 61 | * [Processing Online Editor](http://js.do/blog/processing/editor/) 62 | * [Atom](https://atom.io/) 63 | 64 | ## Contributing 65 | 66 | Please read [CONTRIBUTING.md](https://github.com/totovr/Processing/blob/master/CONTRIBUTING.md) for details of the code of conduct, and the process for submitting pull requests to us. 67 | 68 | ## Versioning 69 | 70 | I use [SemVer](http://semver.org/) for versioning. 71 | 72 | ## Author 73 | 74 | Antonio Vega Ramirez: 75 | 76 | * [Github](https://github.com/totovr) 77 | * [Twitter](https://twitter.com/SpainDice) 78 | 79 | ## License 80 | 81 | This project is licensed under The MIT License (MIT) - see the [LICENSE.md](https://github.com/totovr/Processing/blob/master/LICENSE.md) file for details 82 | 83 | ### The instructions to Setup the Kinect are written for Mac OS High Sierra users. 84 | 85 | 86 | 87 | -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-slate --------------------------------------------------------------------------------