Increasing Access
Currently, learners starting from 2.0 tutorials and examples who open the editor from the site still have to manually open library management settings, and select the 2.0 version. Right now, this is especially relevant for using 2.x, but in the future, it would be important for any non-default version: Once 2.x is default, for example, a tutorial that requires 1.x would also benefit from this feature. From the 1.x website, it should be possible for learners and teachers to open the editor with the correct version already selected, preventing confusion.
Most appropriate sub-area of p5.js?
Home
Feature request details
The ability to specify editor.p5js.org?version=2.0.4 in the URL has recently been implemented - it's not quite live yet, but the issue and PR shows use, and it has been merged.
The prominent links to the editor should specify a version:
|
<a className={styles.buttonlink} href="https://editor.p5js.org"> |
|
<LinkButton variant='link' url='https://editor.p5js.org/'> p5.js Editor </LinkButton> |
- optionally, could update other links - though best to start with the above two
The version should not be hardcoded, but use version from p5-version.ts (you can test both with main/1.x, and 2.0/2.x: 2.x p5-version.ts.
NOTE: The PR should target the 2.0 branch first, but will be applied to main as well.
Increasing Access
Currently, learners starting from 2.0 tutorials and examples who open the editor from the site still have to manually open library management settings, and select the 2.0 version. Right now, this is especially relevant for using 2.x, but in the future, it would be important for any non-default version: Once 2.x is default, for example, a tutorial that requires 1.x would also benefit from this feature. From the 1.x website, it should be possible for learners and teachers to open the editor with the correct version already selected, preventing confusion.
Most appropriate sub-area of p5.js?
Home
Feature request details
The ability to specify
editor.p5js.org?version=2.0.4in the URL has recently been implemented - it's not quite live yet, but the issue and PR shows use, and it has been merged.The prominent links to the editor should specify a version:
p5.js-website/src/components/Nav/MainNavLinks.tsx
Line 84 in e6c6402
p5.js-website/src/content/text-detail/en/download.mdx
Line 18 in e6c6402
The version should not be hardcoded, but use version from p5-version.ts (you can test both with
main/1.x, and2.0/2.x: 2.x p5-version.ts.NOTE: The PR should target the
2.0branch first, but will be applied tomainas well.