File: README

package info (click to toggle)
kdelibs 4%3A2.2.2-13.woody.14
  • links: PTS
  • area: main
  • in suites: woody
  • size: 36,832 kB
  • ctags: 40,077
  • sloc: cpp: 313,284; ansic: 20,558; xml: 11,448; sh: 11,318; makefile: 2,426; perl: 2,084; yacc: 1,663; java: 1,538; lex: 629; python: 300
file content (48 lines) | stat: -rw-r--r-- 1,382 bytes parent folder | download
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
KDE Image I/O library
---------------------
This library allows applications that use the Qt library to read and
write images in extra formats. Current formats include:

JPEG	<read>
XV	<read> <write>
EPS	<read> <write>
NETPBM	<incomplete>
PNG	<read> <write, only with newer libraries>
TIFF	<read>
KRL	<read>

To use these formats, you must 

1. link the application with the libkimgio library
2. Include the <kimageio.h> header
3. call KImageIO::registerFormats() once, somewhere in your code
   before you load an image.


Writing handlers
----------------
Please read the documentation for the QImageIO class in the Qt
documentation.

1. When writing handlers, there is a function naming convention;
suppose, for example, we were writing PNG read and write handlers,
we would name them

void kimgio_png_read ( QImageIO * );
void kimgio_png_write( QImageIO * );

ie

kimgio_<format>_<read/write>

This should reduce the chance of identifier clashes with other code.

2. If you only have either a reader or the writer for a particular
format, don't use NULL in QImageIO::defineIOHandler. Instead, write
a stub function for the unimplemented handler which displays a message
on standard output. This prevents kimgio-using programs dumping core
when attempting to call the unimplemented handler.

Yours in good faith and pedantry,

Sirtaj Singh Kang <taj@kde.org>, 23 September 1998.