NASA-AMMOS / NASA-AMMOS/plandev
Ability to auto-set color by subsystem
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
Clipper users don't anticipate needing to do any color-coding at the activity planner level. Rather, the expectation is that the mission will thoughtfully assign and standardize colors for each instrument/subsystem and that this color scheme will flow throughout all plans.
Ideally, colors would be set at an admin level. Or there would be some way to start a fresh plan that ingests the appropriate color scheme.
Color coding is crucial for discerning between different types of activities at a glance, especially within dense plans.
Related to this issue about color-coding layers without overprinting
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
Start by reviewing the activity planner's current color-coding behavior and the related color-coding-layers issue 835. Clarify whether colors should be configured administratively, inherited when creating a fresh plan, or both, then define how subsystem colors remain consistent across all plans.
Written by the indexing model from the issue text.
Assessment
- Domain
- design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100