diff options
| author | bseifert <none@none> | 2003-10-30 09:08:04 +0300 |
|---|---|---|
| committer | bseifert <none@none> | 2003-10-30 09:08:04 +0300 |
| commit | f049e2df4b09dc19a7d76e2d33b8cfcb5370e9dc (patch) | |
| tree | f2f04cd33835591b8e32953d093a1527a75f3464 /wdshelp | |
| parent | 98a363ad8bd075b1abd702b7d380692ec0c470d6 (diff) | |
Initial revision
Diffstat (limited to 'wdshelp')
| -rw-r--r-- | wdshelp/Table_of_Contents.hhc | 76 | ||||
| -rw-r--r-- | wdshelp/actions.htm | 50 | ||||
| -rw-r--r-- | wdshelp/configuration.htm | 30 | ||||
| -rw-r--r-- | wdshelp/coupling.htm | 35 | ||||
| -rw-r--r-- | wdshelp/deinstallation.htm | 21 | ||||
| -rw-r--r-- | wdshelp/directorytree.htm | 61 | ||||
| -rw-r--r-- | wdshelp/extensionlist.htm | 32 | ||||
| -rw-r--r-- | wdshelp/faq.htm | 45 | ||||
| -rw-r--r-- | wdshelp/format.css | 9 | ||||
| -rw-r--r-- | wdshelp/gnufdl.htm | 389 | ||||
| -rw-r--r-- | wdshelp/legend.htm | 56 | ||||
| -rw-r--r-- | wdshelp/limits.htm | 29 | ||||
| -rw-r--r-- | wdshelp/original_n_baum55.gif | bin | 0 -> 31152 bytes | |||
| -rw-r--r-- | wdshelp/selectdrivesdialog.htm | 33 | ||||
| -rw-r--r-- | wdshelp/sorting.htm | 30 | ||||
| -rw-r--r-- | wdshelp/tree.jpg | bin | 0 -> 3870 bytes | |||
| -rw-r--r-- | wdshelp/treemap.htm | 43 | ||||
| -rw-r--r-- | wdshelp/userdefinedcleanups.htm | 67 | ||||
| -rw-r--r-- | wdshelp/wdshelp.vcproj | 122 | ||||
| -rw-r--r-- | wdshelp/whatisatree.htm | 62 | ||||
| -rw-r--r-- | wdshelp/windirstat.hhp | 43 | ||||
| -rw-r--r-- | wdshelp/windirstat.htm | 63 |
22 files changed, 1296 insertions, 0 deletions
diff --git a/wdshelp/Table_of_Contents.hhc b/wdshelp/Table_of_Contents.hhc new file mode 100644 index 0000000..f4b50db --- /dev/null +++ b/wdshelp/Table_of_Contents.hhc @@ -0,0 +1,76 @@ +<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> +<HTML> +<HEAD> +<meta name="GENERATOR" content="Microsoft® HTML Help Workshop 4.1"> +<!-- Sitemap 1.0 --> +</HEAD><BODY> +<OBJECT type="text/site properties"> + <param name="ImageType" value="Folder"> +</OBJECT> +<UL> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="WinDirStat"> + <param name="Local" value="windirstat.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="What is a Directory Tree?"> + <param name="Local" value="whatisatree.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Directory List"> + <param name="Local" value="directorytree.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Extension List"> + <param name="Local" value="extensionlist.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Treemap"> + <param name="Local" value="treemap.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Coupling of the Views"> + <param name="Local" value="coupling.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Select Drives Dialog"> + <param name="Local" value="selectdrivesdialog.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Cleanups"> + <param name="Local" value="actions.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="User Defined Cleanups"> + <param name="Local" value="userdefinedcleanups.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Configuration"> + <param name="Local" value="configuration.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Sorting"> + <param name="Local" value="sorting.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Legend"> + <param name="Local" value="legend.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Frequently Asked Questions"> + <param name="Local" value="faq.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Limits"> + <param name="Local" value="limits.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="Deinstallation"> + <param name="Local" value="deinstallation.htm"> + </OBJECT> + <LI> <OBJECT type="text/sitemap"> + <param name="Name" value="GNU Free Documentation License"> + <param name="Local" value="gnufdl.htm"> + </OBJECT> +</UL> +</BODY></HTML> diff --git a/wdshelp/actions.htm b/wdshelp/actions.htm new file mode 100644 index 0000000..f95283d --- /dev/null +++ b/wdshelp/actions.htm @@ -0,0 +1,50 @@ +<html> + <head> + <title>Clenaups</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Cleanups</h2> + <p>Serveral clean up actions can be applied to a selected item. The cleanups are + accessible through the main menu, the tool bar and through keyboard shortcuts. + </p> + <h3>Refresh Selected</h3> + <p>Possibly an item has been deleted or modified outside of WinDirStat. "Refresh" + makes WinDirStat re-read the item, so that the display accords with the actual + conditions on the hard disk again. + </p> + <h3>Copy Path</h3> + <p>Copies the path of the selected item into the clipboard.</p> + <h3>Open</h3> + <p>Opens the selected file. Note that in case of an executable file (.exe), this + means that the program is started. + </p> + <h3>Explorer here</h3> + <p>Launches the Windows Explorer so that it shows the selected item.</p> + <h3>Command Prompt here</h3> + <p>Launches the DOS prompt in the selected directory.</p> + <h3>Delete (to Recycle Bin)</h3> + <p>Moves the selected item into the recycle bin. Then the item and the recycle bin + directories are refreshed.</p> + <h3>Delete (no way to undelete)</h3> + <p>Deletes the selected item irreversibly. Then the item is refreshed. Please + delete only files and directories, when you know that neither you nor the + system needs it any more! + </p> + <h3>Properties</h3> + <p>Opens the 'Properties' dialog for the selected file.</p> + <h3>Send Mail to Owner</h3> + <p>Generates a textual report about the selected directory, which can be sent a via + e-mail to its owner. This is intended for network drives, which are used by + several people. The report accurately contains the lines displayed in the + directory list underneath the selected item, in the same "expansion state" and + in the same sort order. + </p> + <h3>User Defined Cleanups</h3> + <p>In addition to these built-in clean ups you can freely <a href="userdefinedcleanups.htm"> + define your own cleanups</a>. + </p> + </BODY> +</html> diff --git a/wdshelp/configuration.htm b/wdshelp/configuration.htm new file mode 100644 index 0000000..7dd71c6 --- /dev/null +++ b/wdshelp/configuration.htm @@ -0,0 +1,30 @@ +<html> + <head> + <title>Configuration</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Configuration</h2> + <h3>General</h3> + <p><u>Cross file system boundaries (only NT and higher)</u>. Under NTFS volumes can + be mounted in directories. By default WinDirStat stops reading at these mount + points, i.e. it shows only the usage of <i>one</i> file system. Here you can + change this behavior. (No mount points are recognized on UNC drives.) + </p> + <p><u>Language</u>. In addition to the built-in language English, this combo box + offers those languages, for which a correspondig wsdrxxxx.dll exists. The + setting takes effect next time when WinDirStat is started.</p> + <h3>Directory List</h3> + <p>Colors for the subtree percentage presentation. Grid lines. + </p> + <h3>Treemap</h3> + <p>Parameters for the cushion shading. Grid lines (try this!). Color of the + selection rectangle. + </p> + <h3>Cleanups</h3> + <p>Here you can configure the <a href="userdefinedcleanups.htm">User Defined Cleanups</a>. + </p> + </BODY> +</html> diff --git a/wdshelp/coupling.htm b/wdshelp/coupling.htm new file mode 100644 index 0000000..88941ae --- /dev/null +++ b/wdshelp/coupling.htm @@ -0,0 +1,35 @@ +<html> + <head> + <title>Coupling of the Views</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Coupling of the Views</h2> + <p>The really strong point of WinDirStat is, that the three views, Directory List, + Extension List and Treemap, are coupled with each other. + </p> + <h3>Directory List -> Treemap</h3> + <p>When you <i>select</i> an item (directory or file) in the directory list, the + treemap also shows this item by highlighting it with a colored frame. In + particular you can see the size of directories. + </p> + <h3>Treemap -> Directory List</h3> + <p>When you click into the treemap, the mouse always hits a file (a colored + rectangle). After that the directory list expands (if necessary) the + appropriate nodes and selects this file. So you can, e.g. by clicking on a big + rectangle, see path and attributes of the corresponding big file in the + directory list. + </p> + <p>So, because of this mutual coupling, the selections in the directory list and in + the treemap are always the same. + </p> + <h3>Directory List + Treemap -> Extension List</h3> + <p>When you select a <i>file</i> in the directory list (or in the treemap), the + extension list shows the file type (the extension). The extension is selected + and scrolled into view. So you can see the description and the + statistics for this file type. + </p> + </BODY> +</html> diff --git a/wdshelp/deinstallation.htm b/wdshelp/deinstallation.htm new file mode 100644 index 0000000..9c35d58 --- /dev/null +++ b/wdshelp/deinstallation.htm @@ -0,0 +1,21 @@ +<html> + <head> + <title>Deinstallation</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Deinstallation</h2> + <p> + <ul> + <li> + Remove the directory C:\program files\windirstat</li> + <li> + Remove the shortcuts for WinDirStat</li> + <li> + <i>For experts</i>: Remove HKCU\Software\seifert\windirstat.</li> + </ul> + </p> + </BODY> +</html> diff --git a/wdshelp/directorytree.htm b/wdshelp/directorytree.htm new file mode 100644 index 0000000..cda7dca --- /dev/null +++ b/wdshelp/directorytree.htm @@ -0,0 +1,61 @@ +<html> + <head> + <title>Directory List</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Directory List</h2> + <p>The directory list resembles the tree view of the Windows Explorer, with the + difference that it shows directories and files sorted by size descending. At + the top you see the directories and files, which use up most space. When you + expand a directory, its subdirectories are shown again sorted by size, and so + on. + </p> + <h3>Columns</h3> + <p> + <ul> + <li> + <u>Name</u>. This column shows the names of the files and directories and their + tree structure.</li> + <li> + <u>Size</u>. For files, this is the size of the file, in bytes. For + directories, this is the size of the subtree, that is the sum of the sizes of + all subdirectories and files.</li> + <li> + <u>Subtree Percentage</u>. This column shows, how the size of a subtree is + composed of the sizes of the sub-items. This information is comparable only + within <i>one</i> level and is always related to the expanded parent item.<br> + [During the scanning, this column shows either a pacman or the number of read + jobs to do for the subtree.] + </li> + <li> + <u>Percentage</u>. The same information as in "Subtree Percentage", in percent.<br> + [During the scanning, this column shows the time spent for the subtree so far.] + </li> + <li> + <u>Files</u>. Number of files in the subtree.</li> + <li> + <u>Subdirs</u>. Number of sub-directories in the subtree.</li> + <li> + <u>Items</u>. Number of items in the subtree. Sum of "Files" and "Subdirs".</li> + <li> + <u>Last Change</u>. Date of the last modification in the subtree.</li> + </ul> + </p> + <h3>Operation</h3> + <p>In the column "Name" you can expand and collapse the directories by a mouse + click on the little boxes with + and -, as in the Windows Explorer. A click on + a name <i>selects</i> an item. After that you can navigate in the tree with the + arrow keys. + </p> + <p>The treemap always highlights the selected item with a frame. + </p> + <p>If you select a file, the extension list automatically shows its type. + </p> + <p>The <a href="sorting.htm">sorting</a> can be set with a mouse click on a column + header. + </p> + </BODY> +</html> diff --git a/wdshelp/extensionlist.htm b/wdshelp/extensionlist.htm new file mode 100644 index 0000000..9e8b3e5 --- /dev/null +++ b/wdshelp/extensionlist.htm @@ -0,0 +1,32 @@ +<html> + <head> + <title>Extension List</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Extension List</h2> + <p>The extension list contains all types (filename extensions) occurring in the + directory tree. For every file type the column "Bytes" shows the sum of the file + sizes. By default, the extension list is sorted descending by this column. + So at the top are those files types, which all in all take up most space + on the hard disk. + </p> + <p>12 colors are assigned to the 12 file types, which take up most space. The rest + is grey. The treemap shows the files in these colors. + </p> + <h3>Columns</h3> + <p> + <ul> + <li><u>Extension</u>. Icon and filename extension.</li> + <li><u>Color</u>. The color, which is used by the treemap to display the files of this type.</li> + <li><u>Description.</u> Description of the file type. Corresponds to the description + shown by the Windows Explorer.</li> + <li><u>Bytes</u>. Total volume of the file type in the directory tree. + Sum of the sizes of all files of this type.</li> + <li><u>Files</u>. Number of files of this type in the directory tree.</li> + </ul> + </p> + </BODY> +</html> diff --git a/wdshelp/faq.htm b/wdshelp/faq.htm new file mode 100644 index 0000000..1debbf0 --- /dev/null +++ b/wdshelp/faq.htm @@ -0,0 +1,45 @@ +<html> + <head> + <title>Frequently Asked Questions</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta content="http://schemas.microsoft.com/intellisense/ie5" name="vs_targetSchema"> + <LINK href="format.css" type="text/css" rel="stylesheet"> + <style type="text/css"> + <!-- + h3 { margin-bottom:6pt; } + p { margin-top:0pt; } + --> + </style> + </head> + <BODY> + <h2>Frequently Asked Questions</h2> + <h3>Q: Does the treemap relate to the allocation of hard disk sectors?</h3> + <p>A: No. The treemap view has nothing to do with hard disk sectors. + Generally big files are scattered on the hard disk. The treemap on the other + hand shows each file as <i>one</i> rectangle. + </p> + <h3>Q: Does WinDirStat start threads for the read jobs?</h3> + <p>A: No. WinDirStat is - apart from the about box, which runs in an own thread + - deeply single-threaded. All work is done in OnIdle(). + </p> + <h3>Q: What does the item <Files> mean?</h3> + <p>A: See <A href="legend.htm">Legend</A>. + </p> + <h3>Q: What does the > symbol in front of the column captions mean?</h3> + <p>A: The > and < symbols in the column headers indicate the current + <A href="sorting.htm">sorting</A>. + </p> + <h3>Q: What is the file wdsr0407.dll for?</h3> + <p>A: This file contains the German translation of WinDirStat. 0407 is the + language identifier for "German - Germany". If this file is absent, then + WinDirStat is available in the (built-in) language English only. + </p> + <h3>Q: The size information in KB and MB seems to be a bit too small.</h3> + <p>A: WinDirStat sticks to the computing convention, that "kilo" doesn't stand + for 1000 but for 1024. So we have:<br> + 1 KB = 1024 Bytes<br> + 1 MB = 1024 KB = 1,048,576 Bytes<br> + 1 GB = 1024 MB = 1,048,576 KB = 1,073,741,824 Bytes. + </p> + </BODY> +</html> diff --git a/wdshelp/format.css b/wdshelp/format.css new file mode 100644 index 0000000..cd51716 --- /dev/null +++ b/wdshelp/format.css @@ -0,0 +1,9 @@ +BODY +{ + font-family:Arial,sans-serif; +} + +LI +{ + margin-bottom:0.5cm; +} diff --git a/wdshelp/gnufdl.htm b/wdshelp/gnufdl.htm new file mode 100644 index 0000000..894f7bf --- /dev/null +++ b/wdshelp/gnufdl.htm @@ -0,0 +1,389 @@ +<html> + <head> + <title>GNU Free Documentation License</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <H2><A href="http://www.gnu.org/licenses/fdl.html">GNU Free + Documentation License</A></H2> + <P> + Version 1.2, November 2002 + <P><PRE>Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. +59 Temple Place, Suite 330, Boston, MA 02111-1307 USA +Everyone is permitted to copy and distribute verbatim copies +of this license document, but changing it is not allowed. + </PRE> + <P><STRONG>0. PREAMBLE</STRONG> + <P> + 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. + <P> + 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. + <P> + 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. + <P><STRONG>1. APPLICABILITY AND DEFINITIONS</STRONG> + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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". + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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. + <P><STRONG>2. VERBATIM COPYING</STRONG> + <P> + 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. + <P> + You may also lend copies, under the same conditions stated above, and you may + publicly display copies. + <P><STRONG>3. COPYING IN QUANTITY</STRONG> + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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. + <P><STRONG>4. MODIFICATIONS</STRONG> + <P> + 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: + <P> + <UL> + <LI> + <STRONG>A.</STRONG> + 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. + <LI> + <STRONG>B.</STRONG> + 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. + <LI> + <STRONG>C.</STRONG> + State on the Title page the name of the publisher of the Modified Version, as + the publisher. + <LI> + <STRONG>D.</STRONG> + Preserve all the copyright notices of the Document. + <LI> + <STRONG>E.</STRONG> + Add an appropriate copyright notice for your modifications adjacent to the + other copyright notices. + <LI> + <STRONG>F.</STRONG> + 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. + <LI> + <STRONG>G.</STRONG> + Preserve in that license notice the full lists of Invariant Sections and + required Cover Texts given in the Document's license notice. + <LI> + <STRONG>H.</STRONG> + Include an unaltered copy of this License. + <LI> + <STRONG>I.</STRONG> + 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. + <LI> + <STRONG>J.</STRONG> + 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. + <LI> + <STRONG>K.</STRONG> + 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. + <LI> + <STRONG>L.</STRONG> + 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. + <LI> + <STRONG>M.</STRONG> + Delete any section Entitled "Endorsements". Such a section may not be included + in the Modified Version. + <LI> + <STRONG>N.</STRONG> + Do not retitle any existing section to be Entitled "Endorsements" or to + conflict in title with any Invariant Section. + <LI> + <STRONG>O.</STRONG> Preserve any Warranty Disclaimers. + </LI> + </UL> + <P> + 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. + <P> + 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. + <P> + 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. + <P> + 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. + <P><STRONG>5. COMBINING DOCUMENTS</STRONG> + <P> + 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. + <P> + 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. + <P> + 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." + <P><STRONG>6. COLLECTIONS OF DOCUMENTS</STRONG> + <P> + 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. + <P> + 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. + <P><STRONG>7. AGGREGATION WITH INDEPENDENT WORKS</STRONG> + <P> + 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. + <P> + 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. + <P><STRONG>8. TRANSLATION</STRONG> + <P> + 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. + <P> + 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. + <P><STRONG>9. TERMINATION</STRONG> + <P> + 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. + <P><STRONG>10. FUTURE REVISIONS OF THIS LICENSE</STRONG> + <P> + 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/. + <P> + 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. + <P> + <H2>How to use this License for your documents</H2> + <P> + 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: + <P><PRE>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". + </PRE> + <P> + If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace + the "with...Texts." line with this: + <P><PRE>with the Invariant Sections being LIST THEIR TITLES, with the +Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. + </PRE> + <P> + If you have Invariant Sections without Cover Texts, or some other combination + of the three, merge those two alternatives to suit the situation. + <P> + 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. + <P> + </BODY> +</html> diff --git a/wdshelp/legend.htm b/wdshelp/legend.htm new file mode 100644 index 0000000..a5cf029 --- /dev/null +++ b/wdshelp/legend.htm @@ -0,0 +1,56 @@ +<html> + <head> + <title>Legend</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + <style type="text/css"> + <!-- + h3 { margin-bottom:6pt; } + p { margin-top:0pt; } + --> + </style> + </head> + <BODY> + <h2>Legend</h2> + <h3><Files></h3> + <p>Generally, each directory in the directory list has a pseudo subdirectory + <Files>. There, all ordinary files of the directory are put together. + That is, all files, which are immediate children of the directory, not those + of subdirectories. This has the advantage, that the directory list is cleaner + and that the statistics is sounder. Because with this item you can + see how much space is used all in all by the files of the directory (not of subdirectories). + </p> + <p>The <Files> item is ommitted, if there is only one file in the + directory, or if it has no subdirectories. + </p> + <h3><Free Space></h3> + <p>If you have activated "Show Free Space" in the Options menu, each drive + has an <Free Space> item. The size of this item tallies with the amount + of free space available on the drive. In the treemap this item has a dark grey color. + Through the <Free Space> item you get an impression of the ratio between + the totaly used disk space and the free disk space. This information corresponds + with the value shown in the Windows Explorer properties dialog for the drive. + </p> + <h3><Unknown></h3> + <p>If you have activated "Show Unknown" in the Options menu, each drive + has an <Unknown> item. The matter is as follows. + On the one hand, WinDirStat knows the total capacity of the drive and + the free disk space. (These values tally with the number shown by the + Windows Explorer properties dialog for the drive.) + On the other hand WinDirStat has determined the sizes of all files + and added them up. + Well, <Unknown> is the difference: Total capacity minus free space + minus determined sum. This rest can be greater than zero by serveral reasons. + For instance there can be directories (e.g. "System Volume Information") with read-access + denied. Their size cannot be included in the sum calculated by WinDirStat. + In the treemap, the <Unknown> item is colored vivid yellow. + </p> + <h3>< (in column headings)</h3> + <p>indicates that the list is <a href="sorting.htm">sorted</a> by this column in ascending order. + </p> + <h3>> (in column headings)</h3> + <p>indicates that the list is <a href="sorting.htm">sorted</a> by this column in descending order. + </p> + </BODY> +</html> diff --git a/wdshelp/limits.htm b/wdshelp/limits.htm new file mode 100644 index 0000000..0768c93 --- /dev/null +++ b/wdshelp/limits.htm @@ -0,0 +1,29 @@ +<html> + <head> + <title>Limits</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Limits</h2> + <table border="1" bordercolor="black" cellspacing="0" cellpadding="20"> + <tr> + <td>Number of direct subitems of a directory</td> + <td>2^31 (= 2.147.483.648)</td> + </tr> + <tr> + <td>Time spent on scanning</td> + <td>2^32 ms (= 49 days)</td> + </tr> + <tr> + <td>File size, tree size</td> + <td>2^63 (= 8.388.608 TB)</td> + </tr> + <tr> + <td>Number of concurrent read jobs</td> + <td>2^63</td> + </tr> + </table> + </BODY> +</html> diff --git a/wdshelp/original_n_baum55.gif b/wdshelp/original_n_baum55.gif Binary files differnew file mode 100644 index 0000000..20d2483 --- /dev/null +++ b/wdshelp/original_n_baum55.gif diff --git a/wdshelp/selectdrivesdialog.htm b/wdshelp/selectdrivesdialog.htm new file mode 100644 index 0000000..96b95f2 --- /dev/null +++ b/wdshelp/selectdrivesdialog.htm @@ -0,0 +1,33 @@ +<html> + <head> + <title>Select Drives Dialog</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Select Drives Dialog</h2> + <p>Here you can decide which drives to include in the statistics. + </p> + <p>You can select one or more drives from the list or choose a directory. + </p> + <p>The list shows all present drives (hard disks, inserted floppy disks or CDs, + and network drives).</p> + <h3>Columns</h3> + <p> + <ul> + <li><u>Name</u>. Name and drive letter of the drive.</li> + <li><u>Total</u>. Capacity of the drive.</li> + <li><u>Free</u>. Free space on the drive.</li> + <li><u>Total/Used</u> Percentage of used space, related to the capacity.</li> + <li><u>Total/Used</u> The same information in percent.</li> + </ul> + </p> + <h3>Operation</h3> + <p>The dialog box has three "radio buttons": "All local drives", "Individual drives" + and "A folder". The default is "All local drives", that is all drives, which are not + network drives. Simply click on OK to begin the scan.</p> + <p>The selection is persistent, i.e. when you open the dialog the next time, + the default setting will be that which you made the last time.</p> + </BODY> +</html> diff --git a/wdshelp/sorting.htm b/wdshelp/sorting.htm new file mode 100644 index 0000000..644e836 --- /dev/null +++ b/wdshelp/sorting.htm @@ -0,0 +1,30 @@ +<html> + <head> + <title>Sorting</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Sorting</h2> + <p>All lists in WinDirStat can be sorted at will. The current sorting is + indicated by the symbols < and > in the column headings. + < means ascending sort, > means descending sort. + </p> + <p>You can set the desired sorting by a mouse click on a column heading. + </p> + <p>Actually two columns are drawn on the sorting. First that one, on which + you clicked last, and second - if the elements are equal regarding this column - + that, which sorted before. + </p> + <p>Note that the sorting of the directory list of course respects the + tree structure: sorting occurs only within one level. + </p> + <p></p> + <h3>Annotation</h3> + <p>The column widths and column order can be adjusted via drag 'n drop. + The widths and column order are persistent; that is, at program + start they are automatically restored as you have set them last. + </p> + </BODY> +</html> diff --git a/wdshelp/tree.jpg b/wdshelp/tree.jpg Binary files differnew file mode 100644 index 0000000..e978839 --- /dev/null +++ b/wdshelp/tree.jpg diff --git a/wdshelp/treemap.htm b/wdshelp/treemap.htm new file mode 100644 index 0000000..26942e2 --- /dev/null +++ b/wdshelp/treemap.htm @@ -0,0 +1,43 @@ +<html> + <head> + <title>Treemap</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>Treemap</h2> + <p>The treemap shows the whole contents of the <a href="whatisatree.htm">directory tree</a> + straight away. + </p> + <p>It represents each file as a colored rectangle, the area of which is + proportional to the file's size. + </p> + The rectangles are arranged in such a way, that directories again make up + rectangles, which contain all their files and subdirectories. So their area is + proportional to the size of the subtrees. </p> + <p>The color of a rectangle indicates the type of the file, as shown in the + extension list. + </p> + <p>The cushion shading additionally brings out the directory structure.</p> + <h3>Operation</h3> + <p>You effortlessly see the big rectangles, that is the big files, even if they are + hidden deeply in subdirectories in the directory tree. Click on them: the + directory list opens the path to the file, and you can read its location and + attributes, and - if you like - apply a cleanup action on it, e.g. delete the + file. + </p> + <p>Navigate in the directory list: the respective selection is highlighted with a + colored frame. In this way gain an impression of the proportions: How big, for + example, is C:\windows compared with C:\program files? + </p> + <p>The context menu options "Select Parent" and "Re-select Child" are also useful + for the navigation. + </p> + <p>Zoom. The option "Zoom in" enlarges the treemap, so that a subtree is + displayed full size. As it were you make a step towards the selected item. + The directory list show the root of this subtree with a blue frame. + By "Zoom out" you step back, and the parent element is shown again. + </p> + </BODY> +</html> diff --git a/wdshelp/userdefinedcleanups.htm b/wdshelp/userdefinedcleanups.htm new file mode 100644 index 0000000..c1662bd --- /dev/null +++ b/wdshelp/userdefinedcleanups.htm @@ -0,0 +1,67 @@ +<html> + <head> + <title>User Defined Cleanups</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h2>User Defined Cleanups</h2> + <p><i>This feature is for experts.</i></p> + <p>You can define up to 10 custom cleanup actions. The cleanups are specified by <i>command + lines</i>. + </p> + <p>Select an entry in the list an set it to "enabled". Choose a title, the title + appears in the menus. + </p> + <p>Compose a command line. Use the "MSDOS prompt" (Windows 9x, command.com) or the + "Command prompt" (NT, cmd.exe) to get help about the available commands and to + test the command line. + </p> + <h3>Examples</h3> + <p> + <ul> + <li> + <pre>dir /b > dir.txt</pre> + List the filenames to the text file dir.txt.</li> + <li> + <pre>del *.bak</pre> + Delete all *.bak files in the current directory.</li> + <li> + <pre>del /s *.bak *.tmp</pre> + Recursively delete all *.bak and *.tmp files.</li> + <li> + <pre>windirstat.exe "%p"</pre> + Call up a second instance of WinDirStat with the path of the selected directory + (a PATH to windirstat.exe must be set).</li> + </ul> + </p> + <h3>Examples (NT and higher)</h3> + <p> + <ul> + <li> + <pre>echo %n & pause</pre> + Display the name of the current directory.</li> + <li> + <pre>cd & pause</pre> + Display the current path and wait for a key stroke.</li> + <li> + <pre>cd .. && myzip "%n"</pre> + Compress the selected directory (with the hypothetic tool myzip).</li> + </ul> + </p> + <p>The meaning of the placeholders %p, %n, %sp, %sn is shown in the dialog. Don't + forget to enclose them in quotation marks, if necessary.</p> + <h3>Assembly of the command line</h3> + <p>Suppose you enter the command line + <pre>xyz</pre> + . WinDirStat then trys to start the following process: + <pre>%COMSPEC% /c xyz</pre> + </p> + <h3>More Options</h3> + <p>Specify, for which item types the cleanup works.</p> + <p>Specify, whether the cleanup shall be applied recursively on all subdirectories + (depth first).</p> + <p>The other options should be clear.</p> + </BODY> +</html> diff --git a/wdshelp/wdshelp.vcproj b/wdshelp/wdshelp.vcproj new file mode 100644 index 0000000..38d5df5 --- /dev/null +++ b/wdshelp/wdshelp.vcproj @@ -0,0 +1,122 @@ +<?xml version="1.0" encoding="Windows-1252"?> +<VisualStudioProject + ProjectType="Visual C++" + Version="7.10" + Name="wdshelp" + ProjectGUID="{7EE5206B-1657-482A-B6A1-343DE5D6DE11}" + Keyword="MakeFileProj"> + <Platforms> + <Platform + Name="Win32"/> + </Platforms> + <Configurations> + <Configuration + Name="Debug|Win32" + OutputDirectory="Debug" + IntermediateDirectory="Debug" + ConfigurationType="0"> + <Tool + Name="VCNMakeTool" + BuildCommandLine="echo The help file will only be generated in release build." + ReBuildCommandLine="echo The help file will only be generated in release build." + CleanCommandLine="echo clean" + Output="windirstat.chm"/> + </Configuration> + <Configuration + Name="Release|Win32" + OutputDirectory="Release" + IntermediateDirectory="Release" + ConfigurationType="0"> + <Tool + Name="VCNMakeTool" + BuildCommandLine="hhc "$(ProjectDir)windirstat.hhp" || cd ." + ReBuildCommandLine="hhc "$(ProjectDir)windirstat.hhp" || cd ." + CleanCommandLine="del ..\..\release\wdsh0407.chm" + Output="..\..\release\windirstat.chm"/> + </Configuration> + </Configurations> + <References> + </References> + <Files> + <Filter + Name="Source Files" + Filter="cpp;c;cxx;def;odl;idl;hpj;bat;asm;asmx" + UniqueIdentifier="{4FC737F1-C7A5-4376-A066-2A32D752A2FF}"> + <File + RelativePath=".\actions.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\configuration.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\coupling.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\deinstallation.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\directorytree.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\extensionlist.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\faq.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\format.css"> + </File> + <File + RelativePath=".\gnufdl.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\legend.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\limits.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\selectdrivesdialog.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\sorting.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\Table of Contents.hhc"> + </File> + <File + RelativePath=".\treemap.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\userdefinedcleanups.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\whatisatree.htm" + DeploymentContent="TRUE"> + </File> + <File + RelativePath=".\windirstat.hhp"> + </File> + <File + RelativePath=".\windirstat.htm" + DeploymentContent="TRUE"> + </File> + </Filter> + </Files> + <Globals> + </Globals> +</VisualStudioProject> diff --git a/wdshelp/whatisatree.htm b/wdshelp/whatisatree.htm new file mode 100644 index 0000000..42298e1 --- /dev/null +++ b/wdshelp/whatisatree.htm @@ -0,0 +1,62 @@ +<html> + <head> + <title>What is a Directory Tree?</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta content="http://schemas.microsoft.com/intellisense/ie5" name="vs_targetSchema"> + <LINK href="format.css" type="text/css" rel="stylesheet"> + </head> + <BODY> + <h2>What is a Directory Tree?</h2> + <p>On most computer operating systems, so on Microsoft Windows, the data on the + hard disk are organized hierarchically. + </p> + <p>On the one hand there are the <i>files</i> which have a certain size and contain + the effective data. Each file has a name. Under Microsoft Windows the "filename + extension" informs about the type of the file. The extension ".exe", for + instance, indicates that it's a program file. The extension ".doc" indicates a + WinWord document, ".jpg" is a photo, and so on. But ridiculously the Microsoft + Windows Explorer hides these filename extensions by default. You can change + this behaviour in the options menu of the Windows Explorer. + </p> + <p>On the other hand there are <i>directories</i>. The Windows Explorer and + WinDirStat, too, symbolize directories as yellow folders. Directories also + have a name, but normally without a filename extension. Directories only serve + to contain files and other directories ("sub-directories"). Due to the fact + that directories can contain subdirectories, and those again can contain + subdirectories, the result is a hierarchical structure on the disk. + </p> + <p> + <img src="tree.jpg" width="99" height="105" align="left" vspace="20" hspace="20" /> + Instead of "hierarchical structure" we simply say <i>tree structure</i>. Since + a tree is built hierarchical as well: The trunk branches out into branches, the + branches into sub-branches, twigs and finally into the leafs. In a file system + the so called root directory is the trunk, the directories + are the branches and the files are the leafs. + </p> + <p> + That's why we call the file system of a computer simply a "directory tree". + </p> + <p><br clear="all" /> + Unlike most real trees, on a disk the trunk and the branches already have + leafs. And, unlike most real trees, too: the <u>files</u> are the voluminous + entities (the size of which is mesured by megabytes or gigabytes), whereas the + actual directories are neglectibly small. By the way, we imagine abstract trees + as turned round: the root at the top, the leafs at the bottom. + </p> + <p>If you saw a branch off a tree and stick it into the earth, then it becomes + itself a little tree (well, at least it looks like one): Every branch is, + together with its sub-branches and leafs, itself a tree, a <i>subtree</i>. + </p> + <p>The family tree metaphor is often used as well: The subdirectories and files of + a directory are called its <i>children</i>. And a directory containing a + subdirectory or file is called their <i>parent</i>. The root directory is + earliest ancestor of all items in the directory tree. + </p> + <p>A <i>path</i> like "C:\documents\letters\draft\loveletter.doc" indicates that on + the hard disk C:, in the root directory "C:\" there is a directory "documents", + under it the subdirectory "letters", under it a subdirectory "draft" and in + there a file "loveletter.doc". So the path is a precise representation of the + way from the root to the leaf. + </p> + </BODY> +</html> diff --git a/wdshelp/windirstat.hhp b/wdshelp/windirstat.hhp new file mode 100644 index 0000000..7eaaa3a --- /dev/null +++ b/wdshelp/windirstat.hhp @@ -0,0 +1,43 @@ +[OPTIONS] +Compatibility=1.1 or later +Compiled file=..\..\release\windirstat.chm +Contents file=Table of Contents.hhc +Default Window=main +Default topic=windirstat.htm +Display compile progress=No +Full-text search=Yes +Language=0x409 Englisch (USA) +Title=WinDirStat + +[WINDOWS] +main="WinDirStat","Table of Contents.hhc",,"windirstat.htm","windirstat.htm",,,,,0x63420,,0x3006,[22,19,816,782],0x108f0000,,,,,,0 + + +[FILES] +windirstat.htm +directorytree.htm +extensionlist.htm +treemap.htm +actions.htm +configuration.htm +coupling.htm +faq.htm +gnufdl.htm +legend.htm +selectdrivesdialog.htm +sorting.htm +whatisatree.htm +userdefinedcleanups.htm +limits.htm +deinstallation.htm + +[ALIAS] +IDH_StartPage=windirstat.htm +IDH_UserDefinedCleanups=userdefinedcleanups.htm +IDH_Treemap=treemap.htm + +[MAP] +#include ..\windirstat\helpmap.h + +[INFOTYPES] + diff --git a/wdshelp/windirstat.htm b/wdshelp/windirstat.htm new file mode 100644 index 0000000..160d5d2 --- /dev/null +++ b/wdshelp/windirstat.htm @@ -0,0 +1,63 @@ +<html> + <head> + <title>WinDirStat</title> + <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> + <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5"> + <link rel="stylesheet" type="text/css" href="format.css"> + </head> + <BODY> + <h1 style="margin-bottom:1pt">WinDirStat - Directory Statistics</h1> + <P style="font-size:70%;margin-top:2pt">Copyright (c) 2003 Bernhard Seifert. + 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". + </P> + <p>Shows where all your disk space has gone, and helps you clean it up. + </p> + <p style="color=#006000">You know the problem: The hard disk is almost full, and + you don't know, where the big files actually are lying, which occupy all the + space. They may well be hidden in sub-sub-directories. To find out this by + means of the Windows Explorer, is tiring: you had to expand and collapse the + directories again and again or view the "Properties" of the directories, which + always count just the size of <i>one</i> subtree. It's hard to form a mental + image of the hard disk usage in this way. This is where WinDirStat helps. + </p> + <p>On start up WinDirStat opens the <a href="selectdrivesdialog.htm">Select Drives + Dialog</a>. Press the OK button. + </p> + <p> + Then WinDirStat reads in the whole <a href="whatisatree.htm">directory tree</a> + once (this can last some minutes depending on the hard disk size) and then + presents it in three useful views: + </p> + <table border="1" bordercolor="#007000" style="BORDER-RIGHT:3px solid; BORDER-TOP:3px solid; BORDER-LEFT:3px solid; WIDTH:373px; BORDER-BOTTOM:3px solid; BORDER-COLLAPSE:collapse; HEIGHT:226px"> + <tr> + <td colspan="2" style="COLOR:#ffffff; HEIGHT:17px; BACKGROUND-COLOR:#007000">WinDirStat</td> + </tr> + <tr style="HEIGHT:80px"> + <td align="center" style="WIDTH: 241px; HEIGHT: 70px"><a href="directorytree.htm">Directory + List</a></td> + <td align="center" style="HEIGHT: 70px"><a href="extensionlist.htm">Extension List</a></td> + </tr> + <tr style="HEIGHT:100px"> + <td colspan="2" align="center"><a href="treemap.htm">Treemap</a></td> + </tr> + </table> + <p>The views are <a href="coupling.htm">coupled</a> with each other. + </p> + <p>You can clean up the hard disks with serveral <a href="actions.htm">Cleanups</a>. + </p> + <p>The views and the <a href="userdefinedcleanups.htm">User Defined Cleanups</a> can + be <a href="configuration.htm">configured</a> according to your personal needs. + </p> + <p><a href="sorting.htm">Sorting</a></p> + <p><a href="legend.htm">Legend</a></p> + <p><a href="faq.htm">Frequently Asked Questions</a></p> + <p><a href="limits.htm">Limits</a></p> + <p><a href="deinstallation.htm">Deinstallation</a></p> + <P style="font-size:70%"><a href="gnufdl.htm">GNU Free Documentation License</a></P> + <P> </P> + </BODY> +</html> |
