[Paraview-developers] Changing ColorMaps.xml format

[Utkarsh Ayachit]

Yes/+1 on all accounts. I think we can make the JSON more readable,
quite easily -- which would be good for the UserSettings.json too, in
any case.

On Tue, Apr 14, 2015 at 4:14 PM, David Thompson
<david.thompson at kitware.com> wrote:
> Hi Utkarsh,
>
>> I am looking at adding tracing support for loading color map presets.
>> When doing that,
>> I am also looking at extending the "presets" mechanism to support
>> saving/loading opacity transfer function (along with color) and other
>> things that may be important in preset. ...
>
> I am all for moving to JSON.
>
> 1. It would be nice to make "RGBPoints" an array of arrays rather than a flat array (for legibility and possibly to distinguish between 3-component RGB and 4-component RGBA).
>
> 2. Just making sure: you plan to continue supporting categorical values, so {"IndexedLookup": true} will work? (I do not see it in the example, but since the default would be false...)
>
> 3. The format of "Annotations" in your example is easy for a machine to parse but hard for a person. I don't object to it, but if the point is to let humans edit colormaps, may this would be better:
>
>   {
>   "Annotations" : [
>     {"value": "100", "label": "some"},
>     ...
>     {"value": "500", "label": "more"}
>    ]
>   }
>
>
>         David