Browse Source

Added abandoned KDE3 version of kdirstat


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kdirstat@1088039 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
tags/v3.5.13
tpearson 9 years ago
commit
b6e09a3a8e
83 changed files with 37255 additions and 0 deletions
  1. 1
    0
      AUTHORS
  2. 280
    0
      COPYING
  3. 482
    0
      COPYING.LIB
  4. 18
    0
      CREDITS
  5. 684
    0
      ChangeLog
  6. 167
    0
      INSTALL
  7. 48
    0
      Makefile.am
  8. 14
    0
      Makefile.cvs
  9. 14
    0
      Makefile.dist
  10. 20
    0
      README
  11. 52
    0
      TODO
  12. 11360
    0
      acinclude.m4
  13. 1045
    0
      aclocal.m4
  14. 191
    0
      build-howto.html
  15. 243
    0
      config.h.in
  16. 2
    0
      configure.files
  17. 109
    0
      configure.in
  18. 6
    0
      configure.in.in
  19. 2
    0
      doc/Makefile.am
  20. 11
    0
      doc/en/Makefile.am
  21. BIN
      doc/en/feedback-mail.png
  22. 1954
    0
      doc/en/index.docbook
  23. BIN
      doc/en/kdirstat-config-cleanups.png
  24. BIN
      doc/en/kdirstat-config-tree-colors.png
  25. BIN
      doc/en/kdirstat-main.png
  26. 153
    0
      kdirstat.kdevprj
  27. 14
    0
      kdirstat.lsm
  28. 70
    0
      kdirstat.spec
  29. 98
    0
      kdirstat/Makefile.am
  30. 9
    0
      kdirstat/fix_move_to_trash_bin.pl
  31. BIN
      kdirstat/hi16-app-kdirstat.png
  32. BIN
      kdirstat/hi32-app-kdirstat.png
  33. 93
    0
      kdirstat/kactivitytracker.cpp
  34. 109
    0
      kdirstat/kactivitytracker.h
  35. 432
    0
      kdirstat/kcleanup.cpp
  36. 360
    0
      kdirstat/kcleanup.h
  37. 283
    0
      kdirstat/kcleanupcollection.cpp
  38. 225
    0
      kdirstat/kcleanupcollection.h
  39. 71
    0
      kdirstat/kdirsaver.cpp
  40. 75
    0
      kdirstat/kdirsaver.h
  41. 20
    0
      kdirstat/kdirstat.desktop
  42. 6
    0
      kdirstat/kdirstat.upd
  43. 14
    0
      kdirstat/kdirstat_part.rc
  44. 847
    0
      kdirstat/kdirstatapp.cpp
  45. 421
    0
      kdirstat/kdirstatapp.h
  46. 184
    0
      kdirstat/kdirstatfeedback.cpp
  47. 115
    0
      kdirstat/kdirstatmain.cpp
  48. 1056
    0
      kdirstat/kdirstatsettings.cpp
  49. 744
    0
      kdirstat/kdirstatsettings.h
  50. 189
    0
      kdirstat/kdirstatui.rc
  51. 1636
    0
      kdirstat/kdirtree.cpp
  52. 1437
    0
      kdirstat/kdirtree.h
  53. 417
    0
      kdirstat/kdirtreeiterators.cpp
  54. 386
    0
      kdirstat/kdirtreeiterators.h
  55. 1956
    0
      kdirstat/kdirtreeview.cpp
  56. 889
    0
      kdirstat/kdirtreeview.h
  57. 503
    0
      kdirstat/kfeedback.cpp
  58. 460
    0
      kdirstat/kfeedback.h
  59. 311
    0
      kdirstat/kpacman.cpp
  60. 265
    0
      kdirstat/kpacman.h
  61. 150
    0
      kdirstat/kstdcleanup.cpp
  62. 65
    0
      kdirstat/kstdcleanup.h
  63. 608
    0
      kdirstat/ktreemaptile.cpp
  64. 323
    0
      kdirstat/ktreemaptile.h
  65. 745
    0
      kdirstat/ktreemapview.cpp
  66. 446
    0
      kdirstat/ktreemapview.h
  67. BIN
      kdirstat/lo16-app-kdirstat.png
  68. BIN
      kdirstat/lo32-app-kdirstat.png
  69. 2
    0
      kdirstat/pics/Makefile.am
  70. BIN
      kdirstat/pics/hi16-action-symlink.png
  71. BIN
      kdirstat/pics/hi16-action-symlink.xcf
  72. BIN
      kdirstat/pics/hi32-action-symlink.png
  73. BIN
      kdirstat/pics/hi48-action-symlink.png
  74. BIN
      kdirstat/pics/hi48-action-symlink.xcf
  75. BIN
      kdirstat/pics/lo16-action-symlink.png
  76. 6
    0
      po/Makefile.am
  77. 963
    0
      po/de.po
  78. 726
    0
      po/fr.po
  79. 733
    0
      po/hu.po
  80. 960
    0
      po/it.po
  81. 973
    0
      po/ja.po
  82. 1
    0
      stamp-h.in
  83. 3
    0
      subdirs

