Re: Using/requiring Cairo

On 06/26/2017 02:36 PM, David Kastrup wrote: Interestingly, "Cairo uses hardware acceleration when available." Well, to be fair this just concerns display backends. So it might be interesting for Denemo and Frescobaldi interfacing but will not otherwise affect output. I think it would be

Re: Using/requiring Cairo

Paul writes: > I can't speak to the technical questions, but I see the appeal of this > idea. Cairo looks like a mature, well-supported, and widely-used > library. One side effect is that most free software PDF viewers use Cairo for their rendering these days, so if we

Re: Using/requiring Cairo

Paul writes: > I can't speak to the technical questions, but I see the appeal of this > idea. Cairo looks like a mature, well-supported, and widely-used > library. > > https://en.wikipedia.org/wiki/Cairo_%28graphics%29 > > Interestingly, "Cairo uses hardware acceleration >

Re: Using/requiring Cairo

I can't speak to the technical questions, but I see the appeal of this idea. Cairo looks like a mature, well-supported, and widely-used library. https://en.wikipedia.org/wiki/Cairo_%28graphics%29 Interestingly, "Cairo uses hardware acceleration

Re: Using/requiring Cairo

k...@aspodata.se writes: > David Kastrup: > ... >> I don't see myself able to deal with all potential icky graphics code >> in LilyPond, and I don't see anybody else stepping up either. > ... > > Just for the record, I'm interested in icky graphics code. There is no shortage in LilyPond and I

Re: Using/requiring Cairo

On Sun, Jun 25, 2017 at 2:05 PM, David Kastrup wrote: >> I would be much more supportive if you could show some numbers where >> memory/CPU is used right now, and could show some data how much Cairo >> would improve on things. It's quite possible that you are right, but >> then it

Re: Using/requiring Cairo

David Kastrup: ... > I don't see myself able to deal with all potential icky graphics code in > LilyPond, and I don't see anybody else stepping up either. ... Just for the record, I'm interested in icky graphics code. Regards, /Karl Hammar

Re: Using/requiring Cairo

David Kastrup: ... > Han-Wen Nienhuys writes: ... > > I would be much more supportive if you could show some numbers where > > memory/CPU is used right now, and could show some data how much Cairo > > would improve on things. It's quite possible that you are right, but > > then

Re: Using/requiring Cairo

Just responding to a minor point: Han-Wen Nienhuys writes: > I suppose that functions like > > https://www.cairographics.org/manual/cairo-Paths.html#cairo-path-extents > > would be a boon. > > I was tickled to reply to your mail, because it was full of complaints >

Re: Using/requiring Cairo

Han-Wen Nienhuys writes: > On Sat, Jun 24, 2017 at 5:54 PM, David Kastrup wrote: >> Han-Wen Nienhuys writes: >> >>> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: The first step would likely just involve

Re: Using/requiring Cairo

On Sat, Jun 24, 2017 at 5:54 PM, David Kastrup wrote: > Han-Wen Nienhuys writes: > >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >>> What does that mean? Mainly a viable migration strategy where we might >>> be able to drop catering

Re: Using/requiring Cairo

k...@aspodata.se writes: > David >> k...@aspodata.se writes: > My point was: >> > Though, my conclusion was that pdf is not better than ps regarding >> > postprocessing, and yes I know that pdf (depending on pdf version) has >> > some features that ps don't have. >> >> But nobody is talking

Re: Using/requiring Cairo

David > k...@aspodata.se writes: > > Werner: ... > >> > And my interest was in reading pdf's, so I can write programs to > >> > extract the info I want from pdf's. > >> > >> Have you tried `pdftk' to uncompress a PDF file? It's then almost as > >> readable as a plain PS file (see attachments). >

Re: Using/requiring Cairo

k...@aspodata.se writes: > Werner: >> >> "taking care of PostScript" is not related to converting LilyPond's >> >> graphics internals to Cairo since LilyPond's graphics internals are >> >> not written in PostScript. >> > >> > Ok, forget it then, you are not listening. [...] >> >> Why such a

Re: Using/requiring Cairo

Werner: > >> "taking care of PostScript" is not related to converting LilyPond's > >> graphics internals to Cairo since LilyPond's graphics internals are > >> not written in PostScript. > > > > Ok, forget it then, you are not listening. [...] > > Why such a hostile tone, Karl? There is no

Re: Using/requiring Cairo

>> "taking care of PostScript" is not related to converting LilyPond's >> graphics internals to Cairo since LilyPond's graphics internals are >> not written in PostScript. > > Ok, forget it then, you are not listening. [...] Why such a hostile tone, Karl? There is no reason for this. I have

Re: Using/requiring Cairo

David Kastrup: > k...@aspodata.se writes: > > David Kastrup: ... > "taking care of PostScript" is not related to converting LilyPond's > graphics internals to Cairo since LilyPond's graphics internals are not > written in PostScript. Ok, forget it then, you are not listening. ... > When

Re: Using/requiring Cairo

k...@aspodata.se writes: > David Kastrup: >> k...@aspodata.se writes: >> >> > Han-Wen Nienhuys: >> >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > ... >> > If no one else like to care for postscript, I can step in to handle it. >> >> I don't know what that means. > >

Re: Using/requiring Cairo

David Kastrup: > k...@aspodata.se writes: > > > Han-Wen Nienhuys: > >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: ... > > If no one else like to care for postscript, I can step in to handle it. > > I don't know what that means. It's like english, I am willing to take

Re: Using/requiring Cairo

k...@aspodata.se writes: > Han-Wen Nienhuys: >> On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >> > What does that mean? Mainly a viable migration strategy where we might >> > be able to drop catering for a whole lot of graphics programming >> > ourselves by introducing a

Re: Using/requiring Cairo

Han-Wen Nienhuys: > On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > > What does that mean? Mainly a viable migration strategy where we might > > be able to drop catering for a whole lot of graphics programming > > ourselves by introducing a dependency on Cairo. I am not

Re: Using/requiring Cairo

David Kastrup: ... > The main question mark would concern font handling > but I think it integrates with FreeType as well as Pango. ... cairo has support for freetype https://cairographics.org/manual/cairo-FreeType-Fonts.html pango has support for cairo:

Re: Using/requiring Cairo

Han-Wen Nienhuys writes: > On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: >> What does that mean? Mainly a viable migration strategy where we might >> be able to drop catering for a whole lot of graphics programming >> ourselves by introducing a

Re: Using/requiring Cairo

On Sat, Jun 24, 2017 at 12:43 PM, David Kastrup wrote: > What does that mean? Mainly a viable migration strategy where we might > be able to drop catering for a whole lot of graphics programming > ourselves by introducing a dependency on Cairo. I am not overly what "catering for

Re: Using/requiring Cairo

Werner LEMBERG writes: >> The first step would likely just involve moving to Cairo data >> structures while keeping most of the current code except where the >> code would duplicate Cairo API calls in a reasonably straightforward >> way. > > Sounds very sensible. Looking around

Re: Using/requiring Cairo

> The first step would likely just involve moving to Cairo data > structures while keeping most of the current code except where the > code would duplicate Cairo API calls in a reasonably straightforward > way. Sounds very sensible. Looking around for other PDF generation libraries, we don't