Browse Source

Added old KDE3 version of libkipi

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/libraries/libkipi@1076200 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
v3.5.13-sru
tpearson 13 years ago
commit
82f79e1df0
  1. 6
      AUTHORS
  2. 481
      COPYING
  3. 1480
      ChangeLog
  4. 183
      INSTALL
  5. 7
      Mainpage.dox
  6. 7
      Makefile.am
  7. 6
      Makefile.am.in
  8. 14
      Makefile.cvs
  9. 26
      NEWS
  10. 86
      PACKAGING
  11. 1
      README
  12. 2
      RELEASE.rev
  13. 44
      TODO
  14. 12417
      acinclude.m4
  15. 12777
      aclocal.m4
  16. 243
      config.h.in
  17. 3
      configure.files
  18. 196
      configure.in
  19. 7
      configure.in.in
  20. 5
      doc/Makefile.am
  21. 18
      libkipi.lsm
  22. 16
      libkipi/Makefile.am
  23. 26
      libkipi/configure.in.in
  24. 11
      libkipi/libkipi.pc.in
  25. 1099
      libkipi/libkipi/Doxyfile
  26. 1086
      libkipi/libkipi/KDStream.cpp
  27. 375
      libkipi/libkipi/KDStream.h
  28. 138
      libkipi/libkipi/KDTools-License-US
  29. 93
      libkipi/libkipi/KDTools-License-non-US
  30. 349
      libkipi/libkipi/LICENSE.GPL
  31. 33
      libkipi/libkipi/Makefile.am
  32. BIN
      libkipi/libkipi/banner_left.png
  33. 224
      libkipi/libkipi/batchprogressdialog.cpp
  34. 80
      libkipi/libkipi/batchprogressdialog.h
  35. 96
      libkipi/libkipi/design
  36. BIN
      libkipi/libkipi/hi16-app-kipi.png
  37. BIN
      libkipi/libkipi/hi22-app-kipi.png
  38. BIN
      libkipi/libkipi/hi32-app-kipi.png
  39. BIN
      libkipi/libkipi/hi48-app-kipi.png
  40. 262
      libkipi/libkipi/imagecollection.cpp
  41. 76
      libkipi/libkipi/imagecollection.h
  42. 348
      libkipi/libkipi/imagecollectionselector.cpp
  43. 81
      libkipi/libkipi/imagecollectionselector.h
  44. 116
      libkipi/libkipi/imagecollectionshared.cpp
  45. 68
      libkipi/libkipi/imagecollectionshared.h
  46. 327
      libkipi/libkipi/imagedialog.cpp
  47. 83
      libkipi/libkipi/imagedialog.h
  48. 169
      libkipi/libkipi/imageinfo.cpp
  49. 82
      libkipi/libkipi/imageinfo.h
  50. 120
      libkipi/libkipi/imageinfoshared.cpp
  51. 91
      libkipi/libkipi/imageinfoshared.h
  52. 221
      libkipi/libkipi/interface.cpp
  53. 94
      libkipi/libkipi/interface.h
  54. BIN
      libkipi/libkipi/kipi-plugins_logo.png
  55. 67
      libkipi/libkipi/kipiplugin.desktop
  56. 37
      libkipi/libkipi/libkipi_export.h.in
  57. 100
      libkipi/libkipi/mainpage.cpp
  58. 91
      libkipi/libkipi/plugin.cpp
  59. 76
      libkipi/libkipi/plugin.h
  60. 388
      libkipi/libkipi/pluginloader.cpp
  61. 102
      libkipi/libkipi/pluginloader.h
  62. 209
      libkipi/libkipi/uploadwidget.cpp
  63. 75
      libkipi/libkipi/uploadwidget.h
  64. 31
      libkipi/libkipi/version.h
  65. 637
      libkipi/pics/kipi-icon.svg
  66. 269
      libkipi/pics/kipi-logo.svg
  67. 1
      po/Makefile.am
  68. 3
      po/ar/Makefile.am
  69. 125
      po/ar/libkipi.po
  70. 3
      po/br/Makefile.am
  71. 123
      po/br/libkipi.po
  72. 3
      po/ca/Makefile.am
  73. 124
      po/ca/libkipi.po
  74. 3
      po/cs/Makefile.am
  75. 133
      po/cs/libkipi.po
  76. 3
      po/cy/Makefile.am
  77. 121
      po/cy/libkipi.po
  78. 3
      po/da/Makefile.am
  79. 136
      po/da/libkipi.po
  80. 3
      po/de/Makefile.am
  81. 132
      po/de/libkipi.po
  82. 3
      po/el/Makefile.am
  83. 136
      po/el/libkipi.po
  84. 3
      po/en_GB/Makefile.am
  85. 133
      po/en_GB/libkipi.po
  86. 3
      po/es/Makefile.am
  87. 139
      po/es/libkipi.po
  88. 3
      po/et/Makefile.am
  89. 134
      po/et/libkipi.po
  90. 3
      po/fi/Makefile.am
  91. 128
      po/fi/libkipi.po
  92. 3
      po/fr/Makefile.am
  93. 136
      po/fr/libkipi.po
  94. 3
      po/ga/Makefile.am
  95. 124
      po/ga/libkipi.po
  96. 3
      po/gl/Makefile.am
  97. 134
      po/gl/libkipi.po
  98. 3
      po/is/Makefile.am
  99. 125
      po/is/libkipi.po
  100. 3
      po/it/Makefile.am
  101. 388
      po/it/libkipi.po
  102. 3
      po/ja/Makefile.am
  103. 124
      po/ja/libkipi.po
  104. 3
      po/lt/Makefile.am
  105. 176
      po/lt/libkipi.po
  106. 3
      po/mt/Makefile.am
  107. 140
      po/mt/libkipi.po
  108. 3
      po/nb/Makefile.am
  109. 136
      po/nb/libkipi.po
  110. 3
      po/nl/Makefile.am
  111. 138
      po/nl/libkipi.po
  112. 3
      po/pa/Makefile.am
  113. 136
      po/pa/libkipi.po
  114. 3
      po/pl/Makefile.am
  115. 136
      po/pl/libkipi.po
  116. 3
      po/pt/Makefile.am
  117. 381
      po/pt/libkipi.po
  118. 3
      po/pt_BR/Makefile.am
  119. 139
      po/pt_BR/libkipi.po
  120. 3
      po/ru/Makefile.am
  121. 131
      po/ru/libkipi.po
  122. 3
      po/rw/Makefile.am
  123. 163
      po/rw/libkipi.po
  124. 3
      po/sk/Makefile.am
  125. 126
      po/sk/libkipi.po
  126. 3
      po/sl/Makefile.am
  127. 135
      po/sl/libkipi.po
  128. 3
      po/sr/Makefile.am
  129. 136
      po/sr/libkipi.po
  130. 3
      po/sr@Latn/Makefile.am
  131. 136
      po/sr@Latn/libkipi.po
  132. 3
      po/ta/Makefile.am
  133. 130
      po/ta/libkipi.po
  134. 3
      po/tr/Makefile.am
  135. 134
      po/tr/libkipi.po
  136. 3
      po/uk/Makefile.am
  137. 130
      po/uk/libkipi.po
  138. 3
      po/zh_CN/Makefile.am
  139. 130
      po/zh_CN/libkipi.po
  140. 4
      subdirs

