Increasing access
p5 is exploring a few new subject areas where APIs are experimental and may change in response to user feedback. The fact that they're experimental should be more clearly communicated to avoid unexpected breakages of code in the future, to make it easier to test out this kind of functionality safely, and most importantly to get more community members involved in the direction of those areas of p5.
Most appropriate sub-area of p5.js?
Feature request details
Some things I think a successful version of this must do:
- It should log a warning when you use experimental functionality when FES is enabled so that it's clear you did something experimental.
- It should only log once per subject area per sketch -- we don't want to flood your console with noise.
- It should have a useful message explaining what experimental thing you're using and directing you to somewhere you can find out more.
- Every experimental subject area should provide this in the form of a contributor doc explaining what it is, what its goals are, and what we need feedback on.
Increasing access
p5 is exploring a few new subject areas where APIs are experimental and may change in response to user feedback. The fact that they're experimental should be more clearly communicated to avoid unexpected breakages of code in the future, to make it easier to test out this kind of functionality safely, and most importantly to get more community members involved in the direction of those areas of p5.
Most appropriate sub-area of p5.js?
Feature request details
Some things I think a successful version of this must do: