hovancik/stretchly

[Feature request]: Randomize color

Open

#1,036 opened on Nov 11, 2021

View on GitHub
 (3 comments) (1 reaction) (0 assignees)JavaScript (410 forks)batch import
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (3,892 stars)
PR merge metrics
 (Avg merge 2d 7h) (14 merged PRs in 30d)

Description

Version

  • I'm using version 1.7.0

Existing requests

  • I've checked Existing requests

What operating system are you using?

Windows

Operating System Version

Windows 10 Pro 21H1

Problem description

I love this app, but notice that I have gotten too used to it, which often results in me ignoring it, often even without noticing. I sometimes just absentmindedly click it away. I don't want to use Strict Mode because sometimes I do have an important reason to delay the break (such as being in a videocall, or just about to finish something).

Possible solution

What I believe could help is randomized colors. In settings, instead of choosing a specific color, one could choose "random". I believe this would trigger the brain more, having more chance to avoid any automated action (like clicking it away).

Alternative solutions

Another option is to hide the "Postpone / Skip break" link for just 2 seconds. It prevents one from hiding it as an 'automated action', but still allows one to postpone it if really needed. A 2 second delay could make me reconsider whether I really do want to postpone/skip now.

Additional information

I started using Stretchly about half a year ago.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Contributor guide

Research direction
Explore the existing color settings implementation in the codebase. Look for where break window colors are defined and how they are applied. Consider adding a 'random' option to the color setting that picks a random color from a predefined palette or generates one dynamically. Investigate the settings UI and the break window rendering code to understand where changes are needed.
Tech stack
javascript
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75