6
AUTHORS

@ -0,0 +1,6 @@
AUTHORS AND MAINTAINERS :
Renchi Raju <renchi.raju at kdemail.net>
Gilles Caulier <caulier dot gilles at free.fr>
Jesper K. Pedersen <blackie at kde.org>
Aurelien Gateau <aurelien dot gateau at free.fr>

481
COPYING

@ -0,0 +1,481 @@
GNU LIBRARY GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
51 Franklin Steet, Fifth Floor
Boston, MA 02110-1301, USA.
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is
numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it. You can use it for
your libraries, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.
Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library. If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software. To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs. This
license, the GNU Library General Public License, applies to certain
designated libraries. This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.
The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it. Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program. However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.
Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries. We
concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves. This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them. (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.) The hope is that this
will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, while the latter only
works together with the library.
Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License"). Each licensee is
addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
d) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Steet, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

1480
ChangeLog

File diff suppressed because it is too large Load Diff

183
INSTALL

@ -0,0 +1,183 @@
Requirements: libkexif v >= 0.1 kde >= 3.1.x
Basic Installation
==================
These are generic installation instructions.
The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation. It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions. Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').
If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release. If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.
The file `configure.in' is used to create `configure' by a program
called `autoconf'. You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.
The simplest way to compile this package is:
1. `cd' to the directory containing the package's source code and type
`./configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead to prevent `csh' from trying to execute
`configure' itself.
Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Optionally, type `make check' to run any self-tests that come with
the package.
4. Type `make install' to install the programs and any data files and
documentation.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean'. To also remove the
files that `configure' created (so you can compile the package for
a different kind of computer), type `make distclean'. There is
also a `make maintainer-clean' target, but that is intended mainly
for the package's developers. If you use it, you may have to get
all sorts of other programs in order to regenerate files that came
with the distribution.
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files. Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.

7
Mainpage.dox

@ -0,0 +1,7 @@
/** @mainpage KDE Extragear Libraries
*
* The extragear-libs module collects libraries that are shared by
* more than one extragear application, or which are useful in their
* own right.
*
*/

7
Makefile.am

@ -0,0 +1,7 @@
AUTOMAKE_OPTIONS = foreign 1.6.1
include admin/deps.am
include admin/Doxyfile.am
COMPILE_FIRST = libkexif libkipi
SUBDIRS=$(TOPSUBDIRS)

6
Makefile.am.in

@ -0,0 +1,6 @@
AUTOMAKE_OPTIONS = foreign 1.6.1
include admin/deps.am
include admin/Doxyfile.am
COMPILE_FIRST = libkexif libkipi

14
Makefile.cvs

@ -0,0 +1,14 @@
all:
@echo "This Makefile is only for the CVS repository"
@echo "This will be deleted before making the distribution"
@echo ""
@if test ! -d admin; then \
echo "Please recheckout this module!" ;\
echo "for cvs: use checkout once and after that update again" ;\
echo "for cvsup: checkout kde-common from cvsup and" ;\
echo " link kde-common/admin to ./admin" ;\
exit 1 ;\
fi
$(MAKE) -f admin/Makefile.common cvs
.SILENT:

26
NEWS

@ -0,0 +1,26 @@
-------------------------------------------------------------------------
0.1.4
Bugs fixed:
o fix FTBFS (fails to build from source) when libkipi is
build the first time on a system.
-------------------------------------------------------------------------
0.1.3
New features:
o Make loadPlugin() public, so that it's possible to load plugins
selectively, and raise version to 1.0.1, so that this API change
can be detected
Bugs fixed:
o various build fixes
o batchprogressdialog: Removed help button. It does not point to
any usefull documentation. BUG: 99418
-------------------------------------------------------------------------
For details and info about previous versions, see ChangeLog.

86
PACKAGING

@ -0,0 +1,86 @@
How to release kipi & co.
----------------------------------------
1. Release libkipi
2. Release kipi-plugins
1. Release libkipi
a) Update release info
libkipi/libkipi.lsm
libkipi/libkipi/version.h
libkipi/libkipi.pc.in
To do that you can use the "prepare_libkipi.rb" script, change the
release version ("version" and "version_n" fields) and run it.
Don't forget to commit your changes :)
b) Update Changelog
- to do that use the "release_kipi_changelog.sh" script
release_kipi_changelog.sh libkipi oldest-revision-or-date new-release-version
- edit Changelog and modify the wrong lines (if any)
- Commit your changes
c) Build the source tarball
- use the "release_libkipi.rb"
edit the script and change the "version" field
if you're releasing an svn snapshot set "usesvnver" to "yes"
run it and get libkipiXXX.tar.bz2
d) Uncompress and test the tarball
- check if all the files are right in
- check if the file RELEASE.rev is in and with the right revision number
- check if it builds correctly.
e) Upload tarball for testing
Before an official release upload the tarball for testing used sites are
digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends
on who is releasing :)
Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a
feedback from pakagers before posting an offical release annoucement.
f) Upload tarbal on SF and update kipi site
official site for uploading the release is http://sourceforge.net/projects/kipi
web page to be update is http://extragear.kde.org/apps/kipi/
to update this last you have to get, change and commit it from
XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
Send a mail to announce the official release.
2. Release kipi-plugins
a) Update release info
kipi-plugins/kipi-plugins.lsm
kipi-plugins/common/include/pluginsversion.h
To do that you can use the "prepare_kipiplugins.rb" script, change the
release version ("version" field) and run it.
Don't forget to commit your changes.
b) Update Changelog
- to do that use the "release_kipi_changelog.sh" script
release_kipi_changelog.sh kipi-plugins oldest-revision-or-date new-release-version
- edit Changelog and modify the wrong lines (if any)
- Commit your changes
c) Build the source tarball
- use the "release_kipi-plugins.rb"
edit the script and change the "version" field and check the "addPo" one for po files
if you're releasing an svn snapshot set "usesvnver" to "yes"
run it and get kipi-pluginsXXX.tar.bz2
d) Uncompress and test the tarball
- check if all the files are right in
- check if the file RELEASE.rev is in and with the right revision number
- check if it builds correctly.
e) Upload tarball for testing
Before an official release upload the tarball for testing used sites are
digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends
on who is releasing :)
Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a
feedback from pakagers before posting an offical release annoucement.
f) Upload tarbal on SF and update kipi site
official site for uploading the release is http://sourceforge.net/projects/kipi
web page to be update is http://extragear.kde.org/apps/kipi/
to update this last you have to get, change and commit it from
XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
Send a mail to announce the official release.

1
README

@ -0,0 +1 @@
See the README file on kipi-plugins

2
RELEASE.rev

@ -0,0 +1,2 @@
Last Changed Rev: 609235
Last Changed Date: 2006-11-29 22:07:56 +0100 (Wed, 29 Nov 2006)

44
TODO

@ -0,0 +1,44 @@
To be discussed:
#1. Define the way plugins should access host app images. Current choices are:
#- Use ImageCollections
#- Use Interface::Browser class suggested by Jesper in the
# "libkipi/libkipi/design" document.
Done
2. In the same way, define how plugins should give images to the host app.
Current choices are:
- Interface::addImage
- Define a class similar to Interface::Browser, which we could call
Interface::Importer
3. Make a decision on some terms: should we use "album" or "image collection"
or both (if so, explain the difference in a README file)
4. Agree on the category list.
5. Define KIPI and plugin versioning so that we don't get mixed version bugs
(Aurélien: I think this could be done by correctly defining lib version
numbers, but I might be missing something here).
6. Define what helper widgets/dialog we should provide to plugins. Right now
we have:
- ImageCollectionDialog (Poor name, should be ImageSelectDialog)
- UploadWidget
To be done:
- Implement a widget to let the user select ImageCollections. The minimal
interface should be:
class ImageCollectionSelector : public QWidget {
QValueList<ImageCollection> imageCollections;
}
- Review all classes to polish the API before freezing it.
- Improve BC strength with d pointers.
- Add functions for copying/moving/renaming files, or do we all agree that the
ImageInfo::cloneData() method is enough?
- Write some documentation. I'm thinking about Doxygen class documentation
plus a skeleton app and a skeleton plugin to serve as examples.

12417
acinclude.m4

File diff suppressed because it is too large Load Diff

12777
aclocal.m4 vendored

File diff suppressed because it is too large Load Diff

243
config.h.in