+ 1
- 0
AUTHORS View File

@@ -0,0 +1 @@
Stefan Hundhammer <sh@suse.de>

+ 280
- 0
COPYING View File

@@ -0,0 +1,280 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, 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

+ 482
- 0
COPYING.LIB View File

@@ -0,0 +1,482 @@
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
Appendix: 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 Library 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
Library General Public License for more details.

You should have received a copy of the GNU Library 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!

+ 18
- 0
CREDITS View File

@@ -0,0 +1,18 @@
We would like to thank the following people:

- Alexander Rawass <alexannika@users.sourceforge.net> for implementing the
first version of treemaps for KDirStat (this version has been completely
replaced beginning May 2002).

- Ben Shneiderman for his ingenious idea of treemaps as an alternative and
truly intuitive way of visualizing trees.

- All the people at the TU Eindhoven who worked on SequoiaView that gave us the
inspiration for including treemaps in KDirStat and numerous papers describing
the algorithms behind it.

- Harald Fernengel (harry1701@users.sourceforge.net) for continued support for
integrating KDirStat with new Qt versions.

- Toyohiro Asukai <toyohiro@ksmplus.com> for Asian support patches.


+ 684
- 0
ChangeLog View File

@@ -0,0 +1,684 @@
2005-01-07 Stefan Hundhammer <sh@suse.de>

* Improved handling of sparse files:
Now adding up only allocated size

* Improved handling of regular files with multiple links:
Now adding up size / no_links per occurence.
This is much closer to what "du" reports.

* Extended "own size" column context menu to show sparse files
and regular files with multiple links

* Reordered "own size" column context menu for consistency: xxx MB (yyy Bytes)

* Removed currently read path from status line while reading:
Much less flicker, no more constant window resizing, improved performance

* Added explanations for sparse files and multiple links to online help
* Bumped version to 2.4.4

2004-12-06 Stefan Hundhammer <sh@suse.de>

* Added "Open with" cleanup upon request by Jarl Friis <jarl@softace.dk>

* Bumped version to 2.4.3

2004-11-23 Stefan Hundhammer <sh@suse.de>

* Migration to KIO slave trash:/ for "move to trash" cleanup
(querying KDE version >= 3.4 at runtime)

* Added configuration update for safer transition from old-style
fixed "*/Trash" paths to "%t" placeholder

* Fixed lots of KDE libs "deprecated" warnings

* Reimported admin/ subdir from a recent KDE version (3.3.0)

* Bumped version to 2.4.2


2004-03-30 Stefan Hundhammer <sh@suse.de>

* Fixed KPacMan rendering in toolbar (thanks to Coolo)


2004-03-01 Stefan Hundhammer <sh@suse.de>

* Updated German translation


2003-11-13 Stefan Hundhammer <sh@suse.de>

* Added Italian translation by Giuliano Colla <colla@copeca.it>


2003-10-29 Stefan Hundhammer <sh@suse.de>

* Applied i18n patch by Toyohiro Asukai <toyohiro@ksmplus.com>

* Updated Japanese translation by Toyohiro Asukai <toyohiro@ksmplus.com>


2003-10-20 Stefan Hundhammer <sh@suse.de>

* Fixed some SuSE-internal Autobuild complaints

* Fixed treemap context menu popup location

* Bumped version to 2.4.1


2003-09-15 Stefan Hundhammer <sh@suse.de>

* Added Hungarian translation contributed by
Marcel Hilzinger <hili@suselinux.hu>

2003-08-26 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.4.0

* Fixed crash on program end while reading directories

* Fixed crash on open dir while still reading another directory

* Added "stop reading" action

* Added German translation contributed by
Christoph Eckert <fmchristoph.eckert@t-online.de>


2003-05-25 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.3.7

* Performance boost: Directory reading is now 16-20 times faster
because much fewer KDirTreeViewItems are cloned during reading

* Using QListViewItem::compare() instead of QListViewItem::key()
for better performance: less string operations / numeric formatting


2003-04-28 Stefan Hundhammer <sh@suse.de>

* Added French translation by Michel Grentzinger <mic.grentz@online.fr>

* Don't add up special files (char/block devices, sockets, FIFOs)


2003-02-03 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.3.6

* Fixed crash on startup when no config file present


2003-02-02 Stefan Hundhammer <sh@suse.de>

* Fixed crash in treemap when deleting subtree with cleanup

* Improved treemap action enabled/disabled state update


2003-01-30 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.3.5

* Colorize treemap tiles (by fixed rules, not customizable yet)

* Added new '%t' cleanup placeholder for the KDE trash directory

* Read jobs are now displayed in the percentage bar column


2003-01-28 Stefan Hundhammer <sh@suse.de>

* User cleanups now have an applicaton-wide keyboard shortcut
(Ctrl-0, Ctrl-1, Ctrl-2, ...)

* Prevent some treemap segfaults when re-reading directories


2003-01-14 Stefan Hundhammer <sh@suse.de>

* Synchronize treemap selection with dir tree after treemap rebuild

2003-01-08 Stefan Hundhammer <sh@suse.de>

* Changed activity point handling: The user was prompted far to
early to send feedback mail.

* Changed treemap double click handling:
Now double clicking the middle button zooms out,
double clicking the right button does nothing
(it pops up the context menu before receiving the second click
anyway)

* Changed help file accordingly


2003-01-07 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.3.4

* Updated admin subdir to latest KDE autoconf / automake stuff

* Gcc 3.x fixes


2003-01-06 Stefan Hundhammer <sh@suse.de>

* Tweaked treemap cushion ridges:
Squarified layout row now gets its own ridge,
no more double /triple ridges for directories

* Changed treemap cushion light source direction from bottom right
to top left

* Moved min/max/default for treemap settings to central header file

* Changed max/default treemap setting values

* Reduced settings dialogs outer borders:
No more accumulated borders


2003-01-04 Stefan Hundhammer <sh@suse.de>

* Added "general" settings page; now user configurable:
- cross file system boundaries
- use local dir read methods
- PacMan animation in toolbar
- PacMan animation ("PacMan armada") in dir tree

* Added "treemap" settings page: now user configurable:
- plain vs. cushion treemap
- squarified vs. simple treemap
- ambient light
- height scale factor
- force grid
- draw lines upon low contrast
- plain (non-cushioned) treemap colors
- highlight rectangle color
- minimum tile size
- auto-resize treemap

* Added "open URL" in "file" menu for easier access to remote URLs

* Bumped version to 2.3.3

2003-01-01 Stefan Hundhammer <sh@suse.de>

* Added treemap actions
* Added treemap menu
* Added treemap context menu
* Improved treemap integration into main application
* Added online help for treemaps


2002-12-31 Stefan Hundhammer <sh@suse.de>

* Lots of small fiddling with treemaps


2002-12-28 Stefan Hundhammer <sh@suse.de>

* Implemented cushion treemaps

* Bumped version to 2.3.2-devel

* Changed treemap selection mechanism:
Now using a transparent separate rectangle so even the outline
of entire directories can clearly be seen.

2002-12-27 Stefan Hundhammer <sh@suse.de>

* Added treemap mouse operations:
- select item in tree view (single click left)
- zoom in (double-click left)
- zoom out (double-click right)
- rebuild treemap in visible area (double-click middle)

* Added visible selection in treemap

* Select treemap tile when tree item is selected


2002-12-26 Stefan Hundhammer <sh@suse.de>

* Implemented squarified treemaps.
Now there are no longer lots of elongated, thin rectangles that
are hard to compare against each other and hard to point at.


2002-12-23 Stefan Hundhammer <sh@suse.de>

* Changed treemap handling completely: Now using QCanvas.

* Bumped version to 2.3.1-devel

2002-05-12 Stefan Hundhammer <sh@suse.de>

* Initial version of new treemaps

* Communication between treemap view and tree view

* Bumped version to 2.3.0-devel

2002-05-10 Stefan Hundhammer <sh@suse.de>

* Removed support for old treemaps

* Updated build-howto.html

2002-05-09 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.2.0
The KDE3 port proved stable enough to warrant a new stable
version.

2002-04-23 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.1.1-beta

* Added Japanese translation by
Toyohiro Asukai <toyohiro@ksmplus.com>

* Applied another Asian lang support patch by
Toyohiro Asukai <toyohiro@ksmplus.com>:
QString::sprintf() -> QString::arg()

