Open MarkBennett opened 2 years ago
Got it. Good feedback. Thanks for the advice.
I rewrote the Motivation section completely: any chance you could tell if this is an improvement @MarkBennett ?
I've worked with a few great, battle-tested React data-vis libraries, including Formidable, Nivo and React-Vis. While these are often enough to produce beautiful charts with very few lines of code, they have limitations when attempting to integrate with more complicated data-centered apps.
Some of the things I struggled with were:
Hypocube introduces a layer of indirection between the "data", as mapped on a Cartesian plane, and the "design", authored in units of pixels. A base Chart component manages the scaling and passes it down via context. Hypocube uses several parts of d3 to manipulate drawing instructions, but takes a React-based approach to managing the DOM - and the canvas context.
That looks way better Casey! My only suggestion would be to try to summarize it in a quick sentance at the top of the page. You'll probably want to do this in your own words, but something short and sweet like:
"Performant, responsive and powerful data visualization for your React applications"
OK.
Thanks so much for all your help with this :+1:
It's not totally clear why I should care about, "Composable, responsive, React-based data visualization".
Reading the motivation it seems like you've learned a lot over the last year, but I'd zoom in on the pain or challenge you faced and how how this solves it, then put a sentence that states the pain and how your library solves it. Would help put it in context for others trying to understand it.