Helmut Neemann

But you also need the axis width to calculate the marks. And if you only provide the font, you also need to know whether the axis is horizontal or vertical....

@kortschak Perhaps you're right. But to me, implementing this interface feels like answering the question "How many letters fit in this line?" and neither knowing the length of the line...

> Sometimes, you just need a human. This is not an option if you don't have an interactive system to design the plot, but the plot is created in a...

I've tried that, but it turns out to be quite messy. The current design makes it difficult to access the required dimensions. I rather stay with the fork that I...

Yep, that was also my problem: I could not access the canvas. But passing the canvas to the `Ticks` method, or the appropriate `func(x float64) vg.Length` function of the canvas...

What about something like this: ``` go type RenderContext struct { Axis Axis Orientation bool Canvas Canvas } type Ticker interface { // Ticks returns Ticks in the specified range...

> Fundamentally, the API change breaks a design decision that was made when the plot package was originally written, that the data side and the rendering side of plotting are...

To be honest, I don't get it! As I understand it, the `Normalizer` stored in the `Scale` field only returns values between 0 and 1. The `X` and `Y` functions...

Or you simply add a new property to the Axis struct. Say `AxisLength vg.Length` This would break no existing code. But you have to update this field every time `ticker.Ticks`...

So you are thinking about something like this? ``` go type impl struct { } func (i impl) Ticks(min, max float64) []plot.Tick { return nil } func (i impl) SetAxis(axis...