Golodhros
Boosting Big Data Workloads at Eventbrite with Presto Auto Scaling
Automated Cross-Browser Testing for WebGL– It’s Not Going to Happen
Varnish and A-B Testing: How to Play Nice
The Fundamental Problem of Search
The Quest for React Micro-Apps: The Beginning
Getting the most out of React Alicante (with videos)
Getting started with Unit Tests
The “Aha” Moments of Becoming an Engineering Manager
How Your Company Can Support Junior Engineers
Creating Flexible and Reusable React File Uploaders
Totally! You could fork the library and modify the charts if that's what you need. The source code is based on the reusable API (https://www.eventbrite.com/engineering/leveling-up-d3-the-re...), and it should be easy for D3 developers to understand the code and extend it. Our development environment also provides with the demo pages that can be used as a sandboxed context, and you can make use of our current tests to keep the code well tested!
Regarding the drill down charts, in theory, is possible!
I am sorry that you just find our current bug with the build! We have an issue about that, and we will be trying to fix it ASAP. I totally understand, having all the charts available in one file is an important use case.
In the meanwhile, you can use the individual chart bundles, like '/dist/umd/bar.min.js' and either load it with require/commonJS or load it with a script tag (it would be assigned to document.britecharts.bar).
We are super interested to know what we can do better on our docs, any feedback would be great!
What do you find is missing on the examples? Would you like more info about when to use each chart? Or more examples of the different configuration options?
That's a great question! We at Eventbrite are looking into improving our accessibility, our designer Sun is pushing for it on this issue: https://github.com/eventbrite/britecharts/issues/168
In that link you can find some references about accessibility on other libraries and best practices.
Thanks, we are super excited about releasing this project as Open Source, it's been such a trip!
Totally, D3.js is a fantastic low-level library and is super reusable in all senses (examples, low-level plugins, different reusability patterns). However, one of D3.js usability problems comes from its main advantage, how powerful it is!
This means that D3 has a very low-level granularity and a huge API, making it hard for newcomers to create a simple chart for a dashboard or a one-off data viz.
That's one of the reasons why we created Britecharts, to democratize D3.js charts, and at the same time, serve as a stepping stone to those who want to learn more about D3.
In our mind, using Britecharts, a junior developer could render a chart quickly, just doing d3 selections. Then, she can start tinkering with one of the charts and even create a new one, learning d3.js in the process.
Specifically, stacked against C3, Britecharts has a more 'D3-like' API, while C3 is a lot more declarative. This means that on C3, we will render charts by passing large configuration objects, while in Britecharts we strive to use a different API, chaining settings like we do on D3.
Also, C3 hasn't been updated to D3 v4, and we can say it is an inactive project.
Thanks for the bug report! I will create a ticket for it and check it out soon.
From what you said, it seems scrolling is triggering a viewport resize, so we will review our viewport resize listener on the demos (it's not really inside Britecharts).
Thanks again!