update pie plugin: add ability to use given radius

[bor]

radius can be passed in data[i].radius
no impact on existing code (compatible)

would be nice if you accept this commit
it allow us to create another type of chart (based on pie plugin)
with minimal code ;)

for example https://github.com/bor/flot.polar_bar

[bor]

here you can review examples polar bar plugin (not work as expected yet)
http://bor.github.com/flot.polar_bar/examples/
and how it should look after this commit
http://bor.github.com/flot.polar_bar/examples/example_page.png

[dnschnur]

I like this idea a lot; rose plots are attractive and a natural fit for the pie plugin. I wonder whether adding a new option is the right approach, though. What you really have is two-dimensional data; it seems like it would be more natural to use a second data value instead.

This requires a lot more work, since you need to mess around with the processDatapoints hook, detect when these secondary values are provided, etc. But it feels like a better design, since those values are really part of the data, not a separate option. What do you think?

[bor]

Yes, it is a good idea too.
I can do this if you don't mind.
But the question is: how it should named? I mean option name(s).

[seanpoulter]

Have you made any progress @bor?

@dnschnur, have you gave the structure of the data series for these any thought? I've just spent a while thinking about a clean way to balance the data structures to supporting both multi-level pie/stacked wedge graphs and rose/polar area graphs and would like to know what you had in mind before I get too far.

Please do let me know where things are at, otherwise I'll continue updating the supporting functions to work with my quick hack for drawSlice(angle, color, fill) to use a start/end angle and radius to draw slices.

[bor]

AFAIU the pull request was no merged :(
And at the moment it not compatible with current codebase, so need to review it again.

[bor]

Seems like 'rebasing' helps.

[sahilthapar]

+1