Christopher Davis

In case it's helpful, here are two short offset examples that I put together a few months ago: https://github.com/ChristopherDavisUCI/altair/commit/af0c3b4c1d27c366fb66fb6743aa15d5d30a56ce

Hi @mattijn, in the lines you identified in the other PR, if we add an `elif` condition so they become ```python if self.param.expr is Undefined: return {"expr": self.name} elif isinstance(self.param.expr,...

I think my question about which `"expr"` we want is very related to your "we don't need to add the parameter" comment. Of course if we use ```json "thetaOffset": {...

Could you post an example of how you make the above parameter using `from altair.expr import X, Y, Z`? My memory is a little fuzzy, but I remember trying to...

@jakevdp do you agree with @mattijn's suggestion, that `theta_shift_as_par` (as defined below) should serialize using the parameter name, as in `"expr": "parameter027"`, and that `theta_shift_as_expr` should serialize so that the...

I'm a little stuck with how to proceed @mattijn @jakevdp @joelostblom Say we define a parameter like @mattijn did above ```python theta_shift = alt.parameter(expr=(-PI/length(data('source_wind')))) ``` There is currently no real...

Hi @mattijn I made an attempt to resolve these issues in #2591. Please take a look and let me know any comments!

Thanks for bringing this up @mattijn. I'm pretty confident we can control this on the Altair end, so I think it's just a matter of having a clear idea of...

Thanks again for bringing this up @mattijn! I'm hopeful that whatever we want to do will be easy to accomplish. I think the difficult part is deciding what we're supposed...

My vote is that `c.add_parameter` should only add to the given chart `c`, and not add to all sub-charts. I feel like this is what will be easiest to maintain....