Contribute analog and Bar Gauge widgets to dojox.widget

[Jared Jurkiewicz]

This is a contribution from IBM, a pair of GFX-based flexible gauge widgets for displaying of data. This contribution provides Analog style and bar style gauges that render well on a variety of browsers and support multiple indicators, where the indicators can use easings for animation of movement and so on.

The code work was done by Benjamin Schell (bmshell), and reviewed by Jared Jurkiewicz

[Jared Jurkiewicz]

Added in dojo.experimental for now.

[Jared Jurkiewicz]

(In [16003]) Cleanup/reorg of gagues stuff. refs #8064

[Jared Jurkiewicz]

(In [16004]) Cleanup/reorg of gagues stuff. refs #8064

[Jared Jurkiewicz]

(In [16005]) Cleanup/reorg of gauges stuff. refs #8064

[bill]

Also, please don't forget to move the code to dojox.charting before the 1.3 release. After the release it will be harder to move, or at least a lot more people will be upset about an "API change" (even though it's clearly marked as experimental). Thanks.

[Jared Jurkiewicz]

There was no agreement that it belongs in Charting. I still disagree with that, in fact. It is not a chart.

[Eugene Lazutkin]

It is almost like chart-like widgets like that belong to a separate category: they don't use (and don't need) the common infrastructure of the regular charts, their data API is totally different (e.g., consists of a single value), yet there are several of them, especially in finance (see #8216, which is similar to the bar gauge).

We can put them in a separate directory on dojox/charting/ or create a top-level project for them in dojox, but I think they should be separated from the rest of dojox widgets. Otherwise they will be indiscoverable by users who look for graphics solutions.

[Eugene Lazutkin]

And the bar gauge looks very similar to the bullet chart by Stephen Few. In fact a bunch of dashboard indicators will fall in the same category.

[Adam Peller]

I'd expect to find this stuff in dojox.widget. For starters, they are dijit._Widgets, but they are experimental and nobody has any right to complain if they are moved. I'm fine with refactoring this stuff, but based on what Eugene says, I'm not convinced lumping them in with the existing 'widgets' in Charting is the right answer either.

In the meantime, the widgets are in the codebase. Closing this ticket.

[Eugene Lazutkin]

Nobody ever suggested to lump them "with the existing 'widgets' in Charting" --- fighting windmills, aren't we? Could you shed a light on who did that "proposal"?