2002-04-22 Stefan Hundhammer <sh@suse.de>

* Applied Asian language support patch by
Toyohiro Asukai <toyohiro@ksmplus.com>:
Somme missing QString::fromLocal8Bit() issues

2002-04-18 Stefan Hundhammer <sh@suse.de>

* KDE-3 migration:
- Replaced admin/ subdirectory completely
* Bumped version to 2.1.0-beta

2002-03-01 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.0.1
* Added large file (>2GB) support

2002-02-24 Stefan Hundhammer <sh@suse.de>

* Bumped version to 2.0.0 - the real release version
* Completed help texts
* Added "Help" button to feedback dialog
* Added "Help" button to settings dialog
* Drastically reduced logging to stdout

2002-02-11 Stefan Hundhammer <sh@suse.de>

* Prevent crash: Disable cleanups that modify the subtree while it
is still being read

2002-02-10 Stefan Hundhammer <sh@suse.de>

* Fixed double slashes in URLs when opening with file selection box
* Bumped version to 1.8.7-rc2

2002-02-09 Stefan Hundhammer <sh@suse.de>

* Fixed huge numbers overflow in details context popup
* Fixed huge numbers sorting
* Added new action "continue reading at mount point".
This is essentially the same as "refreshing selected branch",
but it's more intuitive to use.

2002-02-02 Stefan Hundhammer <sh@suse.de>

* Initial help documentation
* Bumped version to 1.8.6-rc1
This is the first release candidate.
The final version will be released as 2.0

2002-01-27 Stefan Hundhammer <sh@suse.de>

* Fixed update bug upon "refresh branch" and executing cleanups
* Embed cleanup %p / %n parameters in double quotes
* Added keyboard accelerators for standard cleanups
* (Partial) fix for PacMan animation display error on some KDE themes
* Bumped version to 1.8.5-beta

2002-01-19 Stefan Hundhammer <sh@suse.de>

* Added feedback mail facility
* Bumped version to 1.8.4-beta

2002-01-10 Stefan Hundhammer <sh@suse.de>

* Fixed repaint error in percentage bar column when scrolling
* Fixed repaint error when resizing percentage bar column

2002-01-04 Stefan Hundhammer <sh@suse.de>

* Bumped version to 1.8.3-beta
The new KDirStat is now as complete as the old one ever was!

* Added simple 'mail to owner' report
* Implemented cleanup configuration
* Added 'ask for confirmation' flag to cleanups
* Added 'works for local files only' flag to cleanups
* Fixed URL handling: Always strip off trailing slash
* Fixed app icon
* Fixed .desktop file - KDirStat is now in 'Utilities'

2002-01-03 Stefan Hundhammer <sh@suse.de>

* Implemented save/read configuration
* Updated TODO list - gosh, was this thing outdated!
* kdDebug() operator << for KCleanup
* kdDebug() operator << for KDirTreeViewItem


2002-01-02 Stefan Hundhammer <sh@suse.de>

* Implemented 'settings' dialog
* Implemented 'tree colors' settings


2002-01-01 Stefan Hundhammer <sh@suse.de>

* Implemented / completed KCleanupCollection
* Fixed some core dumps (oops)


2001-12-31 Stefan Hundhammer <sh@suse.de>

* kdDebug() operator<< for KFileInfo


2001-12-30 Stefan Hundhammer <sh@suse.de>

* Bumped version to 1.8.2-beta
* Cleanups are back!


2001-12-26 Stefan Hundhammer <sh@suse.de>

* Mount point remains marked as mount point even after
"refresh selected branch"

* KFileInfo / KDirInfo now have direct access to their
KDirTree (i.e. they now have their own pointer)
=> transparent access from outside easier


2001-12-08 Stefan Hundhammer <sh@suse.de>

* Tree colors are back again

* Transparently handle selections in the KDirTree;
all kinds of views should benefit from that.


2001-11-25 Stefan Hundhammer <sh@suse.de>

* Bumped version to 1.8.0-beta

* Added "Refresh selected" to main + context menu

* Implemented refreshing a single branch

* Many internal changes to enable deleting subtrees
(this is a requirement for cleanups)

* Internal cleanup: Got rid of that statRoot() mess,
clean ??::stat() implementation for all directory readers


2001-11-18 Stefan Hundhammer <sh@suse.de>

* Bumped version to 1.7.11-devel

* Improved mount point handling:
* Different icon,
* New read status KDirOnRequestOnly
* Prepared for explicit reading of mounted file systems

* Created infrastructure for context menu in tree view

