Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

2016-07-21 Thread Todd Neal
On Wednesday, July 20, 2016 at 6:19:44 PM UTC-5, kristian wrote: > > I agree with this. Go needs a pdf library that is apache, mit or > bsd licensed. > Have you seen github.com/jung-kurt/gofpdf? I think the API is a bit wonky as it's derived from FPDF, but it works and uses the MIT license.

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

2016-07-20 Thread kristian
I agree with this. Go needs a pdf library that is apache, mit or bsd licensed. For a small commercial service where we don't want to share our own source code, AGPL prohibits use and the commercial license is probably not going to be affordable to a low-margin internet startup. It's weird t

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

2016-07-19 Thread Alfred Hall
Hi Eric. Thanks for the feedback. We are working with a lawyer to improve our LICENSE and make it easier to understand and hopefully cause less confusion. Cheers. Alf On Tue, Jul 19, 2016 at 12:38 AM, Eric Johnson wrote: > > On Monday, July 18, 2016 at 4:45:37 AM UTC-7, rog wrote: >> >> On 16

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

2016-07-18 Thread 'Eric Johnson' via golang-nuts
On Monday, July 18, 2016 at 4:45:37 AM UTC-7, rog wrote: > > On 16 July 2016 at 16:33, Daniel Theophanes > wrote: > > I would also note that AGPL is probably unusable in most Go programs > > (statically linked and all). -Daniel > > Why so? You just need to make your program open source, which

Re: [go-nuts] Re: [ANN] UniDoc PDF Toolkit for golang

2016-07-18 Thread roger peppe
On 16 July 2016 at 16:33, Daniel Theophanes wrote: > I would also note that AGPL is probably unusable in most Go programs > (statically linked and all). -Daniel Why so? You just need to make your program open source, which shouldn't be too onerous a requirement I'd've thought. -- You received t