[FIX](CGG) Small fix to debugging code of generated CGG script files.
[CHG](dataSeparator) The option "dataSeparator" now also controls the pvc.data.Complex composite key separator, besides the crosstab translation separator character
[FIX](pvc.setDebug) pvc.logError and pv.error weren't being updated on debug level change
[FIX](protovis gradient OrdinalScale) Ordinal scales did not convert string ranges using pv.fillStyle but instead used pc.color. This caused a "colors" array containing gradient strings to not be correctly recognized.
[FIX](CCC Translation metadata.type) Reverted the use of metadata.type to default a single bound dimensions' type, because this would cause other relevant defaults not to be applied.
[FIX](protovis gradient multiple) Generally, multiple distinct gradients could render incorrectly, due to sharing of FillStyle/Color objects to store the multiple "color" urls that would refer to gradients defined in distinct parent elements. Urls would point to out-of-scope gradients. Now, all gradients are defined at the svg/defs element and are shared between FillStyles/Colors having the same key. There is no GC of gradients; it is assumed that the number of distinct gradients per root is relatively small, and that these are stable along consecutive renders.
Updated heat grid sample due ccc version update
[FIX](Dashboards._castControlToClass) While searching for the first of a set of candidate class names, ignore any global name whose value is not a function.
[FEAT](CCC Extension Scenes Legend Item) New kind of extension points: Scene Variables extension points.
Allow overriding the calculation of CCC scene variables. This is useful for things like changing the text of discrete ticks or legend items in a way that layout takes it into account. Normal "axisLabel_text" and "legendLabel_text" extension points are not taken into account by the automatic layout algorithms because they cannot be safely used in a context were protovis marks do not yet exist (as is the case). These are not suitable to be used when the size of panels is determined automatically.
In practice, for now, there's a single new extension point: "legendItemScene_value" (or "legend2ItemScene_value", ..., and "legend$ItemScene_value", for any legend group) that allows changing the label of the legend item's scene variable 'value'.
[CHG] Removed the new Legend Item Scenes extension point syntax and instead exposed the already existing JSON legend.scenes.item.value property.
[FIX](CCC scene var valueOf) removed the valueOf method, that would gain to the toString method, when returning a number.
PrptComponent: + usePost, autoResize
missing ;
TableComponent.update: exception was swept under the rug
PrptComponent: don't rely on page load for anything other than html/text
[FIX](CCC Waterfall) Bugs in ortho range calculation and water-group rectangles layout, sometimes revealed with the presence of negative values. There's still a bug with the placement of bars themselves.
[FIX](CCC def.string.format) Bug in evaluating toString of objects. If an object had a valueOf method, the toString of the result of valueOf would be used instead.
doQuery handles null parameters, fetchData shouldn't be picky
PrptComponent: don't persist inferred downloadMode
[FIX](CCC Waterfall WaterLineLabel-Placement) With negative values, water-line labels would sometimes be placed in the wrong position (above or below the line)
[FIX](protovis Band Layout) For the stacked mode, a JS bug, would mess up negative values and cause the bars to be wrongly placed, affected the CCC waterfall chart only.
SchedulePrptComponent in progress
SchedulePrptComponent
SchedulePrptComponent still in progress
SchedulePrptComponent html done, lacks css