* Simple context menu (cleanup actions will follow)


2001-11-17 Stefan Hundhammer <sh@suse.de>

* Moved treemap sources to separate subdirectory to prevent that
too-clever admin/am_edit script from breaking things: It always
uses all available sources rather than just those in
Makefile.am.

* Changed default from --enable-treemaps to --disable-treemaps
since treemaps don't compile and link for more than 6 weeks now.

* Updated build-howto.html


2001-10-22 Harald Fernengel (harry1701@users.sourceforge.net)

* make it work with Qt 3 / KDE 3

2001-09-26 Alexander Rawass <alexannika@users.sourceforge.net>

* committed Makefile.am from kdirstat-1-7-10-devel

2001-09-26 Alexander Rawass <alexannika@users.sourceforge.net>

* debugging output in kparts

2001-09-25 Alexander Rawass <alexannika@users.sourceforge.net>

* added files kdirstat_{part,factory}.{cpp,h,rc}
* trying to make a kpart of kdirstat
* libtool does not work for me yet

2001-08-20 Alexander Rawass <alexannika@users.sourceforge.net>

* modified configure.in.in to test for libqtreemap
test may not work on some/most systems

2001-08-18 Alexander Rawass <alexannika@users.sourceforge.net>

* V1.7.8-devel
* added kdirstat.spec (to build rpms)
* released kdirstat-1.7.8-1.i386.rpm

2001-08-17 Alexander Rawass <alexannika@users.sourceforge.net>

* removed files q*{cpp,h} from cvs
* removed doc/treemaps from cvs
* modified configure.in and kdirstat/Makefile.am
* QTreeMap is now in it's own cvs qtreemap.sourceforge.net

2001-08-11 Alexander Rawass <alexannika@users.sourceforge.net>

* QTreeMap can write data files for 'HypView',
a hyperbolic tree browser

2001-08-09 Alexander Rawass <alexannika@users.sourceforge.net>

* changed all size-functions from int to asize/float
* qxmltreemap: if a node has got an empty attribute 'size',
the size is calculated recursively

* new files & classes
qlistviewtreemapwindow.cpp
qlistviewtreemapwindow.h
qlistviewtreemaparea.cpp
qlistviewtreemap.h
qxmltreemapviewer.cpp

* files q*treemap* are built as a library libqtreemap
* new qxmltreemapviewer binary:
stand-alone QT/Xml Treemap Viewer
* QTreeMap/QListViewTreeMapArea works fine with KProf

2001-08-09 Stefan Hundhammer <sh@suse.de>

* Added "credits" section in about box

2001-08-08 Stefan Hundhammer <sh@suse.de>

* Implemented iterator classes: KFileInfoIterator and
KFileInfoSortedIterator
* Added CREDITS file

2001-08-06 Stefan Hundhammer <sh@suse.de>

* Fixed segfaults due to bad dot entry cleanup (huh? ;-) ) that
had caused core dumps after finishing reading small trees

2001-08-05 Alexander Rawass <alexannika@users.sourceforge.net>

* compiler warnings removed
* using List of Objects (instead List of KDirInfo)
* Bug: regexps not working in xml-window
selection not working in xml-window
* removed dependencies to KDirStat from QTreeMap

2001-07-29 Alexander Rawass <alexannika@users.sourceforge.net>

* load XML working (with memory hole)

2001-07-28 Alexander Rawass <alexannika@users.sourceforge.net>

* new sort of treemap/drawing mode: piemap
added file qtreemaparea_piemap.cpp
will not get checked in until legal problems solved
* checkmarks work also for paintmode

* new options for piemap mode
* bitmap can be saved to a file
* tree can be saved as xml file

