Giulio BERNA wrote:
Hi,
as Michael has said, there is now (almost) full support for bmps in fcl (it's missing PNG and JPEG images inside bmps: this is a feature available in win98+ that let you have a jpeg or png with a bmp header. I think it's not something very useful, but if someone wants it's easy to add support for these using jpeg and png readers inside bmp reader). I admit I haven't used lazarus a lot... When I started to make some work in fcl/image I thought that lazarus relied on fpimages to handle images, but when I peeked a little into lazarus sources I noticed something "strange". While there is a "Images for lazarus" package that relies on fpimage (but readme file says it must not be used because of bugs in jpeg implementation in fpimages... what are these bugs?), I saw that in intfgraphics there are things like "TLazBMPreader" that isn't a descendant of TFPBMPReader. TLazBMPreader has been copy-pasted from tfpbmpreader and has been modified (to solve endianess issues and to support 15 and 16 bit bitmaps). Why don't modify tfpbmpreader if there were problems, instead of copying it and modifying this copy?

The reason for this is not too difficult.
Lazarus and FPC are 2 seperate projects. When there are problems in a FPC library the first is to get it fixed there. But when it is fixed there, lazarus cannot use it yet. We don't want to force every lazarus user to update their fpc for every fix. So in order to provide new/fixed functionality things are sometimes copied to Lazarus.

Now bmp support in fcl is very complete, both in reading and writing. If you want you can use that instead of "reinvent the wheel" in intfgraphics.

Eh, yes. As you might have noticed, those improvements are just released. This doesn't meant that we will use then from day one. In the future we will probably use it. With my previous remark in mind, you will probably understand that those improvements arent shipped with a released FPC. As long as that is not the case, we need our own version.

Maybe there were other reasons that led to this choice (as I said, I know very little about lazarus). Another thing: png endianess issues in fpimage have been solved, so now it's usable even on big endian machines.

See previous remarks.

Marc

_________________________________________________________________
    To unsubscribe: mail [EMAIL PROTECTED] with
               "unsubscribe" as the Subject
  archives at http://www.lazarus.freepascal.org/mailarchives

Reply via email to