Skip to content

Commit e96c679

Browse files
committed
Merge branch 'main' into interpilate
2 parents 76e1e6c + 60078ba commit e96c679

File tree

206 files changed

+9101
-1062
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

206 files changed

+9101
-1062
lines changed

.all-contributorsrc

Lines changed: 1475 additions & 0 deletions
Large diffs are not rendered by default.

.github/ARM32.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
# Processing 32-bit Linux
2+
3+
For the Raspberry Pi 3 and older we'd need to create an 32-bit arm version of
4+
processing.
5+
6+
Github Actions do not support creating 32 bit runners so we need to host one
7+
ourselves.
8+
9+
## Instructions
10+
11+
### Gathering your Tools
12+
13+
You will need:
14+
15+
- A Raspberry Pi
16+
- A micro SD card
17+
- An SD card reader
18+
- A computer
19+
20+
### Flashing the SD Card
21+
1. Install and open [**Raspberry Pi Imager**](https://www.raspberrypi.com/software/) on your computer
22+
2. In **Raspberry Pi Imager**:
23+
- Select your Raspberry Pi model
24+
- Select "Raspberry PI OS lite (32bit)" as the OS (you may need to look into the sub-menus)
25+
- Select your SD card
26+
- Click NEXT
27+
3. Edit the OS settings:
28+
- Set a hostname (e.g. `processing.local`)
29+
- Set a username and password
30+
- Go to the SERVICES tab and enable SSH with password authentication
31+
- Click SAVE and Apply the OS customisation settings
32+
33+
### Configuring the Raspberry Pi
34+
1. Take the written SD card and put it into the Raspberry PI
35+
2. Power it up and wait for it to boot
36+
3. SSH into the Raspberry Pi using the hostname, username, and password you set earlier
37+
4. Follow Github's [instructions on how to set up a self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners). _Note: In the `./config.sh` setup step, you will be prompted to enter a name and other settings. Use default settings by pressing ENTER for each prompt._
38+
5. Verify that the new runner appears in the list of runners on GitHub.
39+
6. Quit the the runner in the terminal (we will set it up to run automatically on boot).
40+
7. Use Github [instructions to setup the runner as a services](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service) so it runs on boot.
41+
42+
Done.
Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
name: 🐛 Found a Bug
2+
description: Report broken or incorrect behavior in Processing 4. (For help with your own code, please visit our forum at discourse.processing.org instead).
3+
labels: [bug]
4+
body:
5+
6+
- type: dropdown
7+
id: sub-area
8+
attributes:
9+
label: Most appropriate sub-area of Processing 4?
10+
description: You may select more than one.
11+
multiple: true
12+
options:
13+
- Accessibility
14+
- Core/Environment/Rendering
15+
- PDE
16+
- Data
17+
- Events
18+
- Image
19+
- IO
20+
- Math
21+
- Typography
22+
- Utilities
23+
- OpenGL
24+
- Contributions Manager
25+
- Export
26+
- Build process
27+
- Unit testing
28+
- Internationalization
29+
- Other (specify if possible)
30+
validations:
31+
required: true
32+
33+
- type: input
34+
attributes:
35+
label: Processing version
36+
description: Go to "Help > About Processing" and look in the bottom-right corner for the version number. It also appears in the title bar of every editor window.
37+
validations:
38+
required: true
39+
40+
- type: input
41+
attributes:
42+
label: Operating system
43+
description: "Ex: Windows/MacOSX/Linux/Android/iOS along with version"
44+
validations:
45+
required: true
46+
47+
- type: textarea
48+
attributes:
49+
label: Steps to reproduce this
50+
description: Describe what steps will produce the bug.
51+
value: |
52+
"1.
53+
54+
2.
55+
56+
3."
57+
validations:
58+
required: true
59+
60+
- type: textarea
61+
attributes:
62+
label: snippet
63+
description: If applicable, include a minimal sketch that produces the error.
64+
value: |
65+
```processing
66+
67+
// Paste your code below :)
68+
69+
void setup() {
70+
71+
}
72+
73+
void draw() {
74+
75+
}
76+
```
77+
validations:
78+
required: false
79+
80+
- type: textarea
81+
attributes:
82+
label: Additional context
83+
description: Add any other context about the problem here.
84+
validations:
85+
required: false
86+
87+
- type: input
88+
attributes:
89+
label: Would you like to work on the issue?
90+
description: |
91+
Please let us know if you can work on this or if the issue should be assigned to someone else.
92+
validations:
93+
required: true
Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
name: 💡 Existing Feature Enhancement
2+
description: Suggest an improvement for an existing feature of Processing.
3+
labels: [enhancement]
4+
body:
5+
6+
- type: dropdown
7+
id: feature-area
8+
attributes:
9+
label: Most relevant area for this enhancement?
10+
description: Choose the most relevant area for the proposed feature or improvement.
11+
multiple: true
12+
options:
13+
- Accessibility
14+
- Core/Environment/Rendering
15+
- PDE
16+
- Data
17+
- Events
18+
- Image
19+
- IO
20+
- Math
21+
- Typography
22+
- Utilities
23+
- OpenGL
24+
- Contributions Manager
25+
- Export
26+
- Build process
27+
- Unit testing
28+
- Internationalization
29+
- Other (specify if possible)
30+
validations:
31+
required: true
32+
33+
- type: input
34+
attributes:
35+
label: Feature to enhance
36+
description: Which existing feature of Processing would be improved by this enhancement?
37+
validations:
38+
required: true
39+
40+
- type: textarea
41+
attributes:
42+
label: Desired enhancement
43+
description: Describe the improvement you’d like to see with that existing feature
44+
validations:
45+
required: true
46+
47+
- type: textarea
48+
attributes:
49+
label: Potential benefits
50+
description: Explain how this enhancement could benefit users or improve Processing.
51+
validations:
52+
required: false
53+
54+
- type: textarea
55+
attributes:
56+
label: Possible drawbacks
57+
description: Consider any possible drawbacks or challenges related to the implementation of this enhancement.
58+
validations:
59+
required: false
60+
61+
- type: textarea
62+
attributes:
63+
label: Additional context
64+
description: Add any other context or screenshots about the feature request here.
65+
validations:
66+
required: false
67+
68+
- type: input
69+
attributes:
70+
label: Would you like to work on the issue?
71+
description: |
72+
Please let us know if you can work on this or if the issue should be assigned to someone else.
73+
validations:
74+
required: true
Lines changed: 72 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,72 @@
1+
name: 🌱 New Feature Request
2+
description: Request adding a new feature to Processing
3+
labels: [new feature]
4+
body:
5+
6+
- type: dropdown
7+
id: feature-area
8+
attributes:
9+
label: Relevant sub-area for this feature?
10+
description: Choose the sub-area most relevant to your feature request.
11+
multiple: true
12+
options:
13+
- Accessibility
14+
- Core/Environment/Rendering
15+
- PDE
16+
- Data
17+
- Events
18+
- Image
19+
- IO
20+
- Math
21+
- Typography
22+
- Utilities
23+
- OpenGL
24+
- Contributions Manager
25+
- Export
26+
- Build process
27+
- Unit testing
28+
- Internationalization
29+
- Other (specify if possible)
30+
validations:
31+
required: true
32+
33+
- type: textarea
34+
id: feature-description
35+
attributes:
36+
label: Feature description
37+
description: Describe the feature in detail. Include how it should work and its intended impact.
38+
validations:
39+
required: true
40+
41+
- type: textarea
42+
id: benefits
43+
attributes:
44+
label: Benefits
45+
description: Outline how this feature would benefit users or improve Processing.
46+
validations:
47+
required: true
48+
49+
- type: textarea
50+
id: challenges
51+
attributes:
52+
label: Possible challenges
53+
description: Discuss any possible challenges or considerations in implementing this feature.
54+
validations:
55+
required: false
56+
57+
- type: textarea
58+
id: additional-context
59+
attributes:
60+
label: Additional context
61+
description: Provide any other information, links, or screenshots that could help illustrate the feature.
62+
validations:
63+
required: false
64+
65+
66+
- type: input
67+
attributes:
68+
label: Would you like to work on the issue?
69+
description: |
70+
Please let us know if you can work on this or if the issue should be assigned to someone else.
71+
validations:
72+
required: true

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
blank_issues_enabled: true
2+
contact_links:
3+
- name: 🌐 Processing Website Issues
4+
url: https://github.com/processing/processing-website/issues
5+
about: Report issues with the processing.org website here.
6+
- name: 📚 Examples Issues
7+
url: https://github.com/processing/processing-examples/issues
8+
about: Report issues with the official Processing examples here.
9+
- name: 💬 Forum
10+
url: https://discourse.processing.org/
11+
about: Have other questions about using Processing? Ask them here!
12+
- name: 🌸 p5.js Issues
13+
url: https://github.com/processing/p5.js/issues
14+
about: Report issues with p5.js here.

.github/release.yml

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
changelog:
2+
exclude:
3+
labels:
4+
- Dependencies
5+
authors:
6+
- dependabot
7+
categories:
8+
- title: What's Changed 🎊
9+
labels:
10+
- '*'
11+
exclude:
12+
labels:
13+
- Dependencies
14+
authors:
15+
- allcontributors
16+
- dependabot
17+
- title: New Contributors 💙
18+
authors:
19+
- allcontributors

0 commit comments

Comments
 (0)