Hi,
I'm having a few problems with javascript rendered charts using 3.2.1 paid. First of all I'm trying to use the ScrollColumn2D called with the FusionCharts.render compact function. The json url for testing is a local file as follows:
{
"chart": {
"caption": "Missed & Blocked Visits",
"yaxisname": "Number of Visits",
"numvisibleplot": "2",
"plotspacepercent": "0"
},
"categories": [
{
"category": [
{
"label": "Test 2"
},
{
"label": "Test 1"
}
]
}
],
"dataset": [
{
"seriesname": "Number of Missed Visits",
"data": [
{
"value": "82"
},
{
"value": "77"
}
]
},
{
"seriesname": "Number of Blocked Visits",
"data": [
{
"value": "76"
},
{
"value": "52"
}
]
}
]
}
Questions:
1. numvisibleplot doesn't seem to work. I can't get this chart to scroll at all with javascript rendering. In the documentation JavaScript Charting Capabilities some of the scroll Equivalent JavaScript Chart are listed with (non scroll) but not ScrollColumn2D so I'm assuming it's supposed to support scrolling?
2. Actually I'd really prefer to use ScrollCombiDY2D but it's not supported with scroll in javascript. Is there a timeline for providing support for these remaining chart types?
3. plotspacepercent doesn't seem to work. How can I reduce the gap between the columns?
4. Is the json setup as fully functional as the xmlURL setup? We manage the backend so can use either. Would you recommend on over the other at this stage?
5. When rendered with javascript I can't get the x-axis labels to not display slanted. I've seen a work around for this in the forum. Can you please advise how to fix this using the compact render call?
6. Can't get the legend to display on javascript pie charts. I've seen this reported in the forum. Is the a timeframe for an update on this?
7. Is it possible to employ highchart parameters which are not supported in the fusion api? For example the high chart doughnut supports inner rings. Is this functionality accessible through the fusion wrapper?
As a general comment we're really only interested in using javascript rendered charts moving forward. We're now using a javascript framework to provide web-application type interfaces. This requires HTML5 so we don't wish to also require our users have flash installed or supported on thier system. I'd encourage you to continue to expand javascript rendered support and include widgets and maps.