Skip to content

Resetting to p5.js default version #3504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
xinemata opened this issue Jun 1, 2025 · 7 comments · May be fixed by #3525
Open

Resetting to p5.js default version #3504

xinemata opened this issue Jun 1, 2025 · 7 comments · May be fixed by #3525
Assignees
@A-L-A
Labels
Area: Design For UI/UX design updates, proposals, or feedback Enhancement Improvement to an existing feature Good First Issue A beginner-friendly issue, great for first-time contributors Help Wanted Would love additional input or contributions!

Comments

@xinemata
Copy link

xinemata commented Jun 1, 2025

Increasing Access

Provide more clarity to all users to return to the stable version of p5.js after switching to another version.

Feature enhancement details

When I switched to the latest version of 2.x, but then wanted to switch back to the default version afterward, it wasn't clear to me which version was the stable one.

Image

Showing an indication of which version is default and which one is still in beta might help users switch back and forth between the stable and experimental versions with more confidence.

A mockup of the improved drop-down menu is shown below:

Image

Looking forward to hearing feedback on this!
@xinemata xinemata added Help Wanted Would love additional input or contributions! Area: Design For UI/UX design updates, proposals, or feedback Good First Issue A beginner-friendly issue, great for first-time contributors Enhancement Improvement to an existing feature Awaiting Maintainer Approval Needs review from a maintainer before moving forward labels Jun 1, 2025
@xinemata
Copy link
Author

xinemata commented Jun 1, 2025

@amy-b and Ava helped write this issue!

@ksen0
Copy link
Member

ksen0 commented Jun 2, 2025

I agree that it's really good to help "switch back" when needed! It's helpful also to use "beta" since the main reference website for 2.0 is beta.p5js.org

Aside from adding more information to the dropdown, do you think it would also be helpful to update the copy that's there? For example, link not to the release note but to the 2.0 reference site, or perhaps other changes?

Adding @davepagurek in this conversation, in case they have thoughts on UI design or copy here!

@davepagurek
Copy link
Contributor

I agree, I think Beta / Default (or Beta / Stable?) would be good to add!

@raclim raclim removed the Awaiting Maintainer Approval Needs review from a maintainer before moving forward label Jun 2, 2025
@amy-b
Copy link

amy-b commented Jun 3, 2025 •
edited
Loading

Great! I have a slight preference to use "Beta / Default" because we say "default" in the description under the dropdown menu ("2.0 will become default on August 2026") and it's a slightly more layman friendly.

Re: adding more information - I do think it would be helpful to get a link to the reference site for those who want to see what's new.

What do you think about this as an update? I added a sentence with the reference link:

There's a new 2.0 release of p5.js available! Check out the new reference page to see what's new. p5.js 2.0 will become default on August 2026, so take this time to test it out and report bugs. Interested in transitioning sketches from 1.x to 2.0? Check out the compatibility & transition resources.

@A-L-A
Copy link

A-L-A commented Jun 11, 2025

If issue is still available, would love to be assigned. @xinemata @amy-b

@raclim
Copy link
Collaborator

raclim commented Jun 11, 2025

Hi @A-L-A, thanks for your interest in the issue! I just assigned it to you!

Feel free to ask here if any further questions come up as you start diving into it!

@A-L-A
Copy link

A-L-A commented Jun 11, 2025

Great, will do thanks @raclim

A-L-A added a commit to A-L-A/p5.js-web-editor that referenced this issue Jun 17, 2025
@A-L-A
[processing#3504] Add version labels for default and beta versions
d6aa359 
- Marked 1.11.7 as '(Default)' and 2.0.3 as '(Beta)'
- Updated version matching logic to handle object format
- Maintained backward compatibility with string versions
@A-L-A A-L-A linked a pull request Jun 17, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@A-L-A A-L-A

Labels
Area: Design For UI/UX design updates, proposals, or feedback Enhancement Improvement to an existing feature Good First Issue A beginner-friendly issue, great for first-time contributors Help Wanted Would love additional input or contributions!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#3504] Add version labels for default and beta versions A-L-A/p5.js-web-editor
6 participants
@ksen0 @davepagurek @xinemata @amy-b @raclim @A-L-A