You are probably right about go get. I was pulling the repos into my
workspace so I could check out the code more easily. That, plus just
informing the user as to what is involved, is why you might want to list
dependencies.
Gradients are coming soon to oksvg.
On Monday, May 7, 2018 at 6:33:10
>
> I’m pretty sure you can just type "go get …” and it finds all the
> dependencies automatically, and they are likely to change over time, so I’m
> not sure it is conventional to list them?
You may want to vendor them
(https://golang.org/cmd/go/#hdr-Vendor_Directories) so if they ever go aw
On May 5, 2018, at 8:38 AM, matthewju...@gmail.com wrote:
> In a generic container I would expect to see items typed as interface{} and
> the behavior defined on a slice of interface{} or struct with private slice
> of interface{} field.
>
> From the godoc it looks like type Node implements type
Steve — thanks for your impressions. I’ll definitely contact you directly when
I get around to trying to integrate rasterx — I haven’t even had a chance to
look at it all, but a first question is when you expect it to be stable and
reasonably feature-complete? e.g., one of the main things I wo
On Fri, 4 May 2018 04:39:06 -0600
Randall O'Reilly wrote:
> https://github.com/goki/goki — key demo in:
> https://github.com/goki/goki/tree/master/gi/examples/widgets
>
> This is the first release of a new Go framework built around the Tree as a
> core data structure (Ki = Tree in Japanese),
Ha
