Skip to content
This repository has been archived by the owner on Nov 7, 2018. It is now read-only.

Improvements and docs for bullet charts #104

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open

Conversation

mgold
Copy link

@mgold mgold commented Sep 3, 2014

Bugfixes, improvements, and documentation for bullet charts. Changes are broken out into multiple commits with detailed summaries.

You can see the changes at work in this bl.ocks; be sure to open in a new window.

Question: what would it take to move bullet charts into d3.format and out of the plugin repo?

To reproduce: go to the vertical example, and change the orientation from
"bottom" to "left". Observe the axis tick marks above the plot, reaching down
into it.
It's how Stephen Few wants it, from the design spec:
Whenever the featured measure intersects a comparative measure, the comparative
measure should usually appear behind the featured measure.
Also, no need to specify a transform that does nothing.

Mostly a style thing.
If I have multiple markers, I want the second to be less prominent.
If I have charts with a varying number of ranges, I also need to know the total
number of ranges.
Rather than call ranges, markers, and measures, see if they're a function first.
Sorting the markers is unhelpful: they won't occlude each other and it's helpful
to be able to style the first marker more prominently.
Sorting the measures is unhelpful for the same reason, we want to always know s0
is the actual value and s1 is the forecast. However, for rendering, we sort them
to prevent occlusion.
@mgold
Copy link
Author

mgold commented Sep 5, 2014

Paging @jasondavies?

Note that this documention reflects the changes I have made.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant