Legend controls: second pass
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- data-visualization, frontend
Research direction
Launch a VISOR session and inspect the existing legends panel and state-file workflow first. Implementing the requested orientation, palette, levels, interpolation, undefined-value color, and persistence options is done when they work for a colored variable and reload correctly from a saved state file.
Written by the indexing model from the issue text.
Description
User Story Description
The MVP list contained the legend panel. That panel for the MVP had minimal functionality. New functionalities need to be added, in particular:
- control orientation of the legend (horizontal / vertical)
- color palette (select from a list of palettes. Note: usually tools show both the name and a schema of the palette)
- control number of palette levels. You can control the number of levels, value at each level and exact color
- type of interpolation (linear vs log) between palette levels
- color to use for undefined value. The user should set from the color wheel or RGB
- pick the interpolation type for the palette: continuous, banded, constant
Acceptance Criteria
Launch a VISOR session. Color one part by a variable. In the legends panel, all the new functionalities are available and work.
Save a state file. Launch a new VISOR session. Load the state file. Verify that all the legend advanced options are stored correctly.
Additional Links
No response
Requires new or update to third party ? If "yes" add the name(s) and the version(s) of the Third Party Software.
No
Name and Version for Third Parties
No response
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 47
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.
More from ansys/Visual-Interactive-Simulation-Object-Renderer
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Library updates Opentechnical
ansys/Visual-Interactive-Simulation-Object-Renderer#136 · 1 assignee ·
-
maintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#131 · 1 assignee ·
-
Release 1.0.2 Openmaintenance
ansys/Visual-Interactive-Simulation-Object-Renderer#130 · 1 assignee ·
-
enhancement
ansys/Visual-Interactive-Simulation-Object-Renderer#126 · 1 assignee ·
All issues in ansys/Visual-Interactive-Simulation-Object-Renderer
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
instance instance add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
searxng/searx-instances#939 · 1 comment ·
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100