4 - Add scalar/mmap to iolayer
5 - Add close() code to iolayer for fakeseek sources.
6 - Merge callback interface into iolayer
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.
14 Enhanched internal structure:
16 MultiImage & 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
23 - SEE design/represent.txt for proposed new structure and
24 interface design that takes these factors into account.
25 - define common i_* tags for specifying attribute common among images
26 like spatial resolution (implement for other image types, especially
27 TIFF) (Spatial resolution is supported for all types that support
28 it - are there any other common properties we can add?)
29 - implement the i_incomplete tag for other formats
32 - Add mng support, pcx and aalib support.
33 - Windows icon files (.ico)
35 - photoshop files (I think I've seen docs)
38 - WMF (extract bitmap data on read)
39 - gzip or bzip2 compressed raw
40 - postscript for output
42 - Transforms, interpolated multidimensional lookup tables.
43 Usefull for CMYK <-> RGB table lookup.
45 - advanced font layout (spacing, kerning, alignment) (Artur?)
47 - ways to check if characters are present in a font, eg. checking if
48 ligatures are present (done for FreeType2)
50 - font synthesis - synthesize a bold or slanted font from a normal font
51 (or even from an existing bold or slanted font)
53 - utf8 support for text output
54 (available for FT1, freetype2, should be easy for Win32)
56 - easy interfaces for text output:
57 - align text around point, including:
58 - left, center, right horizontal alignment
59 - top, center, baseline, bottom alignment
60 - choose whether to base alignment upon character cells or font
61 metrics to avoid spacing problems between lines
62 - fill a box from text, with newline handling
63 - an option to just return the information that would be used to
64 output the text, so it can be used for sizing calculations
65 - how much text fit in the box/how much space is left in the box
66 - fill a box with rich text (size and font changes)
68 - wrapping around boxes/images
71 - tools to get more information about fonts/characters:
72 - name of font "Arial Bold Italic" vs "arialbi.ttf"
73 - ABC widths for characters (currently the only way to get the C width
74 for a character is to get the width with a following space and without
78 - encodings for text output (maybe using the Encode module to work
81 - image rotation, 3 ways of doing rotation:
82 - rotation by shearing, which produces makes lengths in the image larger,
84 (2 of the 3 have been done)
86 - read_multi() needs to handle other multi-image types,
87 (handles TIFF and GIF)
89 - write_multi() to save other multi-image types, (handles TIFF and GIF)
90 - pnm binary formats support multiple images per file
92 - compose channels - build a new image based on channels from several
97 - complex lines/curves:
101 - end-point controls (butt-end, square-end, round-end, pointy, arrows)
102 - brush-lines (as with the Gimp, or Photoshop)
103 - more complex with multiple strokes and various randomness as with
104 Fractal Design Painter (or later versions of Corel Photo Paint)
105 - complex line shapes:
107 - general curves (cubic or bezier, whichever is more general)
108 - easy access to general curves:
109 - points to make a nice curve from
110 - various circular curves (centre, radii, start/end angles,
112 - Complex thick lines are probably more useful than brush-lines for
113 the things I expect Imager to be used for.
114 - http://www.develop-help.com/imager/strokes.png (.jpg for smaller version)
116 - have Imager::Color{::Float}? use Graphics::ColorNames if present.
119 - Make sure everything is doable with the OO interface
120 i_flood_fill() for example.
121 - include low-level functions like gsamp() and so on
123 - Compile with memory debugging enabled and fix all leaks
125 - Add mycalloc() memory allocation wrappers.
127 - should we overload <=> or cmp for Imager::Color objects?
128 too many worms, leave it out
130 - should the interlace option for reading raw images have
131 symbolic names in the OO interface?
133 - improve consistency in the interfaces, both in trying to use named
134 parameters where possible but also in using consistent names, eg.
135 (tx, ty) vs (left, top) in rubthrough() vs paste(). Do we want a (simple)
136 standard for this (suggested names)? Remember to preserve the old
137 interface where possible.
139 - try to clean up the inconsistencies between font types:
140 - utf8 (even if we just treat characters over 0xFF as missing for T1)
141 (done for FT2, FT1, T1)
142 - transformations (done for FT2)
143 - has_char() method (done for FT2, FT1, T1)
145 Format specific issues:
146 - provide patches for libgif and libungif that fix their bugs
147 and give a useful extension interface. Probe for the
148 installation of the patches in Makefile.PL to let gif.c
149 know what features it can use.
151 - Add options for pnm writer to save in any of the p1..P6
152 formats. Even if the input has 1 channel, write 3 and such
153 cases. Also allow ascii mode. Need to be able to write
154 pbm images which needs ties to the quantization code.
156 - save paletted images as paletted where that's supported. Done
157 for gif/tga/bmp/tiff. Not done for png yet.
159 - read other format paletted images as paletted images. This has
160 been done for gif/tga/bmp/tiff formats but not for png.
162 - read/write 16-bit/sample images as such for tiff
164 - read more metadata from images, esp tiff tags, EXIF format information
168 - Add to the documentation
170 - sample code and Imager/Samples.pod describing them
171 - Imager/Cookbook.pod
172 - Write a guide to installing the helper libraries
173 - Go through the entire project and add comments in pod
174 so doco.perl can be used to read them.
175 - see the IRC log in design/doclayout.txt
180 - use prompt() (from ExtUtils::MakeMaker) for questions in Makefile.PL
181 - use the library's mechanism's to find the library if needed, for
182 example, freetype-config for FT2
183 - the freetype2 library is built as "freetype.lib" on Win32 and needs
184 to be renamed to be found by the configuration process and included
185 with -lfreetype. Try to work around that.
186 - freetype2 and freetype1 tend to be installed in /usr/include/freetype2
187 and /usr/include/freetype directories, or similarly named (somedir/freetype
188 for example), instead of putting these directly into the search path
189 search for the freetype{2}?/someheader and then add the subdirectory if
190 we find the file in that directory.