- the XS code for i_tt_glyph_name() used unsigned char to store a
[imager.git] / TODO
CommitLineData
b921d414 1 *** TODO ***
b921d414 2
b921d414
AMH
3Iolayer:
4- Add scalar/mmap to iolayer
a106216b 5- Add close() code to iolayer for fakeseek sources.
b921d414 6- Merge callback interface into iolayer
a106216b
AMH
7- and raw
8- Implment the maxread threshold (Indicates how much can
9 be read from a source before it stops reading from its
10 underlying source. For making sure only the relevant
11 data is read from a socket for example.
12
b921d414 13
b921d414
AMH
14Enhanched internal structure:
15
16MultiImage & metadata support:
17- Figure what interface should be between C and perl?
18- How to store data in the C interface for tags/metadata?
19 Support tiff's madness, i.e. tags and options.
20- Error handling, make a general i_errstr object and arrange
21 such that each image has an i_errstr object to hold its
22 local errors?
23- SEE design/represent.txt for proposed new structure and
24 interface design that takes these factors into account.
faa9b3e7
TC
25- define common i_* tags for specifying attribute common among images
26 like spatial resolution (implement for other image types, especially
10461f9a
TC
27 TIFF) (Spatial resolution is supported for all types that support
28 it - are there any other common properties we can add?)
faa6fa9b 29- implement the i_incomplete tag for other formats
b921d414
AMH
30
31New Features:
a106216b 32- Add mng support, pcx and aalib support.
13db6021
TC
33 - Windows icon files (.ico)
34 - ILBM (Amiga) images
35 - photoshop files (I think I've seen docs)
36 - XBM
37 - FITS
38 - WMF (extract bitmap data on read)
39 - gzip or bzip2 compressed raw
10461f9a 40 - postscript for output
ee6f9750 41 - PAM file support (man pam in recent PNM tools)
5f5fe73e 42
b921d414
AMH
43- Transforms, interpolated multidimensional lookup tables.
44 Usefull for CMYK <-> RGB table lookup.
45
a106216b 46- advanced font layout (spacing, kerning, alignment) (Artur?)
faa9b3e7 47
bf9dd17c 48- ways to check if characters are present in a font, eg. checking if
9c5ed9a7 49 ligatures are present (done for FreeType2)
bf9dd17c 50
faa9b3e7
TC
51- font synthesis - synthesize a bold or slanted font from a normal font
52 (or even from an existing bold or slanted font)
bf9dd17c 53
faa9b3e7 54- utf8 support for text output
9a71bc09 55 (available for FT1, freetype2, should be easy for Win32)
c855ad0e
TC
56
57- easy interfaces for text output:
58 - align text around point, including:
59 - left, center, right horizontal alignment
60 - top, center, baseline, bottom alignment
61 - choose whether to base alignment upon character cells or font
62 metrics to avoid spacing problems between lines
63 - fill a box from text, with newline handling
64 - an option to just return the information that would be used to
65 output the text, so it can be used for sizing calculations
66 - how much text fit in the box/how much space is left in the box
67 - fill a box with rich text (size and font changes)
68 - as above
69 - wrapping around boxes/images
70 - pod2Imager :)
71
72- tools to get more information about fonts/characters:
73 - name of font "Arial Bold Italic" vs "arialbi.ttf"
74 - ABC widths for characters (currently the only way to get the C width
75 for a character is to get the width with a following space and without
76 and then compare)
77 - character names
78
79- encodings for text output (maybe using the Encode module to work
80 between encodings)
faa9b3e7
TC
81
82- image rotation, 3 ways of doing rotation:
faa9b3e7
TC
83 - rotation by shearing, which produces makes lengths in the image larger,
84 but could be useful
a010a7d3 85 (2 of the 3 have been done)
faa9b3e7 86
9c5ed9a7
TC
87- read_multi() needs to handle other multi-image types,
88 (handles TIFF and GIF)
b921d414 89
9c5ed9a7 90- write_multi() to save other multi-image types, (handles TIFF and GIF)
8b695554 91 - pnm binary formats support multiple images per file
f62b2d84 92
362e7486
TC
93- compose channels - build a new image based on channels from several
94 images
95
da77e827
TC
96- arc outlines
97
9a71bc09
TC
98- complex lines/curves:
99 - thick lines:
100 - dotted/dashed lines
101 - doubled lines?
102 - end-point controls (butt-end, square-end, round-end, pointy, arrows)
103 - brush-lines (as with the Gimp, or Photoshop)
104 - more complex with multiple strokes and various randomness as with
105 Fractal Design Painter (or later versions of Corel Photo Paint)
106 - complex line shapes:
107 - lines
108 - general curves (cubic or bezier, whichever is more general)
109 - easy access to general curves:
110 - points to make a nice curve from
111 - various circular curves (centre, radii, start/end angles,
112 direction)
113 - Complex thick lines are probably more useful than brush-lines for
114 the things I expect Imager to be used for.
115 - http://www.develop-help.com/imager/strokes.png (.jpg for smaller version)
116
ea9e6c3f
TC
117- have Imager::Color{::Float}? use Graphics::ColorNames if present.
118
b921d414
AMH
119Clean up:
120- Make sure everything is doable with the OO interface
5f5fe73e 121 i_flood_fill() for example.
45a1d9d2 122 - include low-level functions like gsamp() and so on
f1ac5027 123
b921d414
AMH
124- Compile with memory debugging enabled and fix all leaks
125
a106216b 126- Add mycalloc() memory allocation wrappers.
b921d414
AMH
127
128- should we overload <=> or cmp for Imager::Color objects?
129 too many worms, leave it out
130
131- should the interlace option for reading raw images have
132 symbolic names in the OO interface?
133
f2bc9b80
TC
134- improve consistency in the interfaces, both in trying to use named
135 parameters where possible but also in using consistent names, eg.
136 (tx, ty) vs (left, top) in rubthrough() vs paste(). Do we want a (simple)
137 standard for this (suggested names)? Remember to preserve the old
138 interface where possible.
b921d414 139
c855ad0e
TC
140- try to clean up the inconsistencies between font types:
141 - utf8 (even if we just treat characters over 0xFF as missing for T1)
3799c4d1 142 (done for FT2, FT1, T1)
eeaa33fd 143 - transformations (done for FT2)
3799c4d1 144 - has_char() method (done for FT2, FT1, T1)
c855ad0e 145
b921d414 146Format specific issues:
b921d414
AMH
147- provide patches for libgif and libungif that fix their bugs
148 and give a useful extension interface. Probe for the
149 installation of the patches in Makefile.PL to let gif.c
150 know what features it can use.
151
a106216b 152- Add options for pnm writer to save in any of the p1..P6
b921d414
AMH
153 formats. Even if the input has 1 channel, write 3 and such
154 cases. Also allow ascii mode. Need to be able to write
155 pbm images which needs ties to the quantization code.
156
a106216b 157- save paletted images as paletted where that's supported. Done
f62b2d84 158 for gif/tga/bmp/tiff. Not done for png yet.
f873cb01 159
a106216b 160- read other format paletted images as paletted images. This has
f62b2d84
TC
161 been done for gif/tga/bmp/tiff formats but not for png.
162
163- read/write 16-bit/sample images as such for tiff
27d9683e 164
faa6fa9b
TC
165- read more metadata from images, esp tiff tags, EXIF format information
166 from TIFF and JPEG.
167
b921d414
AMH
168Documentation:
169- Add to the documentation
170- Write a tutorial?
faa9b3e7
TC
171- sample code and Imager/Samples.pod describing them
172- Imager/Cookbook.pod
b921d414
AMH
173- Write a guide to installing the helper libraries
174- Go through the entire project and add comments in pod
175 so doco.perl can be used to read them.
faa6fa9b 176- see the IRC log in design/doclayout.txt
6d0ed98a
TC
177- method index?
178- concept index?
ea9e6c3f
TC
179
180Build/configure:
181- use prompt() (from ExtUtils::MakeMaker) for questions in Makefile.PL
182- use the library's mechanism's to find the library if needed, for
183 example, freetype-config for FT2
184- the freetype2 library is built as "freetype.lib" on Win32 and needs
185 to be renamed to be found by the configuration process and included
186 with -lfreetype. Try to work around that.
187- freetype2 and freetype1 tend to be installed in /usr/include/freetype2
188 and /usr/include/freetype directories, or similarly named (somedir/freetype
189 for example), instead of putting these directly into the search path
190 search for the freetype{2}?/someheader and then add the subdirectory if
191 we find the file in that directory.