Feature Request: Marimekko
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
- Stale
- Tech stack
- kotlin
- Domain
- data-visualization
Research direction
Start by locating the Bistro Plots module and reviewing how existing chart types define their inputs and rendering behavior. Use the requested X and Y labels and metrics, including count alternatives, as the acceptance criteria; confirm the result matches the Marimekko examples described in the issue.
Written by the indexing model from the issue text.
Description
Marimekko charts
Marimekko charts are able to consolidate two 100% stacked bar charts into one. Consolidating two related metrics helps in presenting the information concisely to viewers and results in eye-catching visuals.
Rationale
Although LetsPlot certainly has the tools to create them, the number of data transformations needed might make Marimekko Bars a good addition to the Bistro Plots module.
Expected inputs
Marimekko charts take four inputs:
- Labels to use for the X axis.
- An X axis metric which needs to be accumulated up to the plot size / Alternatively the number of entries of the label is counted.
- Labels to use for the Y axis.
- An Y axis metric which needs to be accumulated up to the plot size / Alternatively the number of entries of the label is counted.
Examples
Asset manager regions vs Asset managers per region
Exported product distribution vs Main exporters per product
Renewable energy jobs vs region distribution for each energy type
- Dominant language
- Kotlin
- Stars
- 1.8k
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 JetBrains/lets-plot
-
SyntaxWarning upon library importPossibly taken @Shriraj1901 claimed this 12 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
All issues in JetBrains/lets-plot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AlfaazPlus/QuranApp#752 · 2 comments ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
theopenconversationkit/tock#2148 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
music-assistant/mobile-app#1393 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100