pratu16x7

28 ms·

1.
by pratu16x7 7y ago
Location: Mumbai, India Remote: Yes Willing to Relocate: Yes (Visa assistance needed for jobs outside India) Technologies: Python, Javascript, VueJs, HTML/CSS, Django/Flask Resume/CV: https://pratu16x7.com/res
2.
by pratu16x7 9y ago
We gave it too less data than it deserved I believe. Thanks for reporting the click problem. Would you mind creating an issue at GitHub, so that we can keep track?
3.
by pratu16x7 9y ago
The argument would be no different from all the products out there who design their own UI (MUX, GitHub). Our framework Frappé (and product ERPNext) has a great emphasis on minimal style, and we really wished the charts to be free of visual
4.
by pratu16x7 9y ago
Update: https://www.npmjs.com/package/frappe-charts
5.
by pratu16x7 9y ago
We used cal-heatmap ( https://github.com/wa0x6e/cal-heatmap ) earlier. It's pretty neat.
6.
by pratu16x7 9y ago
Check our take on why they weren't a priority for us, and we went with percentage charts (the 'Why percentage?' link on the website): http://www.storytellingwithdata.com/blog/2011/07/death-to-pi
7.
by pratu16x7 9y ago
Thanks! That just about answers the burning question: why another charting library? It all boiled down to us needing some simple charts for our report data; nothing fancy, just something that went with our classic design. All we needed was
8.
by pratu16x7 9y ago
> Is responsiveness a priority with this library? It sure is. Just pushed a fix, thanks for reporting :) Do report any issues you find over at https://github.com/frappe/charts/issues
9.
by pratu16x7 9y ago
We look forward to adding those (just created an issue). They are quite decoupled as of now, so shouldn't be much trouble.
10.
by pratu16x7 9y ago
Supported across all major browsers :) We've covered much ground on the most used charts (while the heatmap just happened to be something we needed) and have the basic components down. That'll facilitate putting in, say, more axi