[poppler] Image optimization

[Albert Astals Cid]

A Divendres 20 Maig 2005 04:29, vàreu escriure:
> On Thu, May 19, 2005 at 11:02:35PM +0200, Albert Astals Cid wrote:
> > I disagree, keep for sure that if ever i get myself to use poppler for
> > future kpdf versions i'm not going to ask kde people to install cairo if
> > it is not absolutely necessary. And for now i don't see any reason more
> > than "we are uber cool and use the buzzworder cairo".
>
> cairo gives us transparency, 
Does this mean there are pdf with transparencies that do not work in Splash 
and work with Cairo? First time i hear that, if it is that way it's nice, can 
i have a pointer to such a pdf?

> anti-aliasing, 
As said before no idea this was working, can i see a pdf showing the 
difference between Splash and Poppler

> less code to be maintained  in poppler 
And therefore less power to make changes that may be good for poppler but bad 
for the general usage

> a nicer api. 
Splash API is completely thought to fit xpdf, i can not think how an API can 
be nicer than that.

> This isn't really any different than depending on zlib or libjpeg.
It is, zlib or libjpeg are much more simple and have a determined work to do, 
Cairo is much more "high level" and such it's goals may not always fit the 
ones poppler wants (as i said before)

> When I finish the getChar() -> read() conversion, I certainly 
> don't intend on optimizing the old flate/DCTstreams either.
>
> > No offense to cairo developers, it's a cool technology but it's a bit
> > much to ask people to install cairo instead of using splash when both
> > have a similar performance.
>
> Is it really that much to ask? The cairo library takes only 146k of
> diskspace and probably doesn't depend on anything that is not already on
> a kde system.
libpixman? Ok, ok, libpixman is small too :-D

> > Optimizing only cairo and not splash is
> > just another way of beign more gnomeish than kdeish.
>
> No, its way of minimizing changes to stable code, doing less work and
> encouraging the use of a backend that has more potential.

Well, imho as Carl said, it is because we are lacking a intermediate class 
that both CairoOutputdev and SplashOutputDev should inherit and that should 
contain that lot of non Cairo/Splash dependant code both clases have.

Albert

>
> -Jeff
___________________________________________________
Yahoo! Messenger - Nueva versión GRATIS
Super Webcam, voz, caritas animadas, y más...
http://messenger.yahoo.es