-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO
74 lines (54 loc) · 2.2 KB
/
TODO
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
TODO file for PEL: PHP Exif Library. A library with support for
reading and writing Exif headers in JPEG and TIFF images using PHP.
Copyright (C) 2004, 2005, 2006 Martin Geisler.
Licensed under the GNU GPL, see COPYING for details.
TODO List for PEL
*****************
In addition to the following list, then the source contains a number
of comments beginning with `TODO' and `FIXME' which marks extra places
where attention is needed.
The list has been roughly ordered by priority and the release
targeted.
PEL Version 1.0
---------------
* Add convenience functions.
It would be nice to have functions that could give you a particular
entry or the embedded thumbnail with just one function call.
Manually traversing the directory structure (and repeatedly
checking for null pointers) requires too big a knowledge of the
structure of JPEG, TIFF, and Exif formats.
PEL Version 1.x
---------------
* Only load necessary data.
SF #1210126: instead of parsing the entire JPEG/TIFF image, we
should load data as necessary. This will save memory with big
images.
* Interpret the MakerNotes.
The libexif project already has code for interpretating the
MakerNotes for a number of different camera models.
* Handle character encodings of the USER_COMMENT tag.
The first eight bytes store the character encoding, but PEL ignores
them for now. Using the Multibyte String PHP extension we should
be able to convert the data.
* Deal with characters outside Latin-1 in PelEntryWindowsString.
This needs testing from people running Windows XP set to a locale
different from Latin-1.
PEL Version 2.0
---------------
* Restructure information about tags.
Currently information about the tags are stored in several places
around the code, making updates difficult. All information about a
tag should be stored at one place, maybe by having a class per tag
(how well does PHP handle 142 small classes?).
The information in question is:
- hex code,
- title,
- name,
- description
- format,
- components,
- valid IFD types,
- how to load data,
- how to display (the getText() method)
This will most likely break API compatability and is delayed for
PEL 2.