[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KImgio (Was: App start is too slow)
From:       Waldo Bastian <bastian () kde ! org>
Date:       2000-04-29 19:28:49
[Download RAW message or body]

On Sat, 29 Apr 2000, Stephan Kulow wrote:
> Waldo Bastian wrote:
> > Ok.
> >
> > I have done the following (not commited yet).
> >
> > * I moved kimgio.[cpp|h] to kio.
> > * kimgio loads additional libs only when needed
>
> How?

It registers a dummy QImage read/write function. When it gets called it 
checks the required format, loads any additional lib if not already done so, 
and calls kimgio_<FORMAT>_read() or kimgio_<FORMAT>_write() in this lib.

> > * *.kimgio files define all available image types and whether additional
> > libs need to be loaded.
>
> Well, better call them kimg_*.desktop I'd say

I thought of that but the information stored in the files does not match with 
the information stored in typical .desktop files. So since they are different 
by their very nature, why pretend that they are the same by giving them the 
same name.

> > * The *.kimgio files are stored in ksycoca to access them faster.
> > (Startup is now a wopping 37ms faster.)
> >
> > My questions:
> > * What would be a good place to store the *.kimgio files? I currently
> > store them in $KDEDIR/lib, but I don't think that is the best place for
> > them.
>
> Hmm, /lib are libs :)
> how about share/apps/kimgio?

kimgio is not an application. I now store them in share/services/. 
I think our protocol defintion files (http.desktop) belong there as well.
(With an extension other than .desktop for the same reason)

> > * kdelibs/kimgio seems not very well maintained. It looks like only
> > "EPS", "KRL", "TIFF" and "XView" make sense. "EPS" didn't work for me.
> > What is "KRL"?
>
> Ask Antonio:
> date: 1999/05/07 18:13:50;  author: antlarr;  state: Exp;
> Adding support to read krl files (just before anyone asks, it's used
> in mammographies and high resolution scanners, so it's just for labs.
> and people working with this kind of things).
>
> Sounds quite misc to me - but if it's only loaded on demand, it should
> be fine.
>
> > * JPG is part of Qt right? So kimg_jpeg.la is obsolete, correct?
>
> Guess so
>
> > * With my change $LIB_KIMGIO would be obsolete. kdelibs/kimgio would
> > contain
>
> Well, is that binary compatible? ;-)

No not really, applications start to complain they can't find libkimgio.la.

This convinced me to break source compatibility as well by renaming 
"kimgio.h" to "kimageio.h" since it defines "KImageIO".

I guess I now need approval from the release-meister :-)

Cheers,
Waldo

[prev in list] [next in list] [prev in thread] [next in thread]