Copy the KDE 3.5 branch to branches/trinity for new KDE 3.5 features.

BUG:215923


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdelibs@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19

AUTHORS

@@ -0,0 +1,7 @@
+Look in the appropriate subdirectories or files to get more information
+about the authors.
+
+The package is maintained by Kalle Dalheimer <kalle@kde.org>, however
+numerous people, too many to count, have contributed to kdelibs as a
+whole.  If you have a specific question, dig up the appropriate mailing
+list address, and ask away.

COMPILING

@@ -0,0 +1,137 @@
+THIS DOCUMENT DESCRIBES HOW YOU CAN COMPILE KDE WHEN USING SUBVERSION
+
+(If you use source tarballs, you can skip "make -f Makefile.cvs" and
+should use "make distclean" instead of "svn-clean")
+
+What you need
+=============
+
+Make sure you get the following stuff from the repository:
+
+qt-copy (This is qt-3.3.2)
+arts
+kdelibs
+kdebase (strongly recommended but not strictly necessary)
+<any other package you are interested in>
+
+It is important that you compile AND INSTALL the above packages in the 
+above order.
+
+Further you will need GNU make, autoconf 2.52, automake 1.5 and 
+a working C++ compiler (eg. gcc 2.95.2)
+
+Preparations
+============
+
+Before you start you must decide two things:
+
+1) Where do you want to have Qt installed? Qt is a bit lame in that it 
+basically installs itself in its own source-tree, but symlinks are your 
+friend. E.g you could link /usr/local/lib/qt3 to where you keep your Qt 
+source. Qt libs then end up in /usr/local/lib/qt3/lib.
+
+2) Where do you want to have KDE installed. A good candidate is /usr/local/kde
+
+Make sure you do (if using sh, ksh, or bash):
+export KDEDIR=/usr/local/kde
+
+With csh or tcsh the following is more appropriate:
+
+setenv KDEDIR /usr/local/kde
+
+Now you want to make sure that Qt and KDE libraries are picked up correctly.
+
+On systems that respond to environment variables something similar to the 
+following is appropriate:
+
+export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib
+
+On systems whose diety of choice is ldconfig, try:
+ldconfig -m $KDEDIR/lib
+ldconfig -m $QTDIR/lib
+
+You probably also want to add $KDEDIR/bin and $QTDIR/bin to your path.
+
+See http://www.kde.org/kde2-and-kde3.html for tips about setting up
+KDE 3.0 next to KDE 2.x.
+
+Compiling
+=========
+
+The magic sequence to compile & install a package is:
+gmake -f Makefile.cvs
+./configure --enable-debug
+gmake
+gmake install
+
+(On Linux, GNU make is the default make, and gmake in the above commands
+can be replaced with make).
+
+For Qt the magic sequence is:
+
+./configure -debug -shared -qt-gif -thread -sm -system-zlib -system-libpng -system-jpeg
+make
+
+Common problems
+===============
+
+Wrong Qt paths: 
+One of the biggest problems is picking up the correct version of Qt, 
+especially if your system has more version of Qt installed. Be aware 
+that information about library paths gets saved in the "config.cache" 
+file, "Makefile.in" as well as "Makefile" files. So it can be that after 
+some struggle to get QTDIR/KDEDIR setup correctly your setup is actually 
+correct, but old -incorrect- settings are still lying around.
+
+The best thing to do in such a case is to do a "svn-clean" (from kdesdk/scripts).
+This removes all files which aren't stored in the repository. You can then start all over 
+again with "makefile -f Makefile.cvs". Make sure you don't have any important 
+files lying around in your source tree any more, they will be deleted!
+
+New directories:
+When a new directory gets added to the repository it usually only contains a 
+Makefile.am but not a Makefile. If you try to compile such a directory
+you will get an error like:
+
+  Making all in management
+  make[3]: Entering directory /home/gregturp/KDE/kdelibs/kdeprint/management'
+  make[3]: *** No rule to make target all'.  Stop.
+  make[3]: Leaving directory /home/gregturp/KDE/kdelibs/kdeprint/management'
+  make[2]: *** [all-recursive] Error 1
+  make[2]: Leaving directory /home/gregturp/KDE/kdelibs/kdeprint'
+  make[1]: *** [all-recursive] Error 1
+  make[1]: Leaving directory /home/gregturp/KDE/kdelibs'
+  make: *** [all-recursive-am] Error 2
+
+The solution is to redo "make -f Makefile.cvs; ./configure". 
+
+You can create a single Makefile from a Makefile.am file with the
+kdesdk/scripts/create_makefile script. Make sure to run it from the toplevel
+directory. (E.g. /home/gregturp/KDE/kdelibs)
+
+Problems?
+=========
+
+See http://www.kde.org/compilationfaq.html for common build problems
+and their solution.
+
+If you encounter _LINK_ problems you are probably doing something wrong.
+Do a "svn-clean" and start from scratch, usually this solves the problem.
+
+If you encounter missing include files, especially if the files start with
+a 'q', you probably have not setup your QTDIR correct or have the wrong 
+version of Qt.
+
+If you encounter compile errors after updating from SVN, check whether you 
+need to update kdelibs as well. If the problems persists, wait a few hours,
+usually compile errors are fixed shortly after they have been introduced.
+
+If you still have problems read the kde-devel@kde.org mailinglist and/or
+post your problem there. You can subscribe by sending mail to
+kde-devel-request@kde.org with "subscribe" in the subject.
+
+Have fun!
+
+Cheers,
+Waldo Bastian
+bastian@kde.org

COMPILING.html

@@ -0,0 +1,130 @@
+<html>
+<!-- See also developer.kde.org/documentation/other/compiling.html -->
+<!-- and www/anoncvs.html -->
+<body bgcolor="#FFFFFF">
+<h1>THIS DOCUMENT DESCRIBES HOW YOU CAN COMPILE KDE WHEN USING CVS</h1>
+
+<p>(If you use source tarballs, you can skip "make -f Makefile.cvs" and
+should use "make distclean" instead of "make cvs-clean")
+
+<p><h3>What you need</h3>
+
+<p>Make sure you get the following stuff from CVS:
+
+<p><ul><li>qt-copy (This is qt-3.3.2)
+<li>arts
+<li>kdelibs
+<li>kdebase (strongly recommended but not strictly necessary)
+<li>any other package you are interested in
+</ul>
+
+<p>It is important that you compile AND INSTALL the above packages in the 
+above order.
+
+<p>Further you will need GNU make, autoconf 2.52, automake 1.5 and 
+a working C++ compiler (eg. gcc 2.95.2)
+
+<p><h3>Preparations</h3>
+
+<p>Before you start you must decide two things:
+
+<p>1) Where do you want to have Qt installed? Qt is a bit lame in that it 
+basically installs itself in its own source-tree, but symlinks are your 
+friend. E.g you could link /usr/local/lib/qt3 to where you keep your Qt 
+source. Qt libs then end up in /usr/local/lib/qt3/lib.
+
+<p>2) Where do you want to have KDE installed. A good candidate is /usr/local/kde
+
+<p>Make sure you do (if using sh, ksh, or bash):
+<pre>export KDEDIR=/usr/local/kde</pre>
+
+<p>With csh or tcsh the following is more appropriate:
+
+<pre>setenv KDEDIR /usr/local/kde</pre>
+
+<p>Now you want to make sure that Qt and KDE libraries are picked up correctly.
+
+<p>On systems that respond to environment variables something similar to the 
+following is appropriate:
+
+<p>export LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib
+
+<p>On systems whose diety of choice is ldconfig, try:
+<pre>ldconfig -m $KDEDIR/lib
+ldconfig -m $QTDIR/lib</pre>
+
+<p>You probably also want to add $KDEDIR/bin and $QTDIR/bin to your path.
+
+<p>See http://www.kde.org/kde2-and-kde3.html for tips about setting up
+KDE 3.0 next to KDE 2.x.
+
+<p><h3>Preparing CVS modules</h3>
+<p>
+All KDE modules require an "admin" sub-directory. You can create it by
+making a symbolic link from kde-common/admin, make sure to check out the
+kde-common module.
+<p>
+Example:<br>
+<pre>
+cd kdelibs
+ln -s ../kde-common/admin
+</pre>
+
+<p><h3>Compiling</h3>
+
+<p>The magic sequence to compile &amp; install a package is:
+<pre>gmake -f Makefile.cvs
+./configure --enable-debug
+gmake
+gmake install </pre>
+
+<p>(On Linux, GNU make is the default make, and gmake in the above commands
+can be replaced with make).
+
+<p>For Qt the magic sequence is:
+
+<pre>./configure -debug -shared -qt-gif -thread -sm -system-zlib -system-libpng -system-jpeg
+make</pre>
+
+<p><h3>Common problems</h3>
+
+<p>One of the biggest problems is picking up the correct version of Qt, 
+especially if your system has more version of Qt installed. Be aware 
+that information about library paths gets saved in the "config.cache" 
+file, "Makefile.in" as well as "Makefile" files. So it can be that after 
+some struggle to get QTDIR/KDEDIR setup correctly your setup is actually 
+correct, but old -incorrect- settings are still lying around.
+
+<p>The best thing to do in such a case is to do a "make cvs-clean". This 
+removes all files which aren't stored in CVS. You can then start all over 
+again with "makefile -f Makefile.cvs". Make sure you don't have any important 
+files lying around in your source tree any more, they will be deleted!
+
+
+<p><h3>Problems?</h3>
+
+<p>See <a href="http://www.kde.org/compilationfaq.html">http://www.kde.org/compilationfaq.html</a> for common build problems and their solution.
+
+<p>If you encounter _LINK_ problems you are probably doing something wrong.
+Do a "make cvs-clean" and start from scratch, usually this solves the problem.
+
+<p>If you encounter missing include files, especially if the files start with
+a 'q', you probably have not setup your QTDIR correct or have the wrong 
+version of Qt.
+
+<p>If you encounter compile errors after updating from CVS, check whether you 
+need to update kdelibs as well. If the problems persists, wait a few hours,
+usually compile errors are fixed shortly after they have been introduced.
+
+<p>If you still have problems read the kde-devel@kde.org mailinglist and/or
+post your problem there. You can subscribe by sending mail to
+kde-devel-request@kde.org with "subscribe" in the subject.
+
+<p>Have fun!
+
+<p>Cheers,<br>
+Waldo Bastian<br>
+bastian@kde.org<br>
+</body>
+</html>
+

COPYING

@@ -0,0 +1,346 @@
+NOTE! The GPL below is copyrighted by the Free Software Foundation, but
+the instance of code that it refers to (the kde programs) are copyrighted
+by the authors who actually wrote it.
+
+---------------------------------------------------------------------------
+			
+		    GNU GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+               51 Franklin Street, 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.
+
+			    Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.)  You can apply it to
+your programs, 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 software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, 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 redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+		    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+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 give any other recipients of the Program a copy of this License
+along with the Program.
+
+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 Program or any portion
+of it, thus forming a work based on the Program, 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) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+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 Program, 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 Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) 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; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, 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 executable.  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.
+
+If distribution of executable or 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 counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program 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.
+
+  5. 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 Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program 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.
+
+  7. 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 Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program 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 Program.
+
+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.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program 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.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the 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 Program
+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 Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, 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
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "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 PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. 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 PROGRAM 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 PROGRAM (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 PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), 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 Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  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 program's name and a brief idea of what it does.>
+    Copyright (C) 19yy  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program 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 General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program; if not, write to the Free Software
+    Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) 19yy name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Library General
+Public License instead of this License.

COPYING-DOCS

@@ -0,0 +1,397 @@
+		GNU Free Documentation License
+		  Version 1.2, November 2002
+
+
+ Copyright (C) 2000,2001,2002  Free Software Foundation, Inc.
+     51 Franklin St, 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.
+
+
+0. PREAMBLE
+
+The purpose of this License is to make a manual, textbook, or other
+functional and useful document "free" in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
+
+This License is a kind of "copyleft", which means that derivative
+works of the document must themselves be free in the same sense.  It
+complements the GNU General Public License, which is a copyleft
+license designed for free software.
+
+We have designed this License in order to use it for manuals for free
+software, because free software needs free documentation: a free
+program should come with manuals providing the same freedoms that the
+software does.  But this License is not limited to software manuals;
+it can be used for any textual work, regardless of subject matter or
+whether it is published as a printed book.  We recommend this License
+principally for works whose purpose is instruction or reference.
+
+
+1. APPLICABILITY AND DEFINITIONS
+
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License.  Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein.  The "Document", below,
+refers to any such manual or work.  Any member of the public is a
+licensee, and is addressed as "you".  You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
+
+A "Modified Version" of the Document means any work containing the
+Document or a portion of it, either copied verbatim, or with
+modifications and/or translated into another language.
+
+A "Secondary Section" is a named appendix or a front-matter section of
+the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall subject
+(or to related matters) and contains nothing that could fall directly
+within that overall subject.  (Thus, if the Document is in part a
+textbook of mathematics, a Secondary Section may not explain any
+mathematics.)  The relationship could be a matter of historical
+connection with the subject or with related matters, or of legal,
+commercial, philosophical, ethical or political position regarding
+them.
+
+The "Invariant Sections" are certain Secondary Sections whose titles
+are designated, as being those of Invariant Sections, in the notice
+that says that the Document is released under this License.  If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant.  The Document may contain zero
+Invariant Sections.  If the Document does not identify any Invariant
+Sections then there are none.
+
+The "Cover Texts" are certain short passages of text that are listed,
+as Front-Cover Texts or Back-Cover Texts, in the notice that says that
+the Document is released under this License.  A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
+
+A "Transparent" copy of the Document means a machine-readable copy,
+represented in a format whose specification is available to the
+general public, that is suitable for revising the document
+straightforwardly with generic text editors or (for images composed of
+pixels) generic paint programs or (for drawings) some widely available
+drawing editor, and that is suitable for input to text formatters or
+for automatic translation to a variety of formats suitable for input
+to text formatters.  A copy made in an otherwise Transparent file
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text.  A copy that is not "Transparent" is called "Opaque".
+
+Examples of suitable formats for Transparent copies include plain
+ASCII without markup, Texinfo input format, LaTeX input format, SGML
+or XML using a publicly available DTD, and standard-conforming simple
+HTML, PostScript or PDF designed for human modification.  Examples of
+transparent image formats include PNG, XCF and JPG.  Opaque formats
+include proprietary formats that can be read and edited only by
+proprietary word processors, SGML or XML for which the DTD and/or
+processing tools are not generally available, and the
+machine-generated HTML, PostScript or PDF produced by some word
+processors for output purposes only.
+
+The "Title Page" means, for a printed book, the title page itself,
+plus such following pages as are needed to hold, legibly, the material
+this License requires to appear in the title page.  For works in
+formats which do not have any title page as such, "Title Page" means
+the text near the most prominent appearance of the work's title,
+preceding the beginning of the body of the text.
+
+A section "Entitled XYZ" means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language.  (Here XYZ stands for a
+specific section name mentioned below, such as "Acknowledgements",
+"Dedications", "Endorsements", or "History".)  To "Preserve the Title"
+of such a section when you modify the Document means that it remains a
+section "Entitled XYZ" according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document.  These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
+
+
+2. VERBATIM COPYING
+
+You may copy and distribute the Document in any medium, either
+commercially or noncommercially, provided that this License, the
+copyright notices, and the license notice saying this License applies
+to the Document are reproduced in all copies, and that you add no other
+conditions whatsoever to those of this License.  You may not use
+technical measures to obstruct or control the reading or further
+copying of the copies you make or distribute.  However, you may accept
+compensation in exchange for copies.  If you distribute a large enough
+number of copies you must also follow the conditions in section 3.
+
+You may also lend copies, under the same conditions stated above, and
+you may publicly display copies.
+
+
+3. COPYING IN QUANTITY
+
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
+Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
+the back cover.  Both covers must also clearly and legibly identify
+you as the publisher of these copies.  The front cover must present
+the full title with all words of the title equally prominent and
+visible.  You may add other material on the covers in addition.
+Copying with changes limited to the covers, as long as they preserve
+the title of the Document and satisfy these conditions, can be treated
+as verbatim copying in other respects.
+
+If the required texts for either cover are too voluminous to fit
+legibly, you should put the first ones listed (as many as fit
+reasonably) on the actual cover, and continue the rest onto adjacent
+pages.
+
+If you publish or distribute Opaque copies of the Document numbering
+more than 100, you must either include a machine-readable Transparent
+copy along with each Opaque copy, or state in or with each Opaque copy
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
+
+It is requested, but not required, that you contact the authors of the
+Document well before redistributing any large number of copies, to give
+them a chance to provide you with an updated version of the Document.
+
+
+4. MODIFICATIONS
+
+You may copy and distribute a Modified Version of the Document under
+the conditions of sections 2 and 3 above, provided that you release
+the Modified Version under precisely this License, with the Modified
+Version filling the role of the Document, thus licensing distribution
+and modification of the Modified Version to whoever possesses a copy
+of it.  In addition, you must do these things in the Modified Version:
+
+A. Use in the Title Page (and on the covers, if any) a title distinct
+   from that of the Document, and from those of previous versions
+   (which should, if there were any, be listed in the History section
+   of the Document).  You may use the same title as a previous version
+   if the original publisher of that version gives permission.
+B. List on the Title Page, as authors, one or more persons or entities
+   responsible for authorship of the modifications in the Modified
+   Version, together with at least five of the principal authors of the
+   Document (all of its principal authors, if it has fewer than five),
+   unless they release you from this requirement.
+C. State on the Title page the name of the publisher of the
+   Modified Version, as the publisher.
+D. Preserve all the copyright notices of the Document.
+E. Add an appropriate copyright notice for your modifications
+   adjacent to the other copyright notices.
+F. Include, immediately after the copyright notices, a license notice
+   giving the public permission to use the Modified Version under the
+   terms of this License, in the form shown in the Addendum below.
+G. Preserve in that license notice the full lists of Invariant Sections
+   and required Cover Texts given in the Document's license notice.
+H. Include an unaltered copy of this License.
+I. Preserve the section Entitled "History", Preserve its Title, and add
+   to it an item stating at least the title, year, new authors, and
+   publisher of the Modified Version as given on the Title Page.  If
+   there is no section Entitled "History" in the Document, create one
+   stating the title, year, authors, and publisher of the Document as
+   given on its Title Page, then add an item describing the Modified
+   Version as stated in the previous sentence.
+J. Preserve the network location, if any, given in the Document for
+   public access to a Transparent copy of the Document, and likewise
+   the network locations given in the Document for previous versions
+   it was based on.  These may be placed in the "History" section.
+   You may omit a network location for a work that was published at
+   least four years before the Document itself, or if the original
+   publisher of the version it refers to gives permission.
+K. For any section Entitled "Acknowledgements" or "Dedications",
+   Preserve the Title of the section, and preserve in the section all
+   the substance and tone of each of the contributor acknowledgements
+   and/or dedications given therein.
+L. Preserve all the Invariant Sections of the Document,
+   unaltered in their text and in their titles.  Section numbers
+   or the equivalent are not considered part of the section titles.
+M. Delete any section Entitled "Endorsements".  Such a section
+   may not be included in the Modified Version.
+N. Do not retitle any existing section to be Entitled "Endorsements"
+   or to conflict in title with any Invariant Section.
+O. Preserve any Warranty Disclaimers.
+
+If the Modified Version includes new front-matter sections or
+appendices that qualify as Secondary Sections and contain no material
+copied from the Document, you may at your option designate some or all
+of these sections as invariant.  To do this, add their titles to the
+list of Invariant Sections in the Modified Version's license notice.
+These titles must be distinct from any other section titles.
+
+You may add a section Entitled "Endorsements", provided it contains
+nothing but endorsements of your Modified Version by various
+parties--for example, statements of peer review or that the text has
+been approved by an organization as the authoritative definition of a
+standard.
+
+You may add a passage of up to five words as a Front-Cover Text, and a
+passage of up to 25 words as a Back-Cover Text, to the end of the list
+of Cover Texts in the Modified Version.  Only one passage of
+Front-Cover Text and one of Back-Cover Text may be added by (or
+through arrangements made by) any one entity.  If the Document already
+includes a cover text for the same cover, previously added by you or
+by arrangement made by the same entity you are acting on behalf of,
+you may not add another; but you may replace the old one, on explicit
+permission from the previous publisher that added the old one.
+
+The author(s) and publisher(s) of the Document do not by this License
+give permission to use their names for publicity for or to assert or
+imply endorsement of any Modified Version.
+
+
+5. COMBINING DOCUMENTS
+
+You may combine the Document with other documents released under this
+License, under the terms defined in section 4 above for modified
+versions, provided that you include in the combination all of the
+Invariant Sections of all of the original documents, unmodified, and
+list them all as Invariant Sections of your combined work in its
+license notice, and that you preserve all their Warranty Disclaimers.
+
+The combined work need only contain one copy of this License, and
+multiple identical Invariant Sections may be replaced with a single
+copy.  If there are multiple Invariant Sections with the same name but
+different contents, make the title of each such section unique by
+adding at the end of it, in parentheses, the name of the original
+author or publisher of that section if known, or else a unique number.
+Make the same adjustment to the section titles in the list of
+Invariant Sections in the license notice of the combined work.
+
+In the combination, you must combine any sections Entitled "History"
+in the various original documents, forming one section Entitled
+"History"; likewise combine any sections Entitled "Acknowledgements",
+and any sections Entitled "Dedications".  You must delete all sections
+Entitled "Endorsements".
+
+
+6. COLLECTIONS OF DOCUMENTS
+
+You may make a collection consisting of the Document and other documents
+released under this License, and replace the individual copies of this
+License in the various documents with a single copy that is included in
+the collection, provided that you follow the rules of this License for
+verbatim copying of each of the documents in all other respects.
+
+You may extract a single document from such a collection, and distribute
+it individually under this License, provided you insert a copy of this
+License into the extracted document, and follow this License in all
+other respects regarding verbatim copying of that document.
+
+
+7. AGGREGATION WITH INDEPENDENT WORKS
+
+A compilation of the Document or its derivatives with other separate
+and independent documents or works, in or on a volume of a storage or
+distribution medium, is called an "aggregate" if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
+
+If the Cover Text requirement of section 3 is applicable to these
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
+
+
+8. TRANSLATION
+
+Translation is considered a kind of modification, so you may
+distribute translations of the Document under the terms of section 4.
+Replacing Invariant Sections with translations requires special
+permission from their copyright holders, but you may include
+translations of some or all Invariant Sections in addition to the
+original versions of these Invariant Sections.  You may include a
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers.  In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled "Acknowledgements",
+"Dedications", or "History", the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
+
+
+9. TERMINATION
+
+You may not copy, modify, sublicense, or distribute the Document except
+as expressly provided for under this License.  Any other attempt to
+copy, modify, sublicense or distribute the Document 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.
+
+
+10. FUTURE REVISIONS OF THIS LICENSE
+
+The Free Software Foundation may publish new, revised versions
+of the GNU Free Documentation 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.  See
+http://www.gnu.org/copyleft/.
+
+Each version of the License is given a distinguishing version number.
+If the Document specifies that a particular numbered version of this
+License "or any later version" applies to it, you have the option of
+following the terms and conditions either of that specified version or
+of any later version that has been published (not as a draft) by the
+Free Software Foundation.  If the Document does not specify a version
+number of this License, you may choose any version ever published (not
+as a draft) by the Free Software Foundation.
+
+
+ADDENDUM: How to use this License for your documents
+
+To use this License in a document you have written, include a copy of
+the License in the document and put the following copyright and
+license notices just after the title page:
+
+    Copyright (c)  YEAR  YOUR NAME.
+    Permission is granted to copy, distribute and/or modify this document
+    under the terms of the GNU Free Documentation License, Version 1.2
+    or any later version published by the Free Software Foundation;
+    with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
+    A copy of the license is included in the section entitled "GNU
+    Free Documentation License".
+
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the "with...Texts." line with this:
+
+    with the Invariant Sections being LIST THEIR TITLES, with the
+    Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
+
+If your document contains nontrivial examples of program code, we
+recommend releasing these examples in parallel under your choice of
+free software license, such as the GNU General Public License,
+to permit their use in free software.

COPYING.BSD

@@ -0,0 +1,20 @@
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1. Redistributions of source code must retain the above copyright
+   notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+   notice, this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

COPYING.LIB

@@ -0,0 +1,486 @@
+NOTE! The LGPL below is copyrighted by the Free Software Foundation, but 
+the instance of code that it refers to (the kde libraries) are copyrighted 
+by the authors who actually wrote it.
+				   
+---------------------------------------------------------------------------
+		  GNU LIBRARY GENERAL PUBLIC LICENSE
+		       Version 2, June 1991
+
+ Copyright (C) 1991 Free Software Foundation, Inc.
+                    51 Franklin Street, 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 Street, 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!

DEBUG

@@ -0,0 +1,184 @@
+Introduction
+============
+
+This is a short tutorial on debugging KDE applications. Throughout this
+tutorial I will use "kedit" as example application.
+
+
+Configuring for debugging
+=========================
+
+You can use --enable-debug with the configure script, if you want to have
+debug code in your KDE libs. If you have the space and can stand code that's
+somewhat slower, this is worth it. The extra information really
+helps debugging and thus bugfixing.
+
+On the other hand, --disable-debug removes all debug messages, leading
+to a faster and cleaner desktop.
+
+
+Debugging with GDB
+==================
+
+The recommended version of gdb to use is version 4.95 or higher, older 
+versions have problems generating proper backtraces.
+
+There are three ways to debug an application with gdb:
+
+1) You can start the application from within gdb.
+2) You can attach gdb to an already running application.
+3) You can run gdb after an application has crashed using a core file.
+
+
+Starting applications from within gdb
+=====================================
+
+To start an application with gdb you can start gdb as follows:
+
+> gdb kedit
+GNU gdb 4.95.0
+Copyright 2000 Free Software Foundation, Inc.
+GDB is free software, covered by the GNU General Public License, and you are
+welcome to change it and/or distribute copies of it under certain conditions.
+Type "show copying" to see the conditions.
+There is absolutely no warranty for GDB.  Type "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+(gdb) 
+
+You can now set the command line arguments that you want to pass to kedit with 
+the gdb command "set args":
+
+(gdb) set args myfile.txt
+(gdb) 
+
+gdb has loaded the kedit executable on startup but it hasn't loaded any of 
+the libraries yet. This means that you can set any breakpoints in the 
+libraries yet. The easiest way to do that is to set a breakpoint in the
+first line of main and then start the program:
+
+(gdb) break main
+Breakpoint 1 at 0x804855c
+(gdb) run
+Starting program: /opt/kde/bin/kedit myfile.txt
+Breakpoint 1 at 0x4002cf18: file kedit.cpp, line 1595.
+ 
+Breakpoint 1, main (argc=2, argv=0xbffff814) at kedit.cpp:1595
+1595            bool have_top_window = false;
+Current language:  auto; currently c++
+(gdb)  
+
+You can now set breakpoints everywhere. For example lets set a breakpoint 
+in the KApplication constructor. Unfortunately gdb is not very good in 
+handling C++ names, so it is not really possible to specify the constructor
+directly after the break command. Instead we look up a line of source
+code where we want to place the breakpoint. An external editor is of great 
+use at this point. With the list command we can select the source file we
+are interested in and verify that we have found the correct source line:
+
+(gdb) list kapp.cpp:220
+215         parseCommandLine( argc, argv );
+216     }
+217
+218     KApplication::KApplication( bool allowStyles, bool GUIenabled ) :
+219       QApplication( *KCmdLineArgs::qt_argc(), *KCmdLineArgs::qt_argv(),
+220                     GUIenabled ),
+221       KInstance( KCmdLineArgs::about),
+222       d (new KApplicationPrivate)
+223     {
+224         if (!GUIenabled)
+(gdb) break 224
+Breakpoint 2 at 0x4048aa7e: file kapp.cpp, line 224.
+(gdb) 
+
+We can now continue the execution of kedit. Execution will stop when it hits
+a breakpoint of when the program exits. In this case execution will stop
+in the first line of the KApplication constructor:
+
+(gdb) continue
+Continuing.
+Qt: gdb: -nograb added to command-line options.
+         Use the -dograb option to enforce grabbing.
+ 
+Breakpoint 2, KApplication::KApplication (this=0xbffff6a8, allowStyles=true,
+    GUIenabled=true) at kapp.cpp:224
+224         if (!GUIenabled)
+(gdb) 
+
+
+Attaching gdb to already running applications
+=============================================
+
+Sometimes it is not practical to start an application from within gdb.
+E.g. in those cases where you didn't know the application was about to
+crash :-) When you get the friendly DrKonqi dialog informing you about 
+a crash you are just in time to start your debugger.
+
+First lets attach gdb to an application that hasn't crashed (yet).
+
+You start with finding the process of the application with e.g. "ps -aux":
+
+> ps -aux | grep kedit 
+bastian  21570 15.1  6.8 13740 8800 pts/6    S    15:34   0:01 kedit
+bastian  21582  0.0  0.3  1132  412 pts/6    R    15:34   0:00 grep kedit
+
+From this you learn that kedit has process id 21570. Now you can start gdb as
+follows:
+
+> gdb kedit 21570
+GNU gdb 4.95.0
+Copyright 2000 Free Software Foundation, Inc.
+GDB is free software, covered by the GNU General Public License, and you are
+welcome to change it and/or distribute copies of it under certain conditions.
+Type "show copying" to see the conditions.
+There is absolutely no warranty for GDB.  Type "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+/home1/bastian/21570: No such file or directory.
+Attaching to program: /opt/kde/bin/kedit, Pid 21570
+Reading symbols from /opt/kde/lib/kedit.so.0...done.
+Loaded symbols for /opt/kde/lib/kedit.so.0
+....
+Reading symbols from /lib/ld-linux.so.2...done.
+Loaded symbols for /lib/ld-linux.so.2
+Reading symbols from /lib/libnss_compat.so.2...done.
+Loaded symbols for /lib/libnss_compat.so.2
+Reading symbols from /lib/libnsl.so.1...done.
+Loaded symbols for /lib/libnsl.so.1
+0x40c3d88e in __select () from /lib/libc.so.6
+(gdb)  
+
+You will usually end up in the middle of a select() call from the event-loop.
+This is the place where a KDE application spends most of its time, waiting
+for things to happen.
+
+A backtrace will typically look something like this:
+
+(gdb) bt
+#0  0x40c3d88e in __select () from /lib/libc.so.6
+#1  0x40a22844 in __DTOR_END__ () at fam.c++:356
+#2  0x407293bf in QApplication::enter_loop (this=0xbffff6e8)
+    at kernel/qapplication.cpp:2552
+#3  0x406b1d7b in QApplication::exec (this=0xbffff6e8)
+    at kernel/qapplication_x11.cpp:2217
+#4  0x4002d500 in main (argc=1, argv=0xbffff854) at kedit.cpp:1662
+#5  0x40bbba5e in __libc_start_main (main=0x8048568 <main>, argc=1,
+    argv=0xbffff854, init=0x8048514 <_init>, fini=0x80486cc <_fini>,
+    rtld_fini=0x4000aa20 <_dl_fini>, stack_end=0xbffff84c)
+    at ../sysdeps/generic/libc-start.c:92
+(gdb)
+
+
+Getting core dumps
+==================
+
+If you want to have a core dump after your application crashes you need to 
+do two things:
+
+1) Disable the KDE crash handler. This can be done either by using the 
+--nocrashhandler command line option or by setting the KDE_DEBUG environment
+variable to some value e.g. KDE_DEBUG=true.
+
+2) Enable core dump generation by changing the so called 'ulimits' with the
+following command: 
+	ulimit -c unlimited
+
+

INSTALL

@@ -0,0 +1,173 @@
+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 a while.  While running, it prints some
+     messages telling which features it is checking for.
+
+  2. Type `make' to compile the package.
+
+  3. Type `make install' to install the programs and any data files and
+     documentation.
+
+  4. 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/kde/bin', `/usr/local/kde/lib', etc.  You can specify an
+installation prefix other than `/usr/local/kde' 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.
+
+   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.
+

KDE2PORTING.html

@@ -0,0 +1,925 @@
+<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Level 2//EN//2.0">
+<HTML>
+<HEAD>
+	<TITLE>Guide to Porting Applications to KDE 2.0</TITLE>
+</HEAD>
+<BODY>
+
+<H2>Porting Applications to KDE 2.0</H2>
+<H3>Last Modified on November 28, 2000</H3>
+This document contains the changes you have to apply to programs written for
+KDE1.1 when you want to port them to KDE2.0.<P>
+
+As a start you should have a look at doc/porting.doc in the Qt package,
+or <a href="http://doc.trolltech.com/porting.html">this page online</a>.<P>
+
+<H3><A NAME="TOC">Table of Contents</A></H3>
+
+<UL>
+<LI><A HREF="#gettingstarted">Getting Started</A></LI>
+<LI><A HREF="#general">Global changes</A></LI>
+<LI><A HREF="#automoc">automoc/am_edit, Makefile.am tags</A></LI>
+<LI><A HREF="#KApplication">KApplication</A></LI>
+<LI><A HREF="#KCmdLineArgs">KCmdLineArgs</A></LI>
+<LI><A HREF="#KLocale">KLocale</A></LI>
+<LI><A HREF="#KGlobal">KGlobal: access to KDE global objects.</A></LI>
+<LI><A HREF="#KIconLoader">KIconLoader</A></LI>
+<LI><A HREF="#KTMainWindow">KTMainWindow</A></LI>
+<LI><A HREF="#KHelpMenu">KHelpMenu</A></LI>
+<LI><A HREF="#KToolBar">KToolBar</A></LI>
+<LI><A HREF="#launching">Starting other programs</A></LI>
+<LI><A HREF="#khtmlw">khtmlw</A></LI>
+<LI><A HREF="#KIntegerLine">KIntegerLine, KIntLineEdit</A></LI>
+<LI><A HREF="#KDNDIcon">KDNDIcon, KDNDDropZone, KDNDWidget, kdecore/drag.h</A></LI>
+<LI><A HREF="#KConfigBase">KConfigBase, KConfig, KSimpleConfig</A></LI>
+<LI><A HREF="#libkfm">libkfm</A></LI>
+<LI><A HREF="#KDialog">KDialog</A></LI>
+<LI><A HREF="#kcharsets">kcharsets</A></LI>
+<LI><A HREF="#KWizard">KWizard, KNoteBook</A></LI>
+<LI><A HREF="#KSpinBox">KSpinBox, KNumericSpinBox</A></LI>
+<LI><A HREF="#KClipboard">KClipboard</A></LI>
+<LI><A HREF="#KPanner">KPanner, KNewPanner</A></LI>
+<LI><A HREF="#KTreeList">KTreeList, KTreeListItem</A></LI>
+<LI><A HREF="#KMsgBox">KMsgBox</A></LI>
+<LI><A HREF="#KCombo">KCombo</A></LI>
+<LI><A HREF="#KQuickHelp">KQuickHelp</A></LI>
+<LI><A HREF="#KPixmapgradientFill">KPixmap::gradientFill</A></LI>
+<LI><A HREF="#KTabListBox">KTabListBox</A></LI>
+<LI><A HREF="#KToolBarButton">KToolBarButton &amp; KRadioGroup</A></LI>
+<LI><A HREF="#KAccel">KAccel</A></LI>
+<LI><A HREF="#kstring">kstring.h / KString</A></LI>
+<LI><A HREF="#ktopwidget">ktopwidget.h / KTopWidget</A></LI>
+<LI><A HREF="#kbutton">kbutton.h / KButton</A></LI>
+<LI><A HREF="#kbuttonbox">kbuttonbox.h / KButtonBox</A></LI>
+<LI><A HREF="#kcolorgroup">kcolorgroup.h / KColorGroup</A></LI>
+<LI><A HREF="#kled">kled.h, kledlamp.h / KLed, KLedLamp</A></LI>
+<LI><A HREF="#KDockWidget">KDockWidget</A></LI>
+<LI><A HREF="#KPixmap">KPixmap, KPixmapEffect</A></LI>
+<LI><A HREF="#KControlCenter">KDE Control Center</A></LI>
+<LI><A HREF="#KWMModuleApplication">KWMModuleApplication libkdeui/kwmmapp.h</A></LI>
+<LI><A HREF="#KDebug">KDebug</A></LI>
+<LI><A HREF="#KFileDialog">KFileDialog - General Stuff</A></LI>
+<LI><A HREF="#KFileDialogPreview">KFileDialog - Preview Mode</A></LI>
+<LI><A HREF="#ImageEffects">Image Effects</A></LI>
+<LI><A HREF="#KAudio">KAudio (kaudio.h)</A></LI>
+<LI><A HREF="#KImageIO">KImageIO (kimgio.h)</A></LI>
+</UL>
+
+<H3><A NAME="gettingstarted">Getting started</A></H3>
+
+  The first step to get your KDE application to compile under KDE 2.0,
+  is to detect KDE 2.0 and Qt 2.x at configure time. The easiest way to
+  get a working autoconf/automake framework, is to either use 
+  <a href="http://www.kdevelop.org">KDevelop</a> or
+  <a href="http://home.earthlink.net/~granroth/kapptemplate/index.html">kapptemplate</a>
+  (available in CVS under the module "kdesdk"), to generate a new
+  application template. Replace the generated source files by yours
+  and adapt Makefile.am accordingly.
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="general">Global changes</A></H3>
+
+  We did our best to clean up the header files of kdelibs, so they do
+  not include unnecessary bloat for your application. As a consequence, you
+  may notice that some header files are missing from your source files as
+  they have been included before by kapp.h for example. There is a script
+  in kdesdk/scripts called "fixheaders" that takes care of most of these
+  cases. Just call "make -k 2&gt;&amp;1 | perl .../fixheaders" and it will try
+  to look after the error messages and add includes as it recognize the
+  errors.<P>
+
+  Also, if your code does not compile and complains about missing member
+  functions, you should check for methods that started with get...().
+  These methods have been renamed to xy*() for consistency.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="automoc">automoc/am_edit, Makefile.am tags</A></H3>
+
+  On the subject of the compilation framework, automoc has been removed from
+  the admin directory. It has been replaced by am_edit which provides a lot of
+  additional features.<P>
+  METASOURCES=AUTO still does the job of generating the appropriate moc files,
+  but in addition, you should use KDE_ICON for the icons representing the application
+  (and naming those icons conforming to lo16-app-&lt;appname&gt;.png), and install
+  the application-specific icons under $(kde_datadir)/&lt;appname&gt;/pics.
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KApplication">KApplication</A></H3>
+
+  doesn't hold any longer a KLocale instance. With this getLocale()
+  and isLocaleInstantiated are now replaced by KGlobal::locale()<P>
+
+  it also doesn't hold a KiconLoader instance. As this also getIconLoader()
+  has been removed. Replace kapp-&gt;getIconLoader()-&gt;loadIcon() with
+  BarIcon() or use KGlobal::iconLoader() instead of getIconLoader()<P>
+
+  kde_*dir() have been removed as they require a unique top level directory
+  for all applications (KDEDIR). This concept doesn't exist in KDE 2.0
+  any more, it has been replaced with "multiple levels of directories",
+  set in KDEDIRS, so that it's possible to have global settings and
+  group settings, applied before user settings.<P>
+
+  Replace code that uses kde_*dir() + filename with calls to
+  locate(filetype, filename) where filetype is what * used to be
+  in kde_*dir(). locate is defined as function in kstddirs.h to call
+  KGlobal::dirs()-&gt;findResource.<P>
+
+  Use locateLocal to get the path of a writable file. For instance,
+  KApplication::localconfigdir()+filename is now locateLocal( "config", filename ),
+  but for most cases, simply using KGlobal::config() is enough, if you're happy
+  with saving the application's configuration into appnamerc, or
+  KSimpleConfig cfg("anothercfgfile") to create a config file with another name.<P>
+
+  generalFont() and fixedFont() are deprecated and will be removed soon.
+  Please use KGlobalSettings::generalFont() and KGlobalSettings::fixedFont() instead.<P>
+
+  appName() is deprecated. Please use QApplication::name() or instanceName
+  instead.<P>
+
+  The methods tempSaveName() and checkRecoverFile() return QString
+  now. The returned values must _not_ be free()d.<P>
+
+  helpMenu() has been moved to KMainWindow. aboutKDE(), aboutApp() and
+  appHelpActivated() have all been removed See section for KMainWindow
+  for more info.<P>
+
+  The KApplication constructor has changed. Command line arguments and
+  program name should no longer be passed to KApplication but to 
+  KCmdLineArgs. KCmdLineArgs performs command line parsing and a command
+  line help. See below for more info.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KCmdLineArgs">KCmdLineArgs</A></H3>
+
+  KCmdLineArgs is a new class that handles command line parsing and
+  command line help. It is now required that your application
+  specifies at least:<P>
+  <UL>
+	<LI>Its name.
+	<LI>A short description what it does. (e.g. 1 line)
+	<LI>A version.
+	<LI>All command line options that it supports.
+  </UL>
+ 
+  KCmdLineArgs itself will add the command line options supported by Qt 
+  and KApplication.<P>
+
+  You can also use the KAboutData class to specify name, description and 
+  version.<P>
+
+  In return for this information you can query KCmdLineArgs whether an 
+  certain option was specified on the command line and your application 
+  now automatically supports --help and --version. It aborts with a
+  useful error message when the command line contains a syntax error.
+  See kdelibs/kdecore/kcmdlineargs.h for more info.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KLocale">KLocale</A></H3>
+
+  i18n is no longer a macro<P>
+
+  KApplication::getApplication()-&gt;getLocale()-&gt;translate<P>
+
+  but a function on its own. klocale is obsolete and replace every call
+  to klocale-&gt;translate with i18n.<P>
+
+  The return value of i18n is also no longer a const char*,
+  but a unicode QString.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KGlobal">KGlobal: access to KDE global objects.</A></H3>
+
+KGlobal allows centralized access to KDE global objects without including
+extraneous headers. object creation is deferred if possible.<P>
+
+All methods are static and headers for returned types are not included. You
+must have created a KApplication object before the methods can be used.<P>
+<TABLE BORDER="0">
+<TR>
+  <TD COLSPAN="2">
+    <PRE>
+      #include &lt;kglobal.h&gt;
+      #include &lt;kconfig.h&gt;      // Needed to use KConfig
+      #include &lt;klocale.h&gt;      // Needed to use KLocale
+      #include &lt;kiconloader.h&gt;  // Needed to use KIconLoader
+    </PRE>
+  </TD>
+</TR>
+<TR>
+  <TD>
+    <PRE>
+    ...
+        	KConfig *appcfg = KGlobal::config();
+	        QString mystr	 = i18n( "This is a string" );
+
+
+		KIconLoader *loader = KGlobal::iconLoader();
+    </PRE>
+  </TD>
+</TR>
+</TABLE>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KIconLoader">KIconLoader</A></H3>
+
+KIconLoader in 1.1 used to mix icons for applications and for toolbars.
+This has changed, so you may notice that your application doesn't find
+the right icons. loadIcon (used by BarIcon) returns only toolbar icons.<P>
+If you need icons for applications, use loadApplicationIcon.<P>
+loadMiniIcon and loadApplicationMiniIcon have been removed, instead
+loadApplicationIcon now takes a "size" argument where you can specify the
+size of the icon (small, medium, large).<P>
+The other big change you may notice, is that ICON and Icon have been
+removed as they caused big confusion for not loading application icons
+(see above). For this we added BarIcon which does the same as ICON before.
+The third change in this row is that loadIcon doesn't need the extension
+anymore, but looks for standard extensions (png, xpm) itself. If you hard-
+coded .xpm, loadIcon will issue a warning at runtime, but will still work
+in stripping off the .xpm part<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KTMainWindow">KTMainWindow</A></H3>
+
+KTMainWindow has been replaced with KMainWindow.<p>
+
+The KMainWindow constructor needs a parent widget as first argument. 
+You can use 0 for this.<p>
+setView() has been replaced with setCentralWidget().<p>
+view() has been replaced with centralWidget().<p>
+addToolBar() has been removed, it is not needed any more.<p>
+setMenu(...) has been removed, it is not needed any more.<p>
+setStatusBar(...) has been removed, it is not needed any more.<p>
+updateRects() has been removed, it is not needed any more.<p>
+enableStatusBar(...) has been removed, use statusBar()-&gt;show() and/or
+statusBar()-&gt;hide() instead.<p>
+enableToolBar(...) has been removed, use toolBar()-&gt;show() and/or 
+toolBar()-&gt;hide() instead. <p>
+
+view_* public variables do no longer exist. There is really no reason
+for an app to use this information. If you do need it anyway, use
+mainViewGeometry() instead.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KHelpMenu">KHelpMenu</A></H3>
+
+helpMenu() has been moved to KMainWindow from KApplication (kapp).<P>
+
+Both the "About KDE" and the "About &lt;Application&gt;" dialog boxes
+are now modeless. "About KDE" is a completely new widget.<P>
+
+If you used in the toplevel window (that is derived from KMainWindow)
+"kapp-&gt;helpMenu( bool, QString )" to get the help menu
+you must now change this to "helpMenu( QString )". The QString defaults
+to QString::null so it is sufficient to write helpMenu().<P>
+
+The old aboutKDE(), aboutApp() and appHelpActivated() of KApplication
+have all been removed. If you need direct access to these or need
+access to a help menu in a class that is not derived from
+KMainWindow then allocate an instance of the new class KHelpMenu.
+See KDE 2.0 API reference or khelpmenu.h (kdeui) for additional info.<P>
+Espen Sand &lt;<A HREF="mailto:espen@kde.org">espen@kde.org</A>&gt;<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KToolBar">KToolBar</A></H3>
+
+enable(...) is depreciated, use show()/hide() instead.<p>
+enableFloating(...) has been removed, use enableMoving() instead.<p>
+setMaxHeight() is depreciated, use setMaximumHeight() instead.<p>
+maxHeight() is depreciated, use maximumHeight() instead.<p>
+setMaxWidth() is depreciated, use setMaximumWidth() instead.<p>
+maxWidth() is depreciated, use maximumWidth() instead.<p>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="launching">Starting other programs</A></H3>
+
+In KDE 2.0 there are several ways to start other programs from within
+your application. Here is a short summary of your options with reasons why
+you should or should not use them.
+<H4>1. fork + exec</H4>
+<P>
+You never want to use this unless you have a very good reason why it is 
+impossible to use KProcess.
+</P>
+<H4>2. KProcess</H4>
+<P>
+You want to use this if you need to start a new process which needs to be a 
+child of your process, e.g. because you want to catch stdout/stderr or need 
+to send it data via stdin. You should never use this to start other KDE 
+applications unless your application is called kgdb :-) If you need to
+send/receive text like data to/from the process, you are probably better 
+off with KProcIO
+</P>
+
+<H4>3. KProcIO</H4>
+<P>
+Like KProcess. Unlike KProcess, this class actually makes it easy to 
+send data to and receive data from the process.
+
+</P>
+<H4>4. startServiceByDesktopPath</H4>
+<P>
+Preferred way to launch desktop (KDE/Gnome/X) applications or KDE services. 
+The application/service must have a .desktop file. It will make use of 
+KDEinit for increased startup performance and lower memory usage. These 
+benefits only apply to applications available as KDEinit loadable module (KLM)
+</P>
+<H4>5. KRun</H4>
+<P>
+Generic way to open documents/applications/shell commands. Uses
+startServiceBy.... where applicable. Offers the additional 
+benefit of startup-notification.<BR>
+KRun can start any application, from the binary or the desktop file,
+it will determine the mimetype of a file before running the
+preferred handler for it, and it can also start shell commands.
+This makes KRun the recommended way to run another program in KDE 2.
+</P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="khtmlw">khtmlw</A></H3>
+
+khtmlw has been replaced with khtml.<BR>
+<UL>
+	<LI>KHTMLView has vanished. Just use KHTMLWidget, which does scrollbar
+  managing for free.
+
+	<LI>A lot of the API has changed. If you just want to open a file/URL,
+  you just need to do:<P>
+  <PRE>
+	KHTMLWidget *w = new KHTMLWidget();
+	w-&gt;openURL(myURL);
+  </PRE>
+
+	<LI>khtml uses QString's instead of char *'s now. This means, that most
+  of the api has changed. In all functions:<P>
+  <PRE>
+     const char * -&gt; QString
+     QStrList -&gt; QStringList
+  </PRE>
+  The only exception for the moment is KHTMLWidget::write(), which does
+  also exist in a const char * version.<P>
+
+
+<LI>you won't need the getKHTMLWiget function anymore. Just replace
+	getKHTMLWidget-&gt;xxx() with xxx()<P>
+<LI>xxx(QString) -&gt; xxx(const QString &amp;)<P>
+<LI>consistent naming. All getXyz() functions are renamed to xyz()<P>
+<LI>replaced/changed functions:<P>
+<TABLE BORDER="1">
+<TR>
+<TD>KHTMLWidget::setDefaultFontBase()</TD>
+<TD>-&gt; setFontSizes()</TD>
+</TR>
+<TR>
+<TD>x/yOffset()</TD>
+<TD>-&gt; contentsX/Y()</TD>
+</TR>
+<TR>
+<TD>getSelectedText(QString &amp;)</TD>
+<TD>-&gt; QString selectedText()</TD>
+</TR>
+<TR>
+<TD COLSPAN="2" ROWSPAN="0">findTextEnd() has vanished. just remove the call from your code</TD>
+</TR>
+<TR>
+<TD>gotoXY(x, y)</TD>
+<TD>-&gt; setContentsPos(x, y)</TD>
+</TR>
+<TR>
+<TD>docWidth()</TD>
+<TD>-&gt; contentsWidth()</TD>
+</TR>
+<TR>
+<TD>docHeight()</TD>
+<TD>-&gt; contentsHeight()</TD>
+</TR>
+</TABLE><P>
+
+<LI>Don't forget to change the link-flags! (-lkhtml -lkjava instead of -lkhtmlw)
+</UL>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KIntegerLine">KIntegerLine, KIntLineEdit</A></H3>
+
+  KIntegerLine and KIntLineEdit  have been replaced by KIntNumInput.
+  The new header file is called knuminput.h.<P>
+
+  The new KIntNumInput can have an optional slider attached, ensures
+  that the entered value is in a given range (use MAX_INT or similar
+  if you don't care about the range) and can maintain a descriptive
+  label and also a unit for the edited value.<P>
+
+  The API is almost the same and it simplifies existing code a bit,
+  so give it a try. If you need more functionality, please contact
+  me, Dirk A. Mueller &lt;<A HREF="mailto:mueller@kde.org">mueller@kde.org</A>&gt;.<P>
+
+  The additional class KDoubleNumInput gives you the same look &amp; feel,
+  but allows you to edit floating point numbers.<P>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KDNDIcon">KDNDIcon, KDNDDropZone, KDNDWidget, kdecore/drag.h</A></H3>
+
+KDE Drag and Drop is Dead.  Long live Qt Xdnd.<P>
+
+Xdnd is better anyway, because it has been adopted by all the other
+major GUI toolkits still under active development (this precludes
+Motif, but maybe we can convince the lesstif guys!).  Some changes
+are necessary to convert your old KDND-based stuff to Qt DND.<P>
+<UL>
+<LI>Remove drag.h from all of your sources / header files.<P>
+<LI>Remove KDNDDropZone object creations.  Instead of creating an
+  object of this type and then connecting it to some arbitrary slot
+  to handle drops, call "setAcceptDrops(true)" in your widget
+  constructor and then override the protected methods dragEnterEvent,
+  dragMoveEvent, dragLeaveEvent, and dropEvent.<P>
+<LI>You should be aware that to handle drops, you will either have to
+  inherit a widget and then override the methods mentioned above,
+  or install an event handler for the widget in that widget's parent,
+  and then handle QEvent::DragMove or QEvent::Drop inside there (if
+  you want to avoid inheritance).<P>
+<LI>You can emulate the old DndURL drop-type behavior with the Qt
+  Drag Object type QUriList.<P>
+<LI>You can start a drag from inside your widget's mouseMoveEvent
+  method if you wish.<P>
+<LI>Qt includes a Drag and Drop tutorial.  We suggest you read that
+  now if you are confused.<P>
+<LI>QMultiLineEdit has already a DnD interface that accepts text/*
+  If you want to add support for other mimetypes, you need to
+  re-implement all DnD-methods (also dragMoveEvent()) and pass
+  QTextDrag's to the parent methods.<P>
+<LI>QTextDrag also accepts text/uri-list, which means that you
+  always need to check for QUriDrag first if you want to get
+  both working.<P>
+<LI>The mimetype for Uri's is now text/uri-list. If you've used
+  the proprietary Qt 1.x url/url, you need to adjust that.
+</UL>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KConfigBase">KConfigBase, KConfig, KSimpleConfig</A></H3>
+
+  These classes have been largely re-implemented.  The external API
+  remains mostly the same, with the single notable change that
+  the groupIterator and entryIterator methods have been removed and
+  instead replaced by groupList (which returns a QStringList of groups)
+  and entryMap(const QString &amp;group) (which returns a QMap of entries
+  in the specified group).  This is due to internal changes in KConfig
+  which would make providing iterators possibly rather difficult.<P>
+
+  Much more extensive documentation on the KConfig and friends API can
+  be found in the kdoc generated documentation from the header files,
+  and in kdecore/KCONFIG_DESIGN.<P>
+
+  To use the new iterator, you will probably want to do something like
+  this:<P>
+  <PRE>
+
+  QMap&lt;QString, QString&gt; tmpMap = config-&lt;entryMap(myGroup);
+  QMap&lt;QString, QString&gt;::Iterator aIt(tmpMap.begin());
+
+  for (; aIt != tmpMap.end(); ++aIt) {
+   // body here.  Access iterator key as aIt.key(),
+   // data as *aIt.
+  }
+  </PRE>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="libkfm">libkfm has disappeared</A></H3>
+
+  Lots of other functionalities have been taken out of kfm, some being
+  now in libkio, some in libkonq.<P>
+ <STRONG> Replacement table :</STRONG><P>
+<TABLE BORDER="1">
+
+<TR><TD>KFM::download         </TD><TD>-&gt; KIO::NetAccess::download (kdelibs/kio/netaccess.h)</TD></TR>
+<TR><TD>KFM::removeTempFile   </TD><TD>-&gt; KIO::NetAccess::removeTempFile</TD></TR>
+<TR><TD COLSPAN="2" ROWSPAN="0">refreshDesktop, sortDesktop, selectRootIcons : removed; kdesktop handles it</TD></TR>
+<TR><TD>KFM::configure        </TD><TD>-&gt; see konqueror DCOP interface</TD></TR>
+<TR><TD>KFM::openURL          </TD><TD>-&gt; "(void) new KRun (url)" (kdelibs/kio/krun.h)</TD></TR>
+<TR><TD>KFM::refreshDirectory </TD><TD>-&gt; not needed anymore since konqy/kdesktop use KDirWatch</TD></TR>
+<TR><TD>KFM::openProperties   </TD><TD>-&gt; "(void) new KPropertiesDialog (url)" (kdelibs/kfile/kpropsdlg.h)</TD></TR>
+<TR><TD>KFM::exec             </TD><TD>-&gt; "(void) new KRun (url)" (kdelibs/kio/krun.h)</TD></TR>
+<TR><TD>KFM::copy, KFM::move  </TD><TD>-&gt; KIO::Job (async, see kio/job.h)<BR>
+                            or KIO::NetAccess (sync, see kio/netaccess.h)</TD></TR>
+<TR><TD>DlgLocation           </TD><TD>-&gt; Use KLineEditDlg (kdeui/klineeditdlg.h) instead</TD></TR>
+</TABLE>
+
+<H4><P ALIGN="RIGHT"><A HREF="#TOC">Return to the Table of Contents</A></P></H4>
+
+<H3><A NAME="KDialog">KDialog</A></H3>
+
+KDialog is no longer defined in kwizard.h. Include kdialog.h instead.<P>
+Note that the best way to write new dialogs is to use KDialogBase (see kdialogbase.h)<P>
+