[poppler] Understanding the rendering pipeline
Albert Astals Cid
aacid at kde.org
Thu Oct 22 13:21:16 PDT 2009
A Dijous, 22 d'octubre de 2009, Tuom Larsen va escriure:
> On Sun, Oct 18, 2009 at 10:57 PM, Albert Astals Cid <aacid at kde.org> wrote:
> > > buffer?
> > >
> > > What I don't get is how and where are the operators rendered to the
> > memory
> > Well, each of the commands get called and this goes through the outputdev
> > that
> > "draws" things
> > > How gets a page state transformed to pixels?
> > By commands like "draw line"
> > > Is there performed a binary search for every command in pdf?
> > Yes, but it's actually cheap so don't bother optimizing that it'll give
> > you a
> > 0.00000001% performance boost at most.
> thanks for the reply!
> If I understood correctly: in PDF, say there are 1000 lines. Is the binary
> search for outputdev's appropriate callback called 1000 times? I thought
> there is some kind of cache (this is what I was trying to find in the
> source) but you are saying that it is fast enough? Is this correct?
Compared to the cost of actually rendering the line, yes, O(log(N)) where N is
< 200 is cheap
> Thanks for the info, once more!
More information about the poppler