* new files & classes
qxmltreemapwindow.cpp
qxmltreemapwindow.h
qxmltreemaparea.cpp
qxmltreemap.h
(don't work yet)

* new defines for compilation:
HAVE_PIEMAP if you have the piemap source
EXPERIMENTAL if you want to see more options

2001-07-17 Alexander Rawass <alexannika@users.sourceforge.net>

* user can use keywords instead of numbers for options
* checkmarks start working
* yet only with drawmode

2001-07-16 Alexander Rawass <alexannika@users.sourceforge.net>

* user can now use regexps or wildcards in config
* regexps are now compiled only once at startup
* wildcards are working correctly
* regexps need 3 /// backslashes in kdirstatrc
* Feature: the color list is parsed in alphabetic sort

2001-07-14 Alexander Rawass <alexannika@users.sourceforge.net>

* KDirTreeMapWindow reads out configuration with KConfig
* Bug: regexps are not working correctly

2001-07-13 Alexander Rawass <alexannika@users.sourceforge.net>

* user can click on rectangles and select/deselect them
* those rectangles are stored in a list and appear
at the bottom of the right-button popupmenu

2001-07-12 Alexander Rawass <alexannika@users.sourceforge.net>

* user can search for regexp, matches get highlighted
* current_dir_display working again

2001-07-11 Alexander Rawass <alexannika@users.sourceforge.net>

* new shading: image (sensible only with squarify)
displays pictures, can be used as picture browser
* removed most warnings

2001-07-11 Alexander Rawass <alexannika@users.sourceforge.net>

* various bugs fixed in squarified treemaps:
correct end of recursion
using floats rather than ints to prevent miscalc.
should work now????
* new hierarchical shadings


2001-07-10 Alexander Rawass <alexannika@users.sourceforge.net>

* implemented squarified treemaps (experimental, buggy)
* new file added: qtreemaparea_squarify.cpp
* Bug: when zooming in too much, the paintarea takes up too much
memory -> X swaps till death

2001-07-05 Alexander Rawass <alexannika@users.sourceforge.net>

* more options and exp. shadings
* experimental dynamic shading (not working)
* user can watch treemap build up
* paintEntry moved to qtreemaparea_paint.cpp
* drawTreeMap,drawDuTree,CTM moved to qtreemaparea_recursion.cpp
* renamed some of the shadings and
* wrote some Documentation how to use Shadings and Options


2001-07-03 Alexander Rawass <alexannika@users.sourceforge.net>

* QTreeMapWindow is now an abstract class
* KDirTreeMapWindow implements makeTreeMapWidget()
* experimental hierach. cushion
* new menu options (experimental & debugging)
* new way to make a border (border_step)
* CTM (Cushion Treemap) test routine added (not working yet)
* new Bug: I'm getting warnings about wrong RGB parameters,
even in flat mode


2001-07-01 Alexander Rawass <alexannika@users.sourceforge.net>

* QTreeMapArea is now a general abstract class to display hierarchies of any kind (not connected to KDirStat anymore)
* KDirTreeMapArea is the implementation for KDirStat
* new Bug: signals/slot not working correctly
* Bug fixed: crashed when telling kdirstat to display a directory which does not exist


2001-06-29 Stefan Hundhammer <sh@suse.de>

* Moved CVS to SourceForge

2001-06-24 Alexander Rawass <alexannika@users.sourceforge.net>

* V1.7.6-Devel
* Removed Zoom Bug
* Removed DM_FILES Bug
* Faster shading (dirs are always drawn flat)
* New directory coloring (shades of grey)
* Options for start direction, border width, draw text
* Removed most compiler warnings

2001-06-18 Stefan Hundhammer <sh@suse.de>

* V1.7.3-Devel
* Applied first treemap patch from
Alexander Rawass <alexannika@users.sourceforge.net>
* Added Alexander Rawass to authors list
* Improved treemap repaint behaviour (not perfect yet)

2001-06-17 Stefan Hundhammer <sh@suse.de>

* V1.7.2-Alpha
* Implemented support for all of KDE's IO protocols (ftp, smb, ...)
* Fixed PacMan warnings on premature exit


+ 167
- 0
INSTALL View File

@@ -0,0 +1,167 @@
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'.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

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.


+ 48
- 0
Makefile.am View File

@@ -0,0 +1,48 @@
# Toplevel Makefile.am for KDirStat
#
# Originally generated by KDevelop, modified by sh@suse.de
#

SUBDIRS = kdirstat po doc

EXTRA_DIST = \
AUTHORS \
COPYING \
COPYING.LIB \
CREDITS \
ChangeLog \
INSTALL \
README \
TODO \
admin \
build-howto.html \
kdirstat.kdevprj \
kdirstat.lsm


# This is not a GNU package. You can remove this line
# if have all needed files a GNU package needs.
AUTOMAKE_OPTIONS = foreign

CLEANFILES = $(wildcard autom4te.cache/*)

$(top_srcdir)/configure.in: configure.in.in $(top_srcdir)/subdirs
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common configure.in ;

$(top_srcdir)/subdirs:
cd $(top_srcdir) && $(MAKE) -f admin/Makefile.common subdirs

$(top_srcdir)/acinclude.m4: $(top_srcdir)/admin/acinclude.m4.in $(top_srcdir)/admin/libtool.m4.in
@cd $(top_srcdir) && cat admin/acinclude.m4.in admin/libtool.m4.in > acinclude.m4

MAINTAINERCLEANFILES = subdirs configure.in acinclude.m4 configure.files

package-messages:
$(MAKE) -f admin/Makefile.common package-messages
$(MAKE) -C po merge


dist-hook:
cd $(top_distdir) && perl admin/am_edit -padmin
cd $(top_distdir) && $(MAKE) -f admin/Makefile.common subdirs


+ 14
- 0
Makefile.cvs View File

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

.SILENT:

+ 14
- 0
Makefile.dist View File

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

.SILENT:

+ 20
- 0
README View File

@@ -0,0 +1,20 @@
This is a graphical "du" (disk usage) display.

What you see here is a 90% rewrite - GUI, engine, everything. The one thing it
can do a whole lot better than the old version is stay on one file system - the
single most most requested feature. Plus, it's way faster for large directory
trees - scanning an entire Linux file system no longer takes 30+
minutes. Rather, it's about 2-3 minutes: The old version seemed to have
problems with system buffer thrashing due to too many directories open for
reading at one time - the new version uses an internal queue and keeps only one
directory open.

For more details, see the KDirStat home page at

http://kdirstat.sourceforge.net/



Stefan Hundhammer <sh@suse.de>
2002-05-10


+ 52
- 0
TODO View File

@@ -0,0 +1,52 @@
TODO list for KDirStat
========================
Updated: 2005-01-07

- help text for "treemap" settings

- help text for "general" settings

- update screen shots in online help (no treemaps yet)

- make KDirStat a KPart



Maybe:
======

- German help file

- Animation other than pacman (optional?)

- configure mail report texts (the user gets an editor in the mailer anyway)

- 'kdf' like 'disk free' display for file system of current tree - pie, bar graph?
Steal that thing from the SuSE YaST2 package manager UI I wrote?
(which, in turn, I stole in large parts from KDirStat)

- Filter on tree view: by user, by mtime, by size

- Select items in the tree view as "special interest" for further processing in mail reports

- Manually mark dir subtrees as "static" - e.g., for system directories that
almost never change anyway; scan them just once and save their sizes to file;
only rescan those subtrees on explicit user request

- Automagically mark such subtrees by mtime and/or a hardwired list




Postponed until further notice:
===============================

- write scanned trees to cache file for later reuse;
use this cache file first and then begin scanning the dir tree.

Since the Linux 2.4 kernel is great at caching directory entries,
this isn't really necessary for Linux - and I am a Linux guy...
;-)




+ 11360
- 0
acinclude.m4
File diff suppressed because it is too large
View File


+ 1045
- 0
aclocal.m4
File diff suppressed because it is too large
View File


+ 191
- 0
build-howto.html View File

@@ -0,0 +1,191 @@
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>

<head>
<title>Building KDirStat for KDE 3.x</title>
</head>

<body bgcolor=#F0F0F0>


<table width=100%>
<tr>
<td width=50% align=left>
Last modified: 23 Nov 2004
</td>
<td width=50% align=right>
Contact: <a href="mailto:sh@suse.de?subject=KDirStat build-howto">Stefan Hundhammer</a>
</td>
</tr>
</table>


<h1 align=center>Building KDirStat for KDE 3.x</h1>


<table width=100% bgcolor=#B0B0F0>
<tr><td><h2>Note:</h2></td></tr>

<tr><td>
If you are using the
latest
<a href="http://www.suse.com/">SuSE Linux</a>
, you may not have to build it at all.
There usually is an RPM package you can use at the
<a href="http://kdirstat.sourceforge.net/download/">download area</a>.
See also the <a href="http://kdirstat.sourceforge.net/">KDirStat home page</a>.
</td></tr>
</table>

<ul>
<li>
Get the latest sources - either the
<a href="http://kdirstat.sourceforge.net/download/">tarball from the download area</a>
or via
<a href="http://sourceforge.net/cvs/?group_id=30290">anonymous CVS from SourceForge.</a>
<p><br></p>
</li>

<li>
Make sure you have a development system up and running.

<p>
You'll need at least:

<ul>
<li>A C++ compiler
<li>Header files for the system libs
<li>X11 development environment (libs and header files)
<li>Qt 3.0 (or later) development environment
<li>KDE 3.x development environment
</ul>

<p>
- maybe more. If you are unsure and you are running SuSE Linux, it might be
a good idea to install the <em>development system</em> selection.
</p>

<p>
Please understand that I cannot and will not fix everybody's broken development
systems any more - this had taken me quite some time with KDirStat 0.8x. Please
make sure you can compile simple KDE programs like <em>kless</em> or
<em>kexample</em> before contacting me about build problems.
</p>
</li>
<br>

<li>Unpack the sources:
<br>
<pre>

tar xjvf kdirstat-2.4.2.tar.bz2

</pre>
<p>
(or whatever version you downloaded)
</p>
<p><br></p>
</li>

<li>
Go to this directory:
<br>
<pre>

cd kdirstat-2.4.2

</pre>
</li>

<li>
Make sure I didn't accidentially include a <em>config.cache</em> file in the
tarball - remove it to make sure. This is a neverending cause of trouble.
<br>
<pre>

rm -f config.cache

</pre>
</li>


<li>
Let the <em>configure</em> script figure out where everything required is on
your system.
<p>
Watch out for error messages and <b>fix them</b> before reporting
errors!
</p>

<p>On SuSE Linux systems, KDE 3.x is installed to <em>/opt/kde3</em> which is a
good idea if you want to keep some KDE 1.x/2.x programs around. So use that
<em>/opt/kde3</em> prefix for KDirStat, too - otherwise it will be installed to
<em>/opt/kde</em> and clutter up a working KDE 1.x/2.x environment.
<br>
<pre>

./configure --prefix=/opt/kde3

</pre>
<p>
If you don't care about that or if you set up KDE 3.x in <em>/opt/kde</em>
anyway, simply type
</p>
<pre>

./configure

</pre>
</li>

<li>
Compile everything:
<br>
<pre>

make

</pre>
<p>
Again, watch out for error messages.
</p>
<p>
<br>
</p>
</li>

<li>
If everything worked out allright, become <em>root</em> and install the program
and everything it needs:
<br>
<pre>

su
make install

</pre>
<p>
<b>Don't do this if the previous step reported errors!</b>
</p>
</li>

</ul>

<p>
That's it.
</p>



</body>
</html>


<!-- --- Emacs Customization --- -->
<!-- -->
<!-- Local Variables: -->
<!-- time-stamp-format: "%02d %3b %04y" -->
<!-- time-stamp-start: "Last modified:[ \t]+" -->
<!-- time-stamp-end: "$" -->
<!-- End: -->


+ 243
- 0
config.h.in View File

@@ -0,0 +1,243 @@
/* config.h.in. Generated from configure.in by autoheader. */

/* Define if you have the CoreAudio API */
#undef HAVE_COREAUDIO

/* Define to 1 if you have the <crt_externs.h> header file. */
#undef HAVE_CRT_EXTERNS_H

/* Defines if your system has the crypt function */
#undef HAVE_CRYPT

/* Define to 1 if you have the <dlfcn.h> header file. */
#undef HAVE_DLFCN_H

/* Define to 1 if you have the <inttypes.h> header file. */
#undef HAVE_INTTYPES_H

/* Define if you have libjpeg */
#undef HAVE_LIBJPEG

/* Define if you have libpng */
#undef HAVE_LIBPNG

/* Define if you have a working libpthread (will enable threaded code) */
#undef HAVE_LIBPTHREAD

/* Define if you have libz */
#undef HAVE_LIBZ

/* Define if you have long long as datatype */
#undef HAVE_LONG_LONG

/* Define to 1 if you have the <memory.h> header file. */
#undef HAVE_MEMORY_H

/* Define if your system needs _NSGetEnviron to set up the environment */
#undef HAVE_NSGETENVIRON

/* Define if you have res_init */
#undef HAVE_RES_INIT

/* Define if you have the res_init prototype */
#undef HAVE_RES_INIT_PROTO

/* Define if you have a STL implementation by SGI */
#undef HAVE_SGI_STL

/* Define to 1 if you have the `snprintf' function. */
#undef HAVE_SNPRINTF

/* Define to 1 if you have the <stdint.h> header file. */
#undef HAVE_STDINT_H

/* Define to 1 if you have the <stdlib.h> header file. */
#undef HAVE_STDLIB_H

/* Define to 1 if you have the <strings.h> header file. */
#undef HAVE_STRINGS_H

/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H

/* Define if you have strlcat */
#undef HAVE_STRLCAT

/* Define if you have the strlcat prototype */
#undef HAVE_STRLCAT_PROTO

/* Define if you have strlcpy */
#undef HAVE_STRLCPY

/* Define if you have the strlcpy prototype */
#undef HAVE_STRLCPY_PROTO

/* Define to 1 if you have the <sys/bitypes.h> header file. */