There are still many examples and areas of the docs that use the original plot_width and plot_height properties. We should update all of these to use width and height instead.

cc @tcmetzger

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

https://readthedocs.org/projects/chartify/builds/

It is currently a pain to use an OxyPlot.WinfowsForms.PlotView with a transparent background: it throws if you set its BackColor to transparent. To avoid this, it is necessary to set the ControlStyles.SupportsTransparentBackColor style to true on the PlotView; however, Control.SetStyle is protected, so consumers must resort to reflection or extending PlotView to do so. This could be

I think it could be useful, when one wants to plot only e.g. class 1, to have an option to produce consistent plots for both plot_cumulative_gain and plot_roc

At the moment, instead, only plot_roc supports such option.

Thanks a lot

I think it'd be nice to make holoviews work with Python sum().

sum([holoviews.Area(data=(x[num], y[num])) for num in range(8)]).cols(2)

This is currently raising an exception, since sum([area1, area2, area3, ...]) is equivalent to 0 + area1 + area2 + area3 (the 0 is the start in sum(iterable, /, start=0)). And Area (or other elements) __radd__ is not implemen

I don't think this is a duplicate ticket, even though it's quite an obvious feature after that cat demo at SciPy2018.

The code that selects and renders the different geos is here in the THREE.js code
https://github.com/maartenbreddels/ipyvolume/blob/master/js/src/scatter.js#L57

I don't know quite where/how to inject the mesh definition compatible with the data file of this form, but i

What is the feature ?

I'm trying out this library for the first time and I'm seeing several places where some shorthand functions would have been really pleasant:

1. Shorthand functions for Pos: Pos::top_right, Pos::bottom_right, Pos::bottom_center etc..
2. Short way to set colors for components. My plots are supposed to be white-on-black, which requires a lot of boilerplate on lots o

Matplotlib is able to handle canvas events https://matplotlib.org/stable/users/event_handling.html
Perhaps, after mouse clicking or panning the ticks handling could be delegated back to matplotlib?
So this could perhaps elimate the need in ticks=:native for pyplot backend

So that other people (like me) can help development of the interactive API. At the moment it is something alien that I Can just use through example. This is not the proper way forward...

(finally found Mouse in interaction/iodevices.jl...)

So as we start to see 1Hz soundings in the wild, we start to see issues with our calculations and the fact that sometimes pressure, as directly reported, is not necessarily monotonically decreasing. For instance, see this
sample sounding. There are a couple of spots where the pressure bounces up for a single point by 0.1 h