@ -0,0 +1,243 @@
/* config.h.in. Generated from configure.in by autoheader. */
/* Define to 1 if you have the <Carbon/Carbon.h> header file. */
#undef HAVE_CARBON_CARBON_H
/* Define if you have the CoreAudio API */
#undef HAVE_COREAUDIO
/* Define to 1 if you have the <crt_externs.h> header file. */
#undef HAVE_CRT_EXTERNS_H
/* Defines if your system has the crypt function */
#undef HAVE_CRYPT
/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H
/* Define to 1 if you have the <inttypes.h> header file. */
#undef HAVE_INTTYPES_H
/* Define if you have libjpeg */
#undef HAVE_LIBJPEG
/* Define if you have libpng */
#undef HAVE_LIBPNG
/* Define if you have a working libpthread (will enable threaded code) */
#undef HAVE_LIBPTHREAD
/* Define if you have libz */
#undef HAVE_LIBZ
/* Define to 1 if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H
/* Define if your system needs _NSGetEnviron to set up the environment */
#undef HAVE_NSGETENVIRON
/* Define if you have res_init */
#undef HAVE_RES_INIT
/* Define if you have the res_init prototype */
#undef HAVE_RES_INIT_PROTO
/* Define if you have a STL implementation by SGI */
#undef HAVE_SGI_STL
/* Define to 1 if you have the `snprintf' function. */
#undef HAVE_SNPRINTF
/* Define to 1 if you have the <stdint.h> header file. */
#undef HAVE_STDINT_H
/* Define to 1 if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H
/* Define to 1 if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
/* Define if you have strlcat */
#undef HAVE_STRLCAT
/* Define if you have the strlcat prototype */
#undef HAVE_STRLCAT_PROTO
/* Define if you have strlcpy */
#undef HAVE_STRLCPY
/* Define if you have the strlcpy prototype */
#undef HAVE_STRLCPY_PROTO
/* Define to 1 if you have the <sys/bitypes.h> header file. */
#undef HAVE_SYS_BITYPES_H
/* Define to 1 if you have the <sys/stat.h> header file. */
#undef HAVE_SYS_STAT_H
/* Define to 1 if you have the <sys/types.h> header file. */
#undef HAVE_SYS_TYPES_H
/* Define to 1 if you have the <unistd.h> header file. */
#undef HAVE_UNISTD_H
/* Define to 1 if you have the `vsnprintf' function. */
#undef HAVE_VSNPRINTF
/* Suffix for lib directories */
#undef KDELIBSUFF
/* kdemacros.h usable */
#undef KDEMACROS_USABLE
/* Name of package */
#undef PACKAGE
/* Define to the address where bug reports for this package should be sent. */
#undef PACKAGE_BUGREPORT
/* Define to the full name of this package. */
#undef PACKAGE_NAME
/* Define to the full name and version of this package. */
#undef PACKAGE_STRING
/* Define to the one symbol short name of this package. */
#undef PACKAGE_TARNAME
/* Define to the version of this package. */
#undef PACKAGE_VERSION
/* The size of `char *', as computed by sizeof. */
#undef SIZEOF_CHAR_P
/* The size of `int', as computed by sizeof. */
#undef SIZEOF_INT
/* The size of `long', as computed by sizeof. */
#undef SIZEOF_LONG
/* The size of `short', as computed by sizeof. */
#undef SIZEOF_SHORT
/* The size of `size_t', as computed by sizeof. */
#undef SIZEOF_SIZE_T
/* The size of `unsigned long', as computed by sizeof. */
#undef SIZEOF_UNSIGNED_LONG
/* Define to 1 if you have the ANSI C header files. */
#undef STDC_HEADERS
/* Version number of package */
#undef VERSION
/* Defined if compiling without arts */
#undef WITHOUT_ARTS
/*
* jpeg.h needs HAVE_BOOLEAN, when the system uses boolean in system
* headers and I'm too lazy to write a configure test as long as only
* unixware is related
*/
#ifdef _UNIXWARE
#define HAVE_BOOLEAN
#endif
/*
* AIX defines FD_SET in terms of bzero, but fails to include <strings.h>
* that defines bzero.
*/
#if defined(_AIX)
#include <strings.h>
#endif
#if defined(HAVE_NSGETENVIRON) && defined(HAVE_CRT_EXTERNS_H)
# include <sys/time.h>
# include <crt_externs.h>
# define environ (*_NSGetEnviron())
#endif
#if !defined(HAVE_RES_INIT_PROTO)
#ifdef __cplusplus
extern "C" {
#endif
int res_init(void);
#ifdef __cplusplus
}
#endif
#endif
#if !defined(HAVE_STRLCAT_PROTO)
#ifdef __cplusplus
extern "C" {
#endif
unsigned long strlcat(char*, const char*, unsigned long);
#ifdef __cplusplus
}
#endif
#endif
#if !defined(HAVE_STRLCPY_PROTO)
#ifdef __cplusplus
extern "C" {
#endif
unsigned long strlcpy(char*, const char*, unsigned long);
#ifdef __cplusplus
}
#endif
#endif
/*
* On HP-UX, the declaration of vsnprintf() is needed every time !
*/
#if !defined(HAVE_VSNPRINTF) || defined(hpux)
#if __STDC__
#include <stdarg.h>
#include <stdlib.h>
#else
#include <varargs.h>
#endif
#ifdef __cplusplus
extern "C"
#endif
int vsnprintf(char *str, size_t n, char const *fmt, va_list ap);
#ifdef __cplusplus
extern "C"
#endif
int snprintf(char *str, size_t n, char const *fmt, ...);
#endif
/* define to 1 if -fvisibility is supported */
#undef __KDE_HAVE_GCC_VISIBILITY
#if defined(__SVR4) && !defined(__svr4__)
#define __svr4__ 1
#endif
/* type to use in place of socklen_t if not defined */
#undef kde_socklen_t
/* type to use in place of socklen_t if not defined (deprecated, use
kde_socklen_t) */
#undef ksize_t

3
configure.files

@ -0,0 +1,3 @@
./admin/configure.in.min
configure.in.in
./libkipi/configure.in.in

196
configure.in

@ -0,0 +1,196 @@
dnl =======================================================
dnl FILE: ./admin/configure.in.min
dnl =======================================================
dnl This file is part of the KDE libraries/packages
dnl Copyright (C) 2001 Stephan Kulow (coolo@kde.org)
dnl This file is free software; you can redistribute it and/or
dnl modify it under the terms of the GNU Library General Public
dnl License as published by the Free Software Foundation; either
dnl version 2 of the License, or (at your option) any later version.
dnl This library is distributed in the hope that it will be useful,
dnl but WITHOUT ANY WARRANTY; without even the implied warranty of
dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
dnl Library General Public License for more details.
dnl You should have received a copy of the GNU Library General Public License
dnl along with this library; see the file COPYING.LIB. If not, write to
dnl the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
dnl Boston, MA 02110-1301, USA.
# Original Author was Kalle@kde.org
# I lifted it in some mater. (Stephan Kulow)
# I used much code from Janos Farkas
dnl Process this file with autoconf to produce a configure script.
AC_INIT(acinclude.m4) dnl a source file from your sub dir
dnl This is so we can use kde-common
AC_CONFIG_AUX_DIR(admin)
dnl This ksh/zsh feature conflicts with `cd blah ; pwd`
unset CDPATH
dnl Checking host/target/build systems, for make, install etc.
AC_CANONICAL_SYSTEM
dnl Perform program name transformation
AC_ARG_PROGRAM
dnl Automake doc recommends to do this only here. (Janos)
AM_INIT_AUTOMAKE(libkipi-0.1.5, "3.5.5") dnl searches for some needed programs
AM_MAINTAINER_MODE
KDE_SET_PREFIX
dnl generate the config header
AM_CONFIG_HEADER(config.h) dnl at the distribution this done
dnl Checks for programs.
AC_CHECK_COMPILERS
AC_ENABLE_SHARED(yes)
AC_ENABLE_STATIC(no)
KDE_PROG_LIBTOOL
dnl for NLS support. Call them in this order!
dnl WITH_NLS is for the po files
AM_KDE_WITH_NLS
KDE_USE_QT(3.2)
AC_PATH_KDE
dnl =======================================================
dnl FILE: configure.in.in
dnl =======================================================
#MIN_CONFIG(3.2)
CXXFLAGS="$CXXFLAGS $KDE_DEFAULT_CXXFLAGS"
KDE_ENABLE_HIDDEN_VISIBILITY
KDE_INIT_DOXYGEN([KEG Libraries API Reference], [Version $VERSION])
dnl =======================================================
dnl FILE: ./libkipi/configure.in.in
dnl =======================================================
AC_OUTPUT([ libkipi/libkipi.pc ])
KDE_ENABLE_HIDDEN_VISIBILITY
AC_LANG_PUSH(C++)
libkipi_kdemacros_cppflags=$CPPFLAGS
CPPFLAGS="$CPPFLAGS $all_includes"
AC_MSG_CHECKING([if kdemacros.h is usable])
AC_COMPILE_IFELSE(
[
#include <kdemacros.h>
#include <string>
int other_func( void ) KDE_EXPORT;
int other_func( void )
{
std::string s("KDE_EXPORT");
return 0;
}
],
[ AC_MSG_RESULT([yes])
AC_DEFINE(KDEMACROS_USABLE, 1, [kdemacros.h usable]) ],
[ AC_MSG_RESULT([no]) ]
)
CPPFLAGS=$libkipi_kdemacros_cppflags
AC_LANG_POP(C++)
AM_CONFIG_HEADER([ libkipi/libkipi/libkipi_export.h ])
KDE_CREATE_SUBDIRSLIST
AM_CONDITIONAL(libkexif_SUBDIR_included, test "x$libkexif_SUBDIR_included" = xyes)
AM_CONDITIONAL(libkipi_SUBDIR_included, test "x$libkipi_SUBDIR_included" = xyes)
AM_CONDITIONAL(doc_SUBDIR_included, test "x$doc_SUBDIR_included" = xyes)
AM_CONDITIONAL(po_SUBDIR_included, test "x$po_SUBDIR_included" = xyes)
AC_CONFIG_FILES([ Makefile ])
AC_CONFIG_FILES([ doc/Makefile ])
AC_CONFIG_FILES([ libkipi/Makefile ])
AC_CONFIG_FILES([ libkipi/libkipi/Makefile ])
AC_CONFIG_FILES([ po/Makefile ])
AC_CONFIG_FILES([ po/ar/Makefile ])
AC_CONFIG_FILES([ po/br/Makefile ])
AC_CONFIG_FILES([ po/ca/Makefile ])
AC_CONFIG_FILES([ po/cs/Makefile ])
AC_CONFIG_FILES([ po/cy/Makefile ])
AC_CONFIG_FILES([ po/da/Makefile ])
AC_CONFIG_FILES([ po/de/Makefile ])
AC_CONFIG_FILES([ po/el/Makefile ])
AC_CONFIG_FILES([ po/en_GB/Makefile ])
AC_CONFIG_FILES([ po/es/Makefile ])
AC_CONFIG_FILES([ po/et/Makefile ])
AC_CONFIG_FILES([ po/fi/Makefile ])
AC_CONFIG_FILES([ po/fr/Makefile ])
AC_CONFIG_FILES([ po/ga/Makefile ])
AC_CONFIG_FILES([ po/gl/Makefile ])
AC_CONFIG_FILES([ po/is/Makefile ])
AC_CONFIG_FILES([ po/it/Makefile ])
AC_CONFIG_FILES([ po/ja/Makefile ])
AC_CONFIG_FILES([ po/lt/Makefile ])
AC_CONFIG_FILES([ po/mt/Makefile ])
AC_CONFIG_FILES([ po/nb/Makefile ])
AC_CONFIG_FILES([ po/nl/Makefile ])
AC_CONFIG_FILES([ po/pa/Makefile ])
AC_CONFIG_FILES([ po/pl/Makefile ])
AC_CONFIG_FILES([ po/pt/Makefile ])
AC_CONFIG_FILES([ po/pt_BR/Makefile ])
AC_CONFIG_FILES([ po/ru/Makefile ])
AC_CONFIG_FILES([ po/rw/Makefile ])
AC_CONFIG_FILES([ po/sk/Makefile ])
AC_CONFIG_FILES([ po/sl/Makefile ])
AC_CONFIG_FILES([ po/sr/Makefile ])
AC_CONFIG_FILES([ po/sr@Latn/Makefile ])
AC_CONFIG_FILES([ po/ta/Makefile ])
AC_CONFIG_FILES([ po/tr/Makefile ])
AC_CONFIG_FILES([ po/uk/Makefile ])
AC_CONFIG_FILES([ po/zh_CN/Makefile ])
AC_OUTPUT
# Check if KDE_SET_PREFIX was called, and --prefix was passed to configure
if test -n "$kde_libs_prefix" -a -n "$given_prefix"; then
# And if so, warn when they don't match
if test "$kde_libs_prefix" != "$given_prefix"; then
# And if kde doesn't know about the prefix yet
echo ":"`kde-config --path exe`":" | grep ":$given_prefix/bin/:" 2>&1 >/dev/null
if test $? -ne 0; then
echo ""
echo "Warning: you chose to install this package in $given_prefix,"
echo "but KDE was found in $kde_libs_prefix."
echo "For this to work, you will need to tell KDE about the new prefix, by ensuring"
echo "that KDEDIRS contains it, e.g. export KDEDIRS=$given_prefix:$kde_libs_prefix"
echo "Then restart KDE."
echo ""
fi
fi
fi
if test x$GXX = "xyes" -a x$kde_have_gcc_visibility = "xyes" -a x$kde_cv_val_qt_gcc_visibility_patched = "xno"; then
echo ""
echo "Your GCC supports symbol visibility, but the patch for Qt supporting visibility"
echo "was not included. Therefore, GCC symbol visibility support remains disabled."
echo ""
echo "For better performance, consider including the Qt visibility supporting patch"
echo "located at:"
echo ""
echo "http://bugs.kde.org/show_bug.cgi?id=109386"
echo ""
echo "and recompile all of Qt and KDE. Note, this is entirely optional and"
echo "everything will continue to work just fine without it."
echo ""
fi
if test "$all_tests" = "bad"; then
if test ! "$cache_file" = "/dev/null"; then
echo ""
echo "Please remove the file $cache_file after changing your setup"
echo "so that configure will find the changes next time."
echo ""
fi
else
echo ""
echo "Good - your configure finished. Start make now"
echo ""
fi

7
configure.in.in

@ -0,0 +1,7 @@
#MIN_CONFIG(3.2)
CXXFLAGS="$CXXFLAGS $KDE_DEFAULT_CXXFLAGS"
KDE_ENABLE_HIDDEN_VISIBILITY
KDE_INIT_DOXYGEN([KEG Libraries API Reference], [Version $VERSION])

5
doc/Makefile.am

@ -0,0 +1,5 @@
KDE_LANG = en
KDE_DOCS = AUTO
SUBDIRS = $(AUTODIRS)

18
libkipi.lsm

@ -0,0 +1,18 @@
Begin4
Title: libkipi
Version: 0.1.5
Entered-date: 2006-11-29
Description: KDE Image Plugin Interface, a library to share plugins among
graphic applications
Keywords: kde image plugins
Author: renchi at pooh.tam.uiuc.edu (Renchi Raju)
caulier dot gilles at free.fr (Gilles Caulier)
blackie at kde.org (Jesper K. Pedersen)
aurelien dot gateau at free.fr (Aurelien Gateau)
Maintained-by:
Primary-site: http://extragear.kde.org/apps/kipi
Alternate-site:
Original-site:
Platforms:
Copying-policy: LGPL
End

16
libkipi/Makefile.am

@ -0,0 +1,16 @@
SUBDIRS = libkipi
pkgconfigdir = $(libdir)/pkgconfig
pkgconfig_DATA = libkipi.pc
EXTRA_DIST = libkipi.pc.in
# i18n translation messages
messages:
LIST=`find . -name \*.h -o -name \*.hh -o -name \*.H -o -name \*.hxx -o -name \*.hpp -o -name \*.cpp -o -name \*.cc -o -name \*.cxx -o -name \*.ecpp -o -name \*.C`; \
if test -n "$$LIST"; then \
$(XGETTEXT) $$LIST -o $(podir)/libkipi.pot; \
fi
include $(top_srcdir)/admin/Doxyfile.am

26
libkipi/configure.in.in

@ -0,0 +1,26 @@
AC_OUTPUT([ libkipi/libkipi.pc ])
KDE_ENABLE_HIDDEN_VISIBILITY
AC_LANG_PUSH(C++)
libkipi_kdemacros_cppflags=$CPPFLAGS
CPPFLAGS="$CPPFLAGS $all_includes"
AC_MSG_CHECKING([if kdemacros.h is usable])
AC_COMPILE_IFELSE(
[
#include <kdemacros.h>
#include <string>
int other_func( void ) KDE_EXPORT;
int other_func( void )
{
std::string s("KDE_EXPORT");
return 0;
}
],
[ AC_MSG_RESULT([yes])
AC_DEFINE(KDEMACROS_USABLE, 1, [kdemacros.h usable]) ],
[ AC_MSG_RESULT([no]) ]
)
CPPFLAGS=$libkipi_kdemacros_cppflags
AC_LANG_POP(C++)
AM_CONFIG_HEADER([ libkipi/libkipi/libkipi_export.h ])

11
libkipi/libkipi.pc.in

@ -0,0 +1,11 @@
prefix=@prefix@
exec_prefix=@exec_prefix@
libdir=@libdir@
includedir=@includedir@
Name: libkipi
Description: KDE library for shared plugins between graphical applications
Requires:
Version: 0.1.5
Libs: -L${libdir} -lkipi
Cflags: -I${includedir}

1099
libkipi/libkipi/Doxyfile

File diff suppressed because it is too large Load Diff

1086
libkipi/libkipi/KDStream.cpp

File diff suppressed because it is too large Load Diff

375
libkipi/libkipi/KDStream.h

@ -0,0 +1,375 @@
/* -*- Mode: C++ -*-
KD Tools - a set of useful widgets for Qt
$Id: KDStream.h 387954 2005-02-10 07:49:40Z blackie $
*/
/****************************************************************************
** Copyright (C) 2001-2005 Klarälvdalens Datakonsult AB. All rights reserved.
**
** This file is part of the KD Tools library.
**
** This file may be distributed and/or modified under the terms of the
** GNU General Public License version 2 as published by the Free Software
** Foundation and appearing in the file LICENSE.GPL included in the
** packaging of this file.
**
** Licensees holding valid commercial KD Tools licenses may use this file in
** accordance with the KD Tools Commercial License Agreement provided with
** the Software.
**
** This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
** WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
**
** Contact info@klaralvdalens-datakonsult.se if any conditions of this
** licensing are not clear to you.
**
**********************************************************************/
#ifndef KIPI_KDSTREAM
#define KIPI_KDSTREAM
// Forward declarations.
class QImage;
class QPixmap;
class QColor;
class QColorGroup;
class QPalette;
class QCursor;
class QDate;
class QDateTime;
class QTime;
class QFont;
class QPen;
class QPoint;
class QSize;
class QRect;
class QObject;
class QVariant;
class QBrush;
class QSizePolicy;
class QKeySequence;
#include <qstring.h>
#include <qvaluelist.h>
#include <qstrlist.h>
#include <qasciidict.h>
#include <qintdict.h>
#include <qptrdict.h>
#include <qdict.h>
#include <qvaluestack.h>
#include <qasciicache.h>
#include <qintcache.h>
#include <qcache.h>
#if ( QT_VERSION < 300 )
#include <qlist.h>
#include <qstack.h>
#include <qqueue.h>
#include <qvector.h>
#endif
#if ( QT_VERSION >= 300 )
#include <qptrlist.h>
#include <qptrstack.h>
#include <qptrqueue.h>
#include <qpair.h>
#include <qptrvector.h>
#include <qvaluevector.h>
#endif
// utility functions.
class KDStream;
typedef KDStream & (*KDSTREAMFUNC)(KDStream &);
KDStream& endl( KDStream& stream);