Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

document skin names

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
design, frontend

Research direction

Start with the linked src/plugins/score-lib-process/Process/Style/ScenarioStyle.cpp and inspect how Scenario objects receive colors. Then trace the theme editor's color list to understand where usage information could be displayed. Done means the editor provides descriptive usage context for each skin color without losing the existing color listing.

Written by the indexing model from the issue text.

Description

currently the skin color are named 'Base3', "Pulse1' and so on... which is not so descriptive.

it could be nice to give the user some sense of where they are used.

IMHO the best place for that would be in the theme editor, e.g. by adding a second column to the color list, with every place (or at least some places) where this color is used
(I guess this could be implemented by filling some kind of multimap or something every time a Scenario object is given a color so that there's a way to retrieve where each of them is used - am I being clear ?)

Dominant language
Ruby
Stars
3
Forks
16
Avg merge
2d 22h
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ossia/score-docs

All issues in ossia/score-docs

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.