Skip to content
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.

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

Add Distinct Visual Elements for Non-Production Versions (icon, splash screen, etc) #922

Open
SableRaf opened this issue Jan 17, 2025 · 4 comments

Comments

@SableRaf
Copy link
Collaborator

SableRaf commented Jan 17, 2025

Non-production builds for Processing currently look mostly identical to official releases, making it difficult to recognize at a glance that you're using a non-production version. This could lead to confusion among testers and contributors, and create mix-ups when reporting issues.

I suggest we introduce distinct visual markers for pre-release versions (test, beta, dev, or nightly builds). This will help users immediately recognize they are running a non-production version of Processing.

Proposed Changes

  1. App Icon – Use an alternate icon for non-production builds, such as adding a yellow ribbon with Test, Beta, or Dev depending on the build type.
  2. Splash Screen – Include a clear indicator that the user is running a pre-release version.
  3. Version Label in UI – Add a visible label (e.g., "Test Build," "Beta," "Nightly") in the title bar.
  4. Instructions for testing – Include a README in test builds only with specific instructions for testing.
@SableRaf
Copy link
Collaborator Author

Making separate issues for this particular topic may be overkill but I wanted to test Github's new sub-issues 😃

@Stefterv
Copy link
Collaborator

I was wondering where the giant list came from :)

@Stefterv
Copy link
Collaborator

For the beta we cannot really use an indicator in the way we've done it so far. The beta's have been release assets and have not been re-compiled for the final release. I assume there would be no variance in building it again but the current setup is not really conducive to doing it.

@Stefterv
Copy link
Collaborator

In the gradle version I've already made it so that you can run the released version and the build version at the same time. Maybe we can look into having a different settings folder etc...

Also still thinking of creating a little helper tool that helps with installing testing versions etc...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants