41–50 of 51 posts
Earlier quoted context omitted.
I bet that not supporting those are intended. I don't get why there is always this need to support old tech. Can't we not just move forward?
Both my android devices run 2.3 and I'm using highcharts without problems on both. Which is why I won't probably be using this.
Why prefer this over Chart.js [1] which is responsive as well? [1] https://github.com/nnnick/Chart.js/
Earlier quoted context omitted.
SVG in general falls over with very large datasets, I find html canvas based libraries such as maybe Flot better for thousands upon thousands of datapoints. I love d3 as much as anyone and all of it's offspring, but SVG is too slow in most browsers (especially Firefox) for lots of datapoints.
It is interesting that you cannot copy SVG out of your browser. When I visit the page in Chrome, mouse over the graph and "copy," it doesn't copy either the BMP buffer OR the raw SVG (XML). I was going to try and copy/paste into Outlook, but that's obviously no-go if you cannot copy at all. Interesting limitation of SVG that I wasn't aware existed until now.
Earlier quoted context omitted.
Both my android devices run 2.3 and I'm using highcharts without problems on both. Which is why I won't probably be using this.
Why? You're like one of those people who still uses Windows XP. Spend $100 and get a device that runs something released in the last SIX years.
In an ideal world (for software and hardware vendors, at least) we would be replacing devices with their latest versions as soon as they come out and backward compatibility wouldn't be a problem. However, I can imagine a situation where spending $100 on a new phone is a luxury and not everyone can afford it. If a phone makes calls, sends text messages, and connects to the Internet, it's still usable.
Earlier quoted context omitted.
True, but "mobile first" is not "mobile only". The point of responsive design is for things to work well on multiple platforms, not just one.
correct. So why not use a multi-platform interaction like on click?
If a hover tooltip has a clickable content then yes, using on click to lock the tooltip in place is a good idea. For example, hover navigation with subcategories can be awkward to use and on click navigation is a better choice here. But for a simple caption in an interactive chart it would be an overkill on desktops.
Earlier quoted context omitted.
Why? You're like one of those people who still uses Windows XP. Spend $100 and get a device that runs something released in the last SIX years.
But 2.3 (Gingerbread) was released in December 2010, so his device indeed runs something released in the last six years. In an ideal world (for software and hardware vendors, at least) we would be replacing devices with their latest versions as soon as they come out and backward compatibility wouldn't be a problem. However, I can imagine a situation where spending $100 on a new phone is a luxury and not everyone can…
Like XP, Gingerbread has unpatched security vulnerabilities. Having a mobile phone with up-to-date security is well worth spending $99 (for a Moto G, for example).
I get that not everyone can afford something like that, but it's like car insurance. You absolutely can't afford to have your identity stolen.
Earlier quoted context omitted.
Chart.js is not being actively developed or patched. Dealbreaker.
how so? the last commit was 10 days ago.
I was following several issues that the author wasn't even responding to, even though many people were asking after it. Around 25% of the issues are a year old, and many more are 8+ months old.
Finally, someone made a fork of the project with a lot of the requests that people were making. A "people's fork" wouldn't have been created if it were sufficiently active.
Looks cool though.
Given that this doesn't work on Android 2.* stock browser (and I assume IE8), it would be good to see some kind of fallback - preferably canvas and if that's not supported then a table of the raw data, which would be better than the current blank space.
I bet that not supporting those are intended. I don't get why there is always this need to support old tech. Can't we not just move forward?