Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

I've tested the latest version of oksvg, which has support for more elements, and thus I can test with more SVG files in the codepicdeck collection [1] The tests compare four rendering methods, on my MacBook Pro, MacOS 10.13.4, 2.3 GHz Intel Core i7, 16GB. 1) oksvg using GV (svgpng.go) [2] 2)

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Thanks. I just fixed a bug 2 minutes ago that I introduced while refactoring, so you probably want to pull the new version. (Thanks to Anthony Starks for pointing it out.) On Saturday, April 28, 2018 at 1:21:41 PM UTC-7, Daniel Theophanes wrote: > > Thank you for looking into this! This looks gr

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Thank you for looking into this! This looks great! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, vis

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Hey everyone, I looked into using just the rasterizer package from the "golang.org/x/image/vector" package and tested it vs the rasterizer derived from the freetype package. I will call these the GV and FT rasterizers. One thing with the GV is that it only does non-zero-winding-rule, while the

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

> > So it sounds like the AGPL is a good license to choose if you want to keep > your code from being used by big companies… ;-) If your project is secret software with a public network interface then don’t apply the AGPL to it. That’s not the only kind of software used at big companies. Mat

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

So it sounds like the AGPL is a good license to choose if you want to keep your code from being used by big companies… ;-) > On Apr 25, 2018, at 8:48 AM, 'David Chase' via golang-nuts > wrote: > > > > On Tuesday, April 24, 2018 at 10:45:35 AM UTC-4, matthe...@gmail.com wrote: > I’m curious i

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

On Tuesday, April 24, 2018 at 10:45:35 AM UTC-4, matthe...@gmail.com wrote: > > I’m curious if some companies juggle the GPL. I guess if the app is used > internally only then there’s no problem with accidentally requiring a > proprietary program to be released as source code to the world. I’d

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

> I’d have thought the case would be the same with the AGPL. https://opensource.google.com/docs/using/agpl-policy/ -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email t

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

I’m curious if some companies juggle the GPL. I guess if the app is used internally only then there’s no problem with accidentally requiring a proprietary program to be released as source code to the world. I’d have thought the case would be the same with the AGPL. Do people count as individual

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

On Tuesday, April 24, 2018 at 9:38:36 AM UTC-4, matthe...@gmail.com wrote: > > For Go you may want to consider the AGPL which also requires any network >> app to provide its source code. These GNU licenses are from the Free >> Software Foundation which has a traditionally radical philosophy towar

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

> > On the other hand oksvg is completely de novo, so I can slap whatever > license I want on that package. I take it people here prefer the Go > license? Can anyone briefly describe the difference? I will definitely > change it if someone can give me a good reason. I just want to make it as

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

The freetype license looks it's a BSD derivative. That license would be more consistent with the static linking used by gc, so since you can choose either the freetype license or the GPL 2+, if it's not against your ideals, the FTL is probably the better choice. Note that because oksvg imports rast

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Thanks for the compliments, everyone. I will check out the vector package and further test SVG examples are welcome. If I have isolated concepts as well as I hope I have, re-writing the Scanner to use the vector package might not be too hard. Gradients are also near the top of the to-do list,

Re: [go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Nice! On Mon, Apr 23, 2018 at 3:41 AM, Steven Wiley wrote: > I refactored and enhanced the raster package from the golang translation > of freetype, > It'd be a bunch of work, but you might consider basing off of golang.org/x/image/vector instead: 1. Its

[go-nuts] [ANN] oksvg and rasterx; SVG 2.0 path compliant renderer and rasterizer

Hi all, I needed to write an SVG renderer; something that draws an SVG file onto an image (not to be confused with an SVG generator such as SVGo). I wanted to do this in native go, and not rely on wrapping pre-existing C code. The golang 2D drawing packages I could find were not capable of ren