2010-07-31 06:52:47 +04:00
|
|
|
#
|
|
|
|
# The Python Imaging Library.
|
|
|
|
# $Id$
|
|
|
|
#
|
|
|
|
# FLI/FLC file handling.
|
|
|
|
#
|
|
|
|
# History:
|
|
|
|
# 95-09-01 fl Created
|
|
|
|
# 97-01-03 fl Fixed parser, setup decoder tile
|
|
|
|
# 98-07-15 fl Renamed offset attribute to avoid name clash
|
|
|
|
#
|
|
|
|
# Copyright (c) Secret Labs AB 1997-98.
|
|
|
|
# Copyright (c) Fredrik Lundh 1995-97.
|
|
|
|
#
|
|
|
|
# See the README file for information on usage and redistribution.
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
|
|
__version__ = "0.2"
|
|
|
|
|
2013-03-07 20:20:28 +04:00
|
|
|
from PIL import Image, ImageFile, ImagePalette, _binary
|
2010-07-31 06:52:47 +04:00
|
|
|
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
i8 = _binary.i8
|
|
|
|
i16 = _binary.i16le
|
|
|
|
i32 = _binary.i32le
|
|
|
|
o8 = _binary.o8
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
#
|
|
|
|
# decoder
|
|
|
|
|
|
|
|
def _accept(prefix):
|
|
|
|
return i16(prefix[4:6]) in [0xAF11, 0xAF12]
|
|
|
|
|
|
|
|
##
|
|
|
|
# Image plugin for the FLI/FLC animation format. Use the <b>seek</b>
|
|
|
|
# method to load individual frames.
|
|
|
|
|
|
|
|
class FliImageFile(ImageFile.ImageFile):
|
|
|
|
|
|
|
|
format = "FLI"
|
|
|
|
format_description = "Autodesk FLI/FLC Animation"
|
|
|
|
|
|
|
|
def _open(self):
|
|
|
|
|
|
|
|
# HEAD
|
|
|
|
s = self.fp.read(128)
|
|
|
|
magic = i16(s[4:6])
|
2012-12-21 09:47:45 +04:00
|
|
|
if not (magic in [0xAF11, 0xAF12] and
|
|
|
|
i16(s[14:16]) in [0, 3] and # flags
|
2013-03-08 17:01:56 +04:00
|
|
|
s[20:22] == b"\x00\x00"): # reserved
|
2012-10-11 07:52:53 +04:00
|
|
|
raise SyntaxError("not an FLI/FLC file")
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# image characteristics
|
|
|
|
self.mode = "P"
|
|
|
|
self.size = i16(s[8:10]), i16(s[10:12])
|
|
|
|
|
|
|
|
# animation speed
|
|
|
|
duration = i32(s[16:20])
|
|
|
|
if magic == 0xAF11:
|
|
|
|
duration = (duration * 1000) / 70
|
|
|
|
self.info["duration"] = duration
|
|
|
|
|
|
|
|
# look for palette
|
2012-10-16 05:58:46 +04:00
|
|
|
palette = [(a,a,a) for a in range(256)]
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
s = self.fp.read(16)
|
|
|
|
|
|
|
|
self.__offset = 128
|
|
|
|
|
|
|
|
if i16(s[4:6]) == 0xF100:
|
|
|
|
# prefix chunk; ignore it
|
|
|
|
self.__offset = self.__offset + i32(s)
|
|
|
|
s = self.fp.read(16)
|
|
|
|
|
|
|
|
if i16(s[4:6]) == 0xF1FA:
|
|
|
|
# look for palette chunk
|
|
|
|
s = self.fp.read(6)
|
|
|
|
if i16(s[4:6]) == 11:
|
|
|
|
self._palette(palette, 2)
|
|
|
|
elif i16(s[4:6]) == 4:
|
|
|
|
self._palette(palette, 0)
|
|
|
|
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
palette = [o8(r)+o8(g)+o8(b) for (r,g,b) in palette]
|
2012-10-24 17:25:00 +04:00
|
|
|
self.palette = ImagePalette.raw("RGB", b"".join(palette))
|
2010-07-31 06:52:47 +04:00
|
|
|
|
|
|
|
# set things up to decode first frame
|
|
|
|
self.frame = -1
|
|
|
|
self.__fp = self.fp
|
|
|
|
|
|
|
|
self.seek(0)
|
|
|
|
|
|
|
|
def _palette(self, palette, shift):
|
|
|
|
# load palette
|
|
|
|
|
|
|
|
i = 0
|
|
|
|
for e in range(i16(self.fp.read(2))):
|
|
|
|
s = self.fp.read(2)
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
i = i + i8(s[0])
|
|
|
|
n = i8(s[1])
|
2010-07-31 06:52:47 +04:00
|
|
|
if n == 0:
|
|
|
|
n = 256
|
|
|
|
s = self.fp.read(n * 3)
|
|
|
|
for n in range(0, len(s), 3):
|
py3k: The big push
There are two main issues fixed with this commit:
* bytes vs. str: All file, image, and palette data are now handled as
bytes. A new _binary module consolidates the hacks needed to do this
across Python versions. tostring/fromstring methods have been renamed to
tobytes/frombytes, but the Python 2.6/2.7 versions alias them to the old
names for compatibility. Users should move to tobytes/frombytes.
One other potentially-breaking change is that text data in image files
(such as tags, comments) are now explicitly handled with a specific
character encoding in mind. This works well with the Unicode str in
Python 3, but may trip up old code expecting a straight byte-for-byte
translation to a Python string. This also required a change to Gohlke's
tags tests (in Tests/test_file_png.py) to expect Unicode strings from
the code.
* True div vs. floor div: Many division operations used the "/" operator
to do floor division, which is now the "//" operator in Python 3. These
were fixed.
As of this commit, on the first pass, I have one failing test (improper
handling of a slice object in a C module, test_imagepath.py) in Python 3,
and three that that I haven't tried running yet (test_imagegl,
test_imagegrab, and test_imageqt). I also haven't tested anything on
Windows. All but the three skipped tests run flawlessly against Pythons
2.6 and 2.7.
2012-10-21 01:01:53 +04:00
|
|
|
r = i8(s[n]) << shift
|
|
|
|
g = i8(s[n+1]) << shift
|
|
|
|
b = i8(s[n+2]) << shift
|
2010-07-31 06:52:47 +04:00
|
|
|
palette[i] = (r, g, b)
|
|
|
|
i = i + 1
|
|
|
|
|
|
|
|
def seek(self, frame):
|
|
|
|
|
|
|
|
if frame != self.frame + 1:
|
2012-10-11 07:52:53 +04:00
|
|
|
raise ValueError("cannot seek to frame %d" % frame)
|
2010-07-31 06:52:47 +04:00
|
|
|
self.frame = frame
|
|
|
|
|
|
|
|
# move to next frame
|
|
|
|
self.fp = self.__fp
|
|
|
|
self.fp.seek(self.__offset)
|
|
|
|
|
|
|
|
s = self.fp.read(4)
|
|
|
|
if not s:
|
|
|
|
raise EOFError
|
|
|
|
|
|
|
|
framesize = i32(s)
|
|
|
|
|
|
|
|
self.decodermaxblock = framesize
|
|
|
|
self.tile = [("fli", (0,0)+self.size, self.__offset, None)]
|
|
|
|
|
|
|
|
self.__offset = self.__offset + framesize
|
|
|
|
|
|
|
|
def tell(self):
|
|
|
|
|
|
|
|
return self.frame
|
|
|
|
|
|
|
|
#
|
|
|
|
# registry
|
|
|
|
|
|
|
|
Image.register_open("FLI", FliImageFile, _accept)
|
|
|
|
|
|
|
|
Image.register_extension("FLI", ".fli")
|
|
|
|
Image.register_extension("FLI", ".flc")
|