Original issue 36 created by eaburns on 2012-06-20T16:40:03.000Z:

You should be able to plot func(float64)float64 with a line style, sampled at some number of points along the range of the X axis.

Original issue 20 created by eaburns on 2012-06-13T19:34:47.000Z:

Currently, if ticks are drawn on the end of the axis then it doesn't make a nice 90 degree corner, instead you can see a wedge where they don't join correctly. The way to fix this is to draw ticks Axis.Width/2 longer so they go right to the top of the axis line.

Original issue 15 created by eaburns on 2012-06-07T16:31:58.000Z:

It doesn't need to be exported for any reason.

Original issue 25 created by eaburns on 2012-06-15T12:05:18.000Z:

If you don't add padding then the text for a nominal X axis slips beneath the Y axis and looks bad.

Original issue 37 created by eaburns on 2012-06-20T18:09:51.000Z:

People may want to do this and there is probably not trivial to figure out on ones own.

Original issue 17 created by eaburns on 2012-06-11T20:36:28.000Z:

Like GNU plot and others.

Original issue 26 created by eaburns on 2012-06-15T12:06:13.000Z:

This needs to be handled in the vg implementations.

Original issue 19 created by eaburns on 2012-06-12T19:53:15.000Z:

Instead of computing glyphBoxes for the top-most or right-most tick of the axes, the plot should figure out the squishing based on a bunch of things, including the existence of and size of title text and also the axis padding.

Currently plotutil uses the Color func to return a order set of colours for plots. Consider using a palette.Palette instead.

Issue of whether to take a Palette parameter or continue to use the current Color func.

Original issue 29 created by eaburns on 2012-06-15T15:39:34.000Z:

Currently, the tests don't really test anything. They are just used as a convenient way to look at sample plots as I code. There should be some actual tests.

This should be a relatively simple fix, just ensure that precisions agree along the entire axis (within reason).

Original issue 21 created by eaburns on 2012-06-13T19:38:10.000Z:

Add a *TextStyle field to Tick. If it is nil then use the Axis.Tick.Label.TextStyle, otherwise use the pointed to style.

Original issue 8 created by eaburns on 2012-06-04T17:55:31.000Z:

Currently everything is just a float64 and I keep forgetting various unit conversions. There should probably be a size type to prevent all of this.

Original issue 43 created by eaburns on 2012-07-30T23:40:43.000Z:

Make the logo an SVG file.

At the moment, a plot.GlyphBox represents a zero-sized point in the data space surrounded by an pair of offsets in the plot space. There is no way to represent the extent of glyphs that have a size dependent on the size of the plot.

This is due to the fact that the GlyphBoxes method is not passed any information regarding the plot area.

This can be fixed by adding a second pair of normalised x,y coordinates.

type GlyphBox struct {
    // The glyph location in normalized coordinates.
    MinX, MinY float64
    MaxX, MaxY float64

    // Rect is the offset of the glyph's minimum drawing
    // point relative to the glyph location and its size.
    Rect
}

The details of types etc need to be fleshed out.

Original issue 16 created by eaburns on 2012-06-11T20:35:11.000Z:

Figure out a good tick placement. We want no fewer than 3 major ticks.

Original issue 39 created by eaburns on 2012-06-21T12:22:19.000Z:

Currently plots always have a white background. We should allow this to be specified, and we should allow for no background color too.

Original issue 1 created by eaburns on 2012-05-23T12:02:01.000Z:

This is a nice and short name that, to me, conveys its low-levelness.

Original issue 24 created by eaburns on 2012-06-14T21:07:24.000Z:

If StrokeClippedLine is used for boxplots then they don't draw correctly even though their GlyphBoxes explicitly made room for them. Clipping needs to be re-thought.

Original issue 41 created by eaburns on 2012-07-28T01:24:49.000Z:

Some of the functions have changed.

Original issue 4 created by eaburns on 2012-05-23T12:03:27.000Z:

vecsvg should be an SVG implementation of vecgfx.

Original issue 6 created by eaburns on 2012-06-04T16:51:46.000Z:

For example, all of the drawing functions, GlyphBox, and possibly more do not need to be exported. The trade-off is allowing 3rd party extend-ability (a 3rd party package could implement a new plot element type) versus simplifying the visible portion of the plt interface.

Original issue 22 created by eaburns on 2012-06-13T20:08:37.000Z:

There is information (such as line width and font name) that is currently not configurable. Maybe GlyphStyle should be an interface?

Original issue 7 created by eaburns on 2012-06-04T17:42:15.000Z:

Try it.

Original issue 23 created by eaburns on 2012-06-14T19:45:50.000Z:

Try it

Original issue 32 created by eaburns on 2012-06-19T17:01:59.000Z:

makeAxis, NewLegend, anything making a font should return an error instead of panicing.

Original issue 5 created by eaburns on 2012-06-04T16:35:26.000Z:

Metric just makes more sense.

Original issue 10 created by eaburns on 2012-06-05T15:23:09.000Z:

Specifically, look at plt/draw.go

Original issue 9 created by eaburns on 2012-06-05T02:12:18.000Z:

Just merge its fields right into the Axis type.

Original issue 38 created by eaburns on 2012-06-21T12:20:38.000Z:

It's nice to have the number of tick marks computed by DefaultTicks change based on the size of the plot.

SPT (code.google.com/p/caml-spt) uses 1 major tick every 4cm, but no fewer than 2 major ticks, as its hint for how many ticks to attempt. IMGO, SPT sometimes uses too few ticks. Maybe 1 tick every 4cm, but no fewer than 3 would be good for Plotinum.

Original issue 12 created by eaburns on 2012-06-05T19:36:38.000Z:

Currently you cannot have multi-line text (plot title, axis label, and tick-labels; the latter is the most important). There should probably be a new Text object that handles multiple lines of text for which you can compute the various extents of the entire block.

This also requires thought about drawing the text centered, left, and right aligned and possibly justified, ick!

Original issue 30 created by eaburns on 2012-06-17T16:43:01.000Z:

Boxplots should be drawn as polygons instead of lines, barcharts will want to be polygons too. Also polygons would allow shading beneath or above lines.

@jonlawlor, would you do this, please.

Original issue 2 created by eaburns on 2012-05-23T12:02:43.000Z:

veceps should be an encapsulated postscript implementation of vecgfx.

Original issue 42 created by eaburns on 2012-07-28T01:25:50.000Z:

draw2d is broken with the latest freetype-go changes, thus vecimg doesn't compile and is commented out in the examples.

Original issue 40 created by eaburns on 2012-06-21T15:27:52.000Z:

You should be able to add labels to the plot at x,y locations.

Original issue 34 created by eaburns on 2012-06-20T16:30:56.000Z:

Should be able plot histograms.

Original issue 35 created by eaburns on 2012-06-20T16:31:20.000Z:

You should be able to make bar charts.

Original issue 18 created by eaburns on 2012-06-12T16:24:02.000Z:

E.g., what is the initial location of the cursor on a new Path?

Original issue 27 created by eaburns on 2012-06-15T12:06:40.000Z:

The don't seem to draw but let's be sure by explicitly avoiding them.

Palettes specify a list of colors. Strictly this is always a specific list, though may of the implemented palettes can create a long list of colors. These are being used at present to choose colors as part of Heatmaps and contours. In these cases, the z-axis values can be a real number, and a sort of interpolation function is being used to get the specific palette color. There are some special cases introduced, for example OverflowColor, which allow warning of specific colors.

In my mind, it's much better instead to have

// ColorFunc associates each float64 value with a color.Color
type ColorFunc func(float64) color.Color

A ColorFunc could use a palette as its underlying color choice. It could use a "threshholded palette", where it uses a palette for some intermediate range and uses warning colors outside of that range. There are many other possible uses, for example, returning a third warning color when the value is NaN, or having a grayscale image with a specific range of float64 returned as red to highlight their locations. It's much more powerful to have a function rather than just a palette with linear indexing, it's more composable because the special cases are located with the choice of color and not the choice of plotter, and (to me at least) it's more conceptually aligned with what's happening.

Original issue 3 created by eaburns on 2012-05-23T12:03:06.000Z:

vecpdf should be a PDF implementation of vecgfx.

Original issue 14 created by eaburns on 2012-06-05T19:38:30.000Z:

You cannot add legends to a plot yet.

image.Rectangle keeps to points, Min and Max and calculates Size from those. plot.Rect keeps a Min and a Size and calculates Max from those. It would be nice to have the two types speak with a similar accent.

Raised here.

Original issue 13 created by eaburns on 2012-06-05T19:37:21.000Z:

Currently you can't plot any data!

Original issue 11 created by eaburns on 2012-06-05T16:50:30.000Z:

stk5 suggests
p := Plot{X: Axis{"Time", 0,10}, Y: Axis{"Feet", 20, 42}}

Original issue 33 created by eaburns on 2012-06-20T16:30:27.000Z:

You should be able to add error bars to a plot.

A heatmap needs a colour scale in the legend. This means HeatMap needs to satisfy plot.Thumbnailer. There may be additional requirements, but this is the first step.

Original issue 28 created by eaburns on 2012-06-15T15:38:54.000Z:

There should be some example code for building plots.

Original issue 31 created by eaburns on 2012-06-17T21:29:01.000Z:

That makes FillText simpler and hides the details about alignment in the TextStyle.