17452 Posts in 4473 Topics by 1971 members
|Go to End|
20 June 2007 at 11:14am
A cool reporting engine that Tim noticed a few months ago has been released. It might be useful on with Quin's Reporting project?
Emprise Corporation is pleased to announce the immediate availability of
which utilizes the <canvas> element and VML to provide cross-browser
compatible, interactive Web 2.0 charts.
EJSChart takes web charting to a new level by incorporating such features as
automatic axis scaling, zooming, scrolling, smart ticks and Ajax-driven data
loading. With its fully documented API, support for multiple chart types and
data retrieval methods, EJSChart is extremely quick and easy to implement in
any web site or web application that requires graphical display of data.
Major features included:
* Interactivity: Zooming, Scrolling, Hints, Mouse Tracking, Mouse
Events, Key Tracking Crosshairs.
* EJSChart will calculate and scale automatically to fit whatever
data it is presented with.
* Auto Zooming, Scrolling: Too much data and not enough screen real
estate? Show it all. Let your end users zoom in on the pieces
they're most interested in. Axis locking for single axis zoom,
scrolling and automatic axis scaling are all included.
* Multiple Chart Types: Line, Area, Scatter, Pie, Bar, Function and
Trend series are just the beginning. New custom series types are
* Ajax-Driven Data: EJSChart supports XML-formatted data and loads
data on the fly. New series can be added and data updated in
real time without page reloads.
* Compatible: Built with compatibility in mind and tested on all
major browsers, you can be assured your charts will function
consistently for the broadest range of end users.
worries of incompatible plugin versions or confusing security
* Fully documented API and many source code and chart examples
For additional information or to download a trial version, please visit
20 June 2007 at 11:28am
It's not open source, so this can't really be the default graphing library.
Perhaps it could be utilised as an option enhancement for people who install it, if the benefits justify the development effort.
Quin - there is a free personal license, if you think that this is worthwhile, we'd be keen to see what you come up with, but we need an alternative open-source library to bundle with SilverStripe by default.
Google Summer of Code Hacker
20 June 2007 at 2:52pm
it would be very useful to my work, and i was very impressed with it back when i first saw the charts
my concerns would be the following:
free version is somewhat limiting: no trends or scatters, 1 chart per page, 2 items per chart
their watermark is on it
licensing and redistribution?
20 June 2007 at 4:22pm
Sorry to sort of jump in but Im working on a webapp at the moment and we are planning on using Plotr - http://www.solutoire.com/plotr .Its a lightweight charting framework (12kb) and ItÃ¢â‚¬â„¢s released under the BSD license (its pretty young at the moment). Its built on prototype js - which is very handy.! Dont know if you guys have come across it or anything but it looks damn handy.
Google Summer of Code Hacker
20 June 2007 at 7:57pm
plotr is nice, its what i used for my browser poll
not nearly as robust as the EJS charts, but it will suffice
21 June 2007 at 10:32pm
Yeah, I'm sorry but even if it's free I don't think we can have Emprise charts polluting the licensing of the core software.
Core Development Team
22 June 2007 at 10:28am
What would be nice is if we had a a bit of an abstraction layer for charting within SilverStripe, so that other solutions can be used if required be the developers.
Note: I've got no idea in about the feasibility of a charting abstraction layer, so this may not be at all feasible
23 June 2007 at 1:46pm
I agree that we should simplify the process of replacing on chart library with another where appropriate. But I caution against going too far down the 'abstraction layer' path - you can easily wind up having a hugely more complex system.
In particular, I would think that any given report would quite likely need to be designed/modified to make the best use of the chart library that it was designed for.
We should aim for something simple - wrapper classes for each library that operated in a similar way, where appropriate.
|Go to Top|