|Think about Loose Coupling|
GIF patentby didier (Vicar)
|on Jun 18, 2003 at 20:01 UTC||Need Help??|
didier has asked for the
wisdom of the Perl Monks concerning the following question:
June 20, 2003 will be a beautiful day ! Because it's friday that expires the Unisys's patent over the GIF format.
GIF will be therefore royalties free in US, the licence will expire in France, Italy and Uk in one year, between June 15 and 20, 2004 according to countries.
Once upon the time there was a beautiful baby : the PNG format.
PNG has its pixels expressed in 24 bits while GIF only 8.
PNG is not a lossy compression technique while JPEG, well, yes.
However, as far as I know, nobody has been able to compile Tk::PNG under Win32. (Perl AS 5.5x, 5.6.x and 5.8).
Some of the bests fails
Is that also the case in this prestigious monastery ?
Some shoot under Win32 for some of you ?
Some success, O my God, some success ? How ?
If not what's yours thoughts about why it fails ?
And could we survive in a programming world where PNG under Win32 is the master sin ?
For Tk, under Win32, it means: the only way to describe complexity in a picture must be done through the XPM format (JPEG is 24 bits but some pixels will vanish).
Tk::Photo is able to read 24 bits format, like BMP 24b (internally the lib can use 32 bits per pixel) but it can output only 8 bits for BMP and Gif of course.
Note: the XPM format using the Tk'write() method output 24 bits if you want..
Handle XPM is tricky but can take a while.
Of course there is TIMTOWTDI, but GD is a 8 bits package, remains Image'Magick, Prima(? bits, writing capability ?), Wxperl (?) and Win32::Gui which allows BMP 24b (Writing with DIBitmap) but Tk::PNG is, of course, very best suited for the Tk environment
Win32 Tk users are still expecting 24 bits/pixel embedded in a lossless process.
If one of my dear fellow has already solved this problem, could this neural brother explains his method ?