This looks great. I tried to test it locally, but was unable to get the python setup.py updateplotlyjs with ""plotly.js": "github:plotly/plotly.js#cone-sizemode-vector"" to run, but I trust that this is implemented correctly.

I think a name like "constant-absolute" makes more sense from a end-user perspective. To be honest, I assumed that "absolute" would give me what I want - ignoring the internal factor and just using the value I give.

A name, or another alias that better gets that across would be great.

Edit: I got the command to run by adding "@jupyterlab/builder": "^4.1.5", and adding some lines to setup.py to deal with the branch-version instead of x.x.x version of plotly. Also my system didn't seem to install black or inflect so I added those as well with pip install.

But, it just doesn't seem to work from python (i.e. the new "vector" option is not there). I am definitely using my local plotly version, as without export PYTHONPATH=$PYTHONPATH:$(pwd)/plotly.py/packages/python/plotly:$(pwd)/plotly.py/packages/python/plotly-geo it fails.
Not sure where to go from here.

@Sharpz7 good point - TBH I’ve forgotten the rationale behind the original two modes and their names, but if we were designing the API today, the new version would probably have been called absolute. But we have a bit of a conundrum since that’s already taken.

@archmoj i haven’t played with this much, but if I’m understanding it correctly, absolute scales all the sizes up or down so they don’t intersect, leaving the ratios between different sized cones unchanged. Whereas scaled makes the largest cone the same size as absolute but the smaller ones may be larger than they would have been, so that you can still see their directions even if their real magnitudes are much smaller, is that right?

If I have that right, I might suggest raw as the name for the new one. That’s about the only word I can think of that implies “even less processed than absolute”