gradient process ideas and suggestions
Open
Nobody has claimed this yet.
good first issue
ODHack14
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 129
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 48
Description
- point management should be consistent with other processes, i.e. at least from a menu on right-click (and potentially in better ways, see #481)
- IMO the first point should be based on the color value of the first state, and the last point on the one of the end state
- when adding a point it should query the current value of the associated address if there is one
- when choosing a color from i-score's color picker it should be output (ideally it would be great if the color be output continuously when moving the "target" of the color picker
- it would also be very very cool that a gradient be created when 'interpolating states' or creating a sequence (see #480)
- add a (0. to 1.) curve, such as in interpolations between each point pair, in order to change the 'transition' shape between two color values
- not sure about this, but maybe there could be more advanced ways to interpolate between colors (I'm thinking about duration's "color palette" for interpolation) - not for next month, I guess, but probably worth discussing
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Review the gradient-process requests and the referenced issues #481 and #480 first; the work is complete only after the desired subset of proposals is agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100