Also improved the performance with built-in extremes calculation, so we can skip axis min and max options now.Īxis.translate will work like before, so your syncing between charts should not be affected. I've pushed another commit which fixes the tooltip issue when zoomed in. I also think this should be part of the chart options (across all series). 'autoExtremes' is also good if it will enable me to have better performance. The 'threshold' option on the other had is good, but then I ask my self why do I need the SVG option in the first place? And what am I loosing here? Probably we cannot answer this right now. I'm not sure enableTooltip should take part of it since this option already exists in the tooltip itself. The optimize feature is exactly what I was looking for in the first place. The other thing is that we use to draw a crosshair synchronized between charts. But just so you know, zooming to ~100 points in the chart the tooltip starts to get an offset for some points from their original position. Regarding the zoom, the drag gesture is nearly enough since we translate it to a server zoom. So after reading your last comment I realize I will/may loose much functionality (series types, stacking options) since the nature of the solution is overriding the highcharts prototype. So basically we use many kind of series types and enable our customers to change these types on the fly. We use it for dashboards, investigating large time series data graph and monitoring. Our use of highcharts in our app is very intense. We could add optimize options so that the implementer can set when to go to canvas mode and how agressively we optimize. None the less i think this should be an integral part of the product But I suggest we work on this incrementally if you find problems with it. We have bypassed extremes calculation, data cropping, data grouping in Highstock and even Point instanciation, and work on the original data array directly in order to do only one single loop over the data set. And probably we should be able to define levels of optimizing, for example if you have 500,000 points, it is expensive to find the data min and max, but not so much with 10,000 points.Ĭan you think of any pitfalls in advance? There's still much work to be done, for example each series type needs its own optimized drawGraph function as well as perhaps drawPoints. It seems to me this is something possible for a near future release I now added support for zooming and resizing, and probably most other cases of redrawing. We noticed that flot.js (charts) have none of these problems and are very smooth? Can highcharts compete with that?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |