Thomas Fletcher écrit:
> On Tue, 17 Apr 2001, Hubert Figuiere wrote:
>
>> I'm about to finish JPEG import for Abiword, using libjpeg to do the
>> magic. Does anybody find any objection using libjpeg ? (see bug 1292
>> <http://bugzilla.abisource.com/show_bug.cgi?id=1292>)
>>
>> As for the Mac platform, I say OK. But for the others ?
>
> Where do we draw the line on what we load? I hate this
> incremental "add this lib, add this lib, add this lib" since
> we just get bigger and bigger and bigger. Having one
> guaranteed format for import (png) and then using system
> services (translators on BeOS, imaging library on QNX etc)
> would be my recommendation. I know that we already have
> BMP support finangled in there (the defacto windows standard,
> what can I say about it) but it doesn't please me.
BTW I'd like push for JPEG internal support. Why ? Just because I can't
imagine manipulating JPEG photographies in PNG and store them as such.
Having JPEG import within XP code is IMHO not a bad thing. BeOS as libjpeg
built-in. Gnome build already links against LibJPEG (haven't cheked for
GTK). So what is the problem ? Is it difficult for QNX ?
So I'll have to make it a platform switch.
On the otherside, I'm OK to make platform specific importers. For example,
for the Mac port, I planned to do a QT Graphics importer. That would have
brought dozen of picture format for free.
> If I had a thing to say about it, I would say make it a
> loadable module (and consequently make loadable modules
> work properly) but don't force it to be present.
Oh yes. I vote for this one, even if it costs me more time for the MacOS
port. Dom provided some infrastructures. What are we waiting for this ?
> AbiWord ... 3M and growing fast
I actually waste more than 30 Min each time I rebuild completely Abiword.
And linking on my poor Linux laptop is over several minutes... in debug
mode.
Hub
--
Lead developer on libcwk
<http://sourceforge.net/projects/libcwk/>
