Added abandoned Filelight application

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/filelight@1084392 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
v3.5.13-sru
tpearson 15 years ago
commit 3c7b870f36

@ -0,0 +1 @@
Max Howell <max.howell@methylblue.com>

@ -0,0 +1,340 @@
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Steet, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation's software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The "Program", below,
refers to any such program or work, and a "work based on the Program"
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Steet, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w' and `show c'; they could even be
mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision' (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.

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

@ -0,0 +1,122 @@
1.0
Added copy to clipboard function to segment context menus
Accepts URLs from drag and drop
Click central circle to go "up"
Fixed a crash on startup
Fixed a crash during use
Fixed not displaying non-latin1 label correctly
0.6.3
Made "Scan Directory..." a KStdAction::open with setText( "Scan Directory..." );
Swaped map rendering from bitBlt to paintPixmap (again) as some users get problems with the labels being obliterated
LocationBar history is saved inbetween sessions for KDE >= 3.1.3
Rescans are forced if locationBar Go is pushed for location to current map
Fixed several bugs related to resizing the filemap
Initial map display had a long running issue which meant you had to perform a resize to ensure all detail was shown. I finally put in the hours and fixed it.
Cancelling scans clears the location bar
Option to show files not represented as segments (because they are too small) combined in large segments with relevant summaries
Directories that would normally have no child segments shown now have hidden Files segment shown
Fixed faulty show/hide of progress box when many scans done in quick succession
Session management
Saving of Window/*bar settings inbetween sessions
Fixed popup related non-updates and false action calls
Canvas code cleanup
Stopped combo activated scans being called twice
Improved map generation speed (scan speeds are still slow however)
Appropriate wait cursors are set during long operations (scans, map generation)
Fixed misrendered transparency when tooltips exceed Filelight boundries
Optimised and de-flickered the tooltips
Segments that contain unrepresented files (due to 5 level limit on maps) now show a thick border at the edge to indicate that there are unrepresented files
Commandline now accepts ../ and ./ type arguments
Add "Open Konsole here" to context-menu, also tidied it up and made it properly context relevant
Popup title is now relative to map path to reduce menu width somewhat without resorting to csqueeze()
Fixed bug with not showing unrepresented files for dirs that contained dirs
Improvement selection of units for tooltips (always prefer megabytes unless < 0.01 MB)
Improved selection of decimal places for size display (2sig.fig. please)
Label font sizes now default to the system standard
Labels have indentation relative to their level
Label selection improved (not enough yet though!)
Better looking label line diagonals
When smaller fonts are requested, Filelight maximises the font size differences
Attempted to fix crash at exit bug
Made files shades of gray, made indicator for directories that have unshown files
Removed presence of multi-file segments except in root level circumstances (unless Show Small Files is selected in Settings)
Contrast system revamped, you can now have more contrast
Segment colouring system rewritten, better distinction between different segment types
Used more KStdActions (less work for translation teams at very least)
Fixed bug where segmenttip wasn't shown for 1st pixel but labels were
Directories with unshown files have better arrow heads now thanks to some clever trig
Checked for possible cases where division by zero might occur and corrected code
Huge code rewrite in preparation for transition to KPart (must release soon, this is getting silly)
Allow clicks on the central circle to represent the map's root (eg. middle-click to open in Konqi)
0.6.2
Attempted a fix for the absurdly large file bug (eg > 1400GB!)
Linking bug fixed for Gentoo systems
Compile bug fixed for GCC < 3
Fixed crash bug when scan had been stopped and then back then forward pressed
Fixed another compile bug for systems that don't support large files (Debian apparently)
Internationalisation support thanks to patch from André Somers
Made the tooltip translucent (NOT a gimmick, this feature is essential IMO)
Started making debug messages use kdDebug so users can enable/disable the messages
Implemented XML GUI
Vast slot/signal cleanup, fixed many bugs
Fixed a few bugs with the progress box
Cancelled scans now remain stored in the back/forward histories
Fixed incorrect reporting of directory file counts
Increased minimum segment size to 3px outer diameter (any depth)
Added location_bar UI element to toolbar (much work)
The segment tip now appears below the cursor when hovering over the upper part of the map
Increased the recent scans list to 8 entries and made the combohistory work better
0.6.1
Filelight again compiles on KDE <= 3.1.3 (but with some reduced functionality)
Rewrote HistoryAction code
Improved default choice of smallest font
Lowest level segment labels show whenever mouse is not over anything
Middle click opens segment according to mime type (eg. jpgs open in kuickshow)
Implemented realtime contrast updates
Added antialiasing, font size and contrast settings to appearance tab
Renamed "colour scheme" tab "appearance"
Extruded label fontsizes reflect their segment's depth
Rescans ignore tree cache
Changing scan options clears the tree cache
Directory select dialog shows current path as selected when opened
Scans no longer have to be repeated
Implemented antialiasing for the map, very slow so only happens after resizes
Gracefully handles failures to read file attributes
Rewrote backend with templating, should have done that in first place!
Improved changelog listing methods!
Included support for GNU systems that don't support large files (>2GB)
0.6.0
Added expanded labels to give more information on segments in focus
Added settings dialogs
Added new colour schemes
Allowed scans to not cross at mount points
Added #Files info for directory tooltips
filemap is now displayed centrally
Shows percentage of files in directories
0.5.1
Added Filelight to the Utilities submenu in the K-Menu
Tooltips are now presented for file info instead of using the statusbar
Made resizing of the filemap smoother
Improved the icon and made a 48x48 and 22x22 version
Reworked the code somewhat
Scans can now be cancelled
The go history actions are more intelligent
Fixed all the bugs I could find
Attempted to improve filemap contrast some more (still not perfect, but getting there)
Added visual activation cues for various clicks
0.50
Few bug fixes
Improved performance for rendering and scanning
Improved contrast of the filemap
Added icon
Added left and right click functionality
Improved error handling
0.45
Added toolbar, implemented history functionality
Click to scan segments
Increased filesize limit to 4096 GB
Fixed <time.h> required - make bug
Various optimisations
0.4
Initial public release

@ -0,0 +1,36 @@
Filelight INSTALL
===================
Simply:
$ ./configure && make && su -c "make install"
But, I recommend:
$ CXXFLAGS="-O3" ./configure --enable-final --disable-debug \
&& make && su -c "make install"
Troubleshooting
=================
Check you have the kde development packages installed, they'll be named
something like:
kde-devel
This should pull in a lot of other development packages (unless they are already
installed) like:
x11-devel
qt-devel
If you get stuck, please email me the config.log file with any information you
can provide. I will get back to you! Compile issues suck, I know this full well.
--------------------------------------------------------------------------------
I hope you enjoy using Filelight!
Max Howell <max.howell@methylblue.com>

@ -0,0 +1,8 @@
SUBDIRS = src misc doc po
messages: rc.cpp
$(EXTRACTRC) `find . -name "*.rc" -o -name "*.ui"` >> rc.cpp
LIST=`find src -name \*.h -o -name \*.cpp` ;\
if test -n "$$LIST"; then \
$(XGETTEXT) rc.cpp $$LIST -o $(podir)/filelight.pot; \
fi

@ -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:

@ -0,0 +1 @@

@ -0,0 +1,49 @@
Filelight README
==================
Filelight allows you to understand exactly where your diskspace is being used by
graphically representating your filesystem as a set of concentric
segmented-rings.
README last updated with respect to 1.0
--------------------------------------------------------------------------------
Dependencies
==============
Filelight depends on KDElibs >= 3.2 and therefore Qt >= 3.2.
Usage Tips
============
* Click on directories to center the view there
* Click on files to launch the application associated with them
* Middle click to open files/directories with Konqueror
* Right click on the central white circle to manipulate the base directory
* Increase the window size to see more detail
* Hover over segments to find out more information
* Available as a view-KPart in Konqueror
* You can specify a directory to scan on startup from the command line, eg:
$ filelight /home/mxcl
Install
=========
See the accompanying file; INSTALL.
Bugs
======
There are less bugs everyday! Please report bugs to filelight@methylblue.com
--------------------------------------------------------------------------------
I hope you enjoy using Filelight!
Max Howell <max.howell@methylblue.com>

28
TODO

@ -0,0 +1,28 @@
1.3
features for sysadmins, split by users etc.
1.2
split rendering engine from data-gatherer and allow data to be fed through a pipe thus allowing different data sources to be profiled.
show preview icons next to the labels
last access time colour scheme
History actions need to have menu pulldown just like konqi
show statusbar signal to say that diretories weren't scanned due to lack of permissions (allow user to enter root password, for this scan only or to keep and then scan only bits that were missed)
determine if canvas is too square and shrink map accordingly
1.1
If scanning a partition show free space
if the view is square shrink the map slightly as a slightly rectangular view is preferable
use kdirwatcher, then move rescan to scan menu, rename force rescan
clicking center goes up directory
refactor disklister.cpp
implement vectors instead of double-linked lists for file data
Trace inodes in binarytree to avoid recursive hardlinks and counting same directory tree twice
admin mode
fix that Part settings file is not same as app settings file
support other mouse actions for central circle (ie middle click, right click)
write caches for all scans, so if crash or something that root scan that took 20 mins is not lost
MAYBE
flicking mouse wheel shows different information in tooltip, and there's an off setting, show temp status message to reflect info box
ideally, eventually show which labels are children of which by grouping them with a coloured square or something
create html summary files (pics and text)

File diff suppressed because it is too large Load Diff

863
aclocal.m4 vendored

@ -0,0 +1,863 @@
# generated automatically by aclocal 1.9.6 -*- Autoconf -*-
# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
# 2005 Free Software Foundation, Inc.
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
# Copyright (C) 2002, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# AM_AUTOMAKE_VERSION(VERSION)
# ----------------------------
# Automake X.Y traces this macro to ensure aclocal.m4 has been
# generated from the m4 files accompanying Automake X.Y.
AC_DEFUN([AM_AUTOMAKE_VERSION], [am__api_version="1.9"])
# AM_SET_CURRENT_AUTOMAKE_VERSION
# -------------------------------
# Call AM_AUTOMAKE_VERSION so it can be traced.
# This function is AC_REQUIREd by AC_INIT_AUTOMAKE.
AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],
[AM_AUTOMAKE_VERSION([1.9.6])])
# AM_AUX_DIR_EXPAND -*- Autoconf -*-
# Copyright (C) 2001, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets
# $ac_aux_dir to `$srcdir/foo'. In other projects, it is set to
# `$srcdir', `$srcdir/..', or `$srcdir/../..'.
#
# Of course, Automake must honor this variable whenever it calls a
# tool from the auxiliary directory. The problem is that $srcdir (and
# therefore $ac_aux_dir as well) can be either absolute or relative,
# depending on how configure is run. This is pretty annoying, since
# it makes $ac_aux_dir quite unusable in subdirectories: in the top
# source directory, any form will work fine, but in subdirectories a
# relative path needs to be adjusted first.
#
# $ac_aux_dir/missing
# fails when called from a subdirectory if $ac_aux_dir is relative
# $top_srcdir/$ac_aux_dir/missing
# fails if $ac_aux_dir is absolute,
# fails when called from a subdirectory in a VPATH build with
# a relative $ac_aux_dir
#
# The reason of the latter failure is that $top_srcdir and $ac_aux_dir
# are both prefixed by $srcdir. In an in-source build this is usually
# harmless because $srcdir is `.', but things will broke when you
# start a VPATH build or use an absolute $srcdir.
#
# So we could use something similar to $top_srcdir/$ac_aux_dir/missing,
# iff we strip the leading $srcdir from $ac_aux_dir. That would be:
# am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"`
# and then we would define $MISSING as
# MISSING="\${SHELL} $am_aux_dir/missing"
# This will work as long as MISSING is not called from configure, because
# unfortunately $(top_srcdir) has no meaning in configure.
# However there are other variables, like CC, which are often used in
# configure, and could therefore not use this "fixed" $ac_aux_dir.
#
# Another solution, used here, is to always expand $ac_aux_dir to an
# absolute PATH. The drawback is that using absolute paths prevent a
# configured tree to be moved without reconfiguration.
AC_DEFUN([AM_AUX_DIR_EXPAND],
[dnl Rely on autoconf to set up CDPATH properly.
AC_PREREQ([2.50])dnl
# expand $ac_aux_dir to an absolute path
am_aux_dir=`cd $ac_aux_dir && pwd`
])
# AM_CONDITIONAL -*- Autoconf -*-
# Copyright (C) 1997, 2000, 2001, 2003, 2004, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 7
# AM_CONDITIONAL(NAME, SHELL-CONDITION)
# -------------------------------------
# Define a conditional.
AC_DEFUN([AM_CONDITIONAL],
[AC_PREREQ(2.52)dnl
ifelse([$1], [TRUE], [AC_FATAL([$0: invalid condition: $1])],
[$1], [FALSE], [AC_FATAL([$0: invalid condition: $1])])dnl
AC_SUBST([$1_TRUE])
AC_SUBST([$1_FALSE])
if $2; then
$1_TRUE=
$1_FALSE='#'
else
$1_TRUE='#'
$1_FALSE=
fi
AC_CONFIG_COMMANDS_PRE(
[if test -z "${$1_TRUE}" && test -z "${$1_FALSE}"; then
AC_MSG_ERROR([[conditional "$1" was never defined.
Usually this means the macro was only invoked conditionally.]])
fi])])
# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 8
# There are a few dirty hacks below to avoid letting `AC_PROG_CC' be
# written in clear, in which case automake, when reading aclocal.m4,
# will think it sees a *use*, and therefore will trigger all it's
# C support machinery. Also note that it means that autoscan, seeing
# CC etc. in the Makefile, will ask for an AC_PROG_CC use...
# _AM_DEPENDENCIES(NAME)
# ----------------------
# See how the compiler implements dependency checking.
# NAME is "CC", "CXX", "GCJ", or "OBJC".
# We try a few techniques and use that to set a single cache variable.
#
# We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was
# modified to invoke _AM_DEPENDENCIES(CC); we would have a circular
# dependency, and given that the user is not expected to run this macro,
# just rely on AC_PROG_CC.
AC_DEFUN([_AM_DEPENDENCIES],
[AC_REQUIRE([AM_SET_DEPDIR])dnl
AC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnl
AC_REQUIRE([AM_MAKE_INCLUDE])dnl
AC_REQUIRE([AM_DEP_TRACK])dnl
ifelse([$1], CC, [depcc="$CC" am_compiler_list=],
[$1], CXX, [depcc="$CXX" am_compiler_list=],
[$1], OBJC, [depcc="$OBJC" am_compiler_list='gcc3 gcc'],
[$1], GCJ, [depcc="$GCJ" am_compiler_list='gcc3 gcc'],
[depcc="$$1" am_compiler_list=])
AC_CACHE_CHECK([dependency style of $depcc],
[am_cv_$1_dependencies_compiler_type],
[if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then
# We make a subdir and do the tests there. Otherwise we can end up
# making bogus files that we don't know about and never remove. For
# instance it was reported that on HP-UX the gcc test will end up
# making a dummy file named `D' -- because `-MD' means `put the output
# in D'.
mkdir conftest.dir
# Copy depcomp to subdir because otherwise we won't find it if we're
# using a relative directory.
cp "$am_depcomp" conftest.dir
cd conftest.dir
# We will build objects and dependencies in a subdirectory because
# it helps to detect inapplicable dependency modes. For instance
# both Tru64's cc and ICC support -MD to output dependencies as a
# side effect of compilation, but ICC will put the dependencies in
# the current directory while Tru64 will put them in the object
# directory.
mkdir sub
am_cv_$1_dependencies_compiler_type=none
if test "$am_compiler_list" = ""; then
am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp`
fi
for depmode in $am_compiler_list; do
# Setup a source with many dependencies, because some compilers
# like to wrap large dependency lists on column 80 (with \), and
# we should not choose a depcomp mode which is confused by this.
#
# We need to recreate these files for each test, as the compiler may
# overwrite some of them when testing with obscure command lines.
# This happens at least with the AIX C compiler.
: > sub/conftest.c
for i in 1 2 3 4 5 6; do
echo '#include "conftst'$i'.h"' >> sub/conftest.c
# Using `: > sub/conftst$i.h' creates only sub/conftst1.h with
# Solaris 8's {/usr,}/bin/sh.
touch sub/conftst$i.h
done
echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf
case $depmode in
nosideeffect)
# after this tag, mechanisms are not by side-effect, so they'll
# only be used when explicitly requested
if test "x$enable_dependency_tracking" = xyes; then
continue
else
break
fi
;;
none) break ;;
esac
# We check with `-c' and `-o' for the sake of the "dashmstdout"
# mode. It turns out that the SunPro C++ compiler does not properly
# handle `-M -o', and we need to detect this.
if depmode=$depmode \
source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \
depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \
$SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \
>/dev/null 2>conftest.err &&
grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 &&
grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 &&
${MAKE-make} -s -f confmf > /dev/null 2>&1; then
# icc doesn't choke on unknown options, it will just issue warnings
# or remarks (even with -Werror). So we grep stderr for any message
# that says an option was ignored or not supported.
# When given -MP, icc 7.0 and 7.1 complain thusly:
# icc: Command line warning: ignoring option '-M'; no argument required
# The diagnosis changed in icc 8.0:
# icc: Command line remark: option '-MP' not supported
if (grep 'ignoring option' conftest.err ||
grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else
am_cv_$1_dependencies_compiler_type=$depmode
break
fi
fi
done
cd ..
rm -rf conftest.dir
else
am_cv_$1_dependencies_compiler_type=none
fi
])
AC_SUBST([$1DEPMODE], [depmode=$am_cv_$1_dependencies_compiler_type])
AM_CONDITIONAL([am__fastdep$1], [
test "x$enable_dependency_tracking" != xno \
&& test "$am_cv_$1_dependencies_compiler_type" = gcc3])
])
# AM_SET_DEPDIR
# -------------
# Choose a directory name for dependency files.
# This macro is AC_REQUIREd in _AM_DEPENDENCIES
AC_DEFUN([AM_SET_DEPDIR],
[AC_REQUIRE([AM_SET_LEADING_DOT])dnl
AC_SUBST([DEPDIR], ["${am__leading_dot}deps"])dnl
])
# AM_DEP_TRACK
# ------------
AC_DEFUN([AM_DEP_TRACK],
[AC_ARG_ENABLE(dependency-tracking,
[ --disable-dependency-tracking speeds up one-time build
--enable-dependency-tracking do not reject slow dependency extractors])
if test "x$enable_dependency_tracking" != xno; then
am_depcomp="$ac_aux_dir/depcomp"
AMDEPBACKSLASH='\'
fi
AM_CONDITIONAL([AMDEP], [test "x$enable_dependency_tracking" != xno])
AC_SUBST([AMDEPBACKSLASH])
])
# Generate code to set up dependency tracking. -*- Autoconf -*-
# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
#serial 3
# _AM_OUTPUT_DEPENDENCY_COMMANDS
# ------------------------------
AC_DEFUN([_AM_OUTPUT_DEPENDENCY_COMMANDS],
[for mf in $CONFIG_FILES; do
# Strip MF so we end up with the name of the file.
mf=`echo "$mf" | sed -e 's/:.*$//'`
# Check whether this is an Automake generated Makefile or not.
# We used to match only the files named `Makefile.in', but
# some people rename them; so instead we look at the file content.
# Grep'ing the first line is not enough: some people post-process
# each Makefile.in and add a new line on top of each file to say so.
# So let's grep whole file.
if grep '^#.*generated by automake' $mf > /dev/null 2>&1; then
dirpart=`AS_DIRNAME("$mf")`
else
continue
fi
# Extract the definition of DEPDIR, am__include, and am__quote
# from the Makefile without running `make'.
DEPDIR=`sed -n 's/^DEPDIR = //p' < "$mf"`
test -z "$DEPDIR" && continue
am__include=`sed -n 's/^am__include = //p' < "$mf"`
test -z "am__include" && continue
am__quote=`sed -n 's/^am__quote = //p' < "$mf"`
# When using ansi2knr, U may be empty or an underscore; expand it
U=`sed -n 's/^U = //p' < "$mf"`
# Find all dependency output files, they are included files with
# $(DEPDIR) in their names. We invoke sed twice because it is the
# simplest approach to changing $(DEPDIR) to its actual value in the
# expansion.
for file in `sed -n "
s/^$am__include $am__quote\(.*(DEPDIR).*\)$am__quote"'$/\1/p' <"$mf" | \
sed -e 's/\$(DEPDIR)/'"$DEPDIR"'/g' -e 's/\$U/'"$U"'/g'`; do
# Make sure the directory exists.
test -f "$dirpart/$file" && continue
fdir=`AS_DIRNAME(["$file"])`
AS_MKDIR_P([$dirpart/$fdir])
# echo "creating $dirpart/$file"
echo '# dummy' > "$dirpart/$file"
done
done
])# _AM_OUTPUT_DEPENDENCY_COMMANDS
# AM_OUTPUT_DEPENDENCY_COMMANDS
# -----------------------------
# This macro should only be invoked once -- use via AC_REQUIRE.
#
# This code is only required when automatic dependency tracking
# is enabled. FIXME. This creates each `.P' file that we will
# need in order to bootstrap the dependency handling code.
AC_DEFUN([AM_OUTPUT_DEPENDENCY_COMMANDS],
[AC_CONFIG_COMMANDS([depfiles],
[test x"$AMDEP_TRUE" != x"" || _AM_OUTPUT_DEPENDENCY_COMMANDS],
[AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir"])
])
# Copyright (C) 1996, 1997, 2000, 2001, 2003, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 8
# AM_CONFIG_HEADER is obsolete. It has been replaced by AC_CONFIG_HEADERS.
AU_DEFUN([AM_CONFIG_HEADER], [AC_CONFIG_HEADERS($@)])
# Do all the work for Automake. -*- Autoconf -*-
# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 12
# This macro actually does too much. Some checks are only needed if
# your package does certain things. But this isn't really a big deal.
# AM_INIT_AUTOMAKE(PACKAGE, VERSION, [NO-DEFINE])
# AM_INIT_AUTOMAKE([OPTIONS])
# -----------------------------------------------
# The call with PACKAGE and VERSION arguments is the old style
# call (pre autoconf-2.50), which is being phased out. PACKAGE
# and VERSION should now be passed to AC_INIT and removed from
# the call to AM_INIT_AUTOMAKE.
# We support both call styles for the transition. After
# the next Automake release, Autoconf can make the AC_INIT
# arguments mandatory, and then we can depend on a new Autoconf
# release and drop the old call support.
AC_DEFUN([AM_INIT_AUTOMAKE],
[AC_PREREQ([2.58])dnl
dnl Autoconf wants to disallow AM_ names. We explicitly allow
dnl the ones we care about.
m4_pattern_allow([^AM_[A-Z]+FLAGS$])dnl
AC_REQUIRE([AM_SET_CURRENT_AUTOMAKE_VERSION])dnl
AC_REQUIRE([AC_PROG_INSTALL])dnl
# test to see if srcdir already configured
if test "`cd $srcdir && pwd`" != "`pwd`" &&
test -f $srcdir/config.status; then
AC_MSG_ERROR([source directory already configured; run "make distclean" there first])
fi
# test whether we have cygpath
if test -z "$CYGPATH_W"; then
if (cygpath --version) >/dev/null 2>/dev/null; then
CYGPATH_W='cygpath -w'
else
CYGPATH_W=echo
fi
fi
AC_SUBST([CYGPATH_W])
# Define the identity of the package.
dnl Distinguish between old-style and new-style calls.
m4_ifval([$2],
[m4_ifval([$3], [_AM_SET_OPTION([no-define])])dnl
AC_SUBST([PACKAGE], [$1])dnl
AC_SUBST([VERSION], [$2])],
[_AM_SET_OPTIONS([$1])dnl
AC_SUBST([PACKAGE], ['AC_PACKAGE_TARNAME'])dnl
AC_SUBST([VERSION], ['AC_PACKAGE_VERSION'])])dnl
_AM_IF_OPTION([no-define],,
[AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Name of package])
AC_DEFINE_UNQUOTED(VERSION, "$VERSION", [Version number of package])])dnl
# Some tools Automake needs.
AC_REQUIRE([AM_SANITY_CHECK])dnl
AC_REQUIRE([AC_ARG_PROGRAM])dnl
AM_MISSING_PROG(ACLOCAL, aclocal-${am__api_version})
AM_MISSING_PROG(AUTOCONF, autoconf)
AM_MISSING_PROG(AUTOMAKE, automake-${am__api_version})
AM_MISSING_PROG(AUTOHEADER, autoheader)
AM_MISSING_PROG(MAKEINFO, makeinfo)
AM_PROG_INSTALL_SH
AM_PROG_INSTALL_STRIP
AC_REQUIRE([AM_PROG_MKDIR_P])dnl
# We need awk for the "check" target. The system "awk" is bad on
# some platforms.
AC_REQUIRE([AC_PROG_AWK])dnl
AC_REQUIRE([AC_PROG_MAKE_SET])dnl
AC_REQUIRE([AM_SET_LEADING_DOT])dnl
_AM_IF_OPTION([tar-ustar], [_AM_PROG_TAR([ustar])],
[_AM_IF_OPTION([tar-pax], [_AM_PROG_TAR([pax])],
[_AM_PROG_TAR([v7])])])
_AM_IF_OPTION([no-dependencies],,
[AC_PROVIDE_IFELSE([AC_PROG_CC],
[_AM_DEPENDENCIES(CC)],
[define([AC_PROG_CC],
defn([AC_PROG_CC])[_AM_DEPENDENCIES(CC)])])dnl
AC_PROVIDE_IFELSE([AC_PROG_CXX],
[_AM_DEPENDENCIES(CXX)],
[define([AC_PROG_CXX],
defn([AC_PROG_CXX])[_AM_DEPENDENCIES(CXX)])])dnl
])
])
# When config.status generates a header, we must update the stamp-h file.
# This file resides in the same directory as the config header
# that is generated. The stamp files are numbered to have different names.
# Autoconf calls _AC_AM_CONFIG_HEADER_HOOK (when defined) in the
# loop where config.status creates the headers, so we can generate
# our stamp files there.
AC_DEFUN([_AC_AM_CONFIG_HEADER_HOOK],
[# Compute $1's index in $config_headers.
_am_stamp_count=1
for _am_header in $config_headers :; do
case $_am_header in
$1 | $1:* )
break ;;
* )
_am_stamp_count=`expr $_am_stamp_count + 1` ;;
esac
done
echo "timestamp for $1" >`AS_DIRNAME([$1])`/stamp-h[]$_am_stamp_count])
# Copyright (C) 2001, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# AM_PROG_INSTALL_SH
# ------------------
# Define $install_sh.
AC_DEFUN([AM_PROG_INSTALL_SH],
[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
install_sh=${install_sh-"$am_aux_dir/install-sh"}
AC_SUBST(install_sh)])
# Copyright (C) 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 2
# Check whether the underlying file-system supports filenames
# with a leading dot. For instance MS-DOS doesn't.
AC_DEFUN([AM_SET_LEADING_DOT],
[rm -rf .tst 2>/dev/null
mkdir .tst 2>/dev/null
if test -d .tst; then
am__leading_dot=.
else
am__leading_dot=_
fi
rmdir .tst 2>/dev/null
AC_SUBST([am__leading_dot])])
# Check to see how 'make' treats includes. -*- Autoconf -*-
# Copyright (C) 2001, 2002, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 3
# AM_MAKE_INCLUDE()
# -----------------
# Check to see how make treats includes.
AC_DEFUN([AM_MAKE_INCLUDE],
[am_make=${MAKE-make}
cat > confinc << 'END'
am__doit:
@echo done
.PHONY: am__doit
END
# If we don't find an include directive, just comment out the code.
AC_MSG_CHECKING([for style of include used by $am_make])
am__include="#"
am__quote=
_am_result=none
# First try GNU make style include.
echo "include confinc" > confmf
# We grep out `Entering directory' and `Leaving directory'
# messages which can occur if `w' ends up in MAKEFLAGS.
# In particular we don't look at `^make:' because GNU make might
# be invoked under some other name (usually "gmake"), in which
# case it prints its new name instead of `make'.
if test "`$am_make -s -f confmf 2> /dev/null | grep -v 'ing directory'`" = "done"; then
am__include=include
am__quote=
_am_result=GNU
fi
# Now try BSD make style include.
if test "$am__include" = "#"; then
echo '.include "confinc"' > confmf
if test "`$am_make -s -f confmf 2> /dev/null`" = "done"; then
am__include=.include
am__quote="\""
_am_result=BSD
fi
fi
AC_SUBST([am__include])
AC_SUBST([am__quote])
AC_MSG_RESULT([$_am_result])
rm -f confinc confmf
])
# Fake the existence of programs that GNU maintainers use. -*- Autoconf -*-
# Copyright (C) 1997, 1999, 2000, 2001, 2003, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 4
# AM_MISSING_PROG(NAME, PROGRAM)
# ------------------------------
AC_DEFUN([AM_MISSING_PROG],
[AC_REQUIRE([AM_MISSING_HAS_RUN])
$1=${$1-"${am_missing_run}$2"}
AC_SUBST($1)])
# AM_MISSING_HAS_RUN
# ------------------
# Define MISSING if not defined so far and test if it supports --run.
# If it does, set am_missing_run to use it, otherwise, to nothing.
AC_DEFUN([AM_MISSING_HAS_RUN],
[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnl
test x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing"
# Use eval to expand $SHELL
if eval "$MISSING --run true"; then
am_missing_run="$MISSING --run "
else
am_missing_run=
AC_MSG_WARN([`missing' script is too old or missing])
fi
])
# Copyright (C) 2003, 2004, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# AM_PROG_MKDIR_P
# ---------------
# Check whether `mkdir -p' is supported, fallback to mkinstalldirs otherwise.
#
# Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
# created by `make install' are always world readable, even if the
# installer happens to have an overly restrictive umask (e.g. 077).
# This was a mistake. There are at least two reasons why we must not
# use `-m 0755':
# - it causes special bits like SGID to be ignored,
# - it may be too restrictive (some setups expect 775 directories).
#
# Do not use -m 0755 and let people choose whatever they expect by
# setting umask.
#
# We cannot accept any implementation of `mkdir' that recognizes `-p'.
# Some implementations (such as Solaris 8's) are not thread-safe: if a
# parallel make tries to run `mkdir -p a/b' and `mkdir -p a/c'
# concurrently, both version can detect that a/ is missing, but only
# one can create it and the other will error out. Consequently we
# restrict ourselves to GNU make (using the --version option ensures
# this.)
AC_DEFUN([AM_PROG_MKDIR_P],
[if mkdir -p --version . >/dev/null 2>&1 && test ! -d ./--version; then
# We used to keeping the `.' as first argument, in order to
# allow $(mkdir_p) to be used without argument. As in
# $(mkdir_p) $(somedir)
# where $(somedir) is conditionally defined. However this is wrong
# for two reasons:
# 1. if the package is installed by a user who cannot write `.'
# make install will fail,
# 2. the above comment should most certainly read
# $(mkdir_p) $(DESTDIR)$(somedir)
# so it does not work when $(somedir) is undefined and
# $(DESTDIR) is not.
# To support the latter case, we have to write
# test -z "$(somedir)" || $(mkdir_p) $(DESTDIR)$(somedir),
# so the `.' trick is pointless.
mkdir_p='mkdir -p --'
else
# On NextStep and OpenStep, the `mkdir' command does not
# recognize any option. It will interpret all options as
# directories to create, and then abort because `.' already
# exists.
for d in ./-p ./--version;
do
test -d $d && rmdir $d
done
# $(mkinstalldirs) is defined by Automake if mkinstalldirs exists.
if test -f "$ac_aux_dir/mkinstalldirs"; then
mkdir_p='$(mkinstalldirs)'
else
mkdir_p='$(install_sh) -d'
fi
fi
AC_SUBST([mkdir_p])])
# Helper functions for option handling. -*- Autoconf -*-
# Copyright (C) 2001, 2002, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 3
# _AM_MANGLE_OPTION(NAME)
# -----------------------
AC_DEFUN([_AM_MANGLE_OPTION],
[[_AM_OPTION_]m4_bpatsubst($1, [[^a-zA-Z0-9_]], [_])])
# _AM_SET_OPTION(NAME)
# ------------------------------
# Set option NAME. Presently that only means defining a flag for this option.
AC_DEFUN([_AM_SET_OPTION],
[m4_define(_AM_MANGLE_OPTION([$1]), 1)])
# _AM_SET_OPTIONS(OPTIONS)
# ----------------------------------
# OPTIONS is a space-separated list of Automake options.
AC_DEFUN([_AM_SET_OPTIONS],
[AC_FOREACH([_AM_Option], [$1], [_AM_SET_OPTION(_AM_Option)])])
# _AM_IF_OPTION(OPTION, IF-SET, [IF-NOT-SET])
# -------------------------------------------
# Execute IF-SET if OPTION is set, IF-NOT-SET otherwise.
AC_DEFUN([_AM_IF_OPTION],
[m4_ifset(_AM_MANGLE_OPTION([$1]), [$2], [$3])])
# Check to make sure that the build environment is sane. -*- Autoconf -*-
# Copyright (C) 1996, 1997, 2000, 2001, 2003, 2005
# Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 4
# AM_SANITY_CHECK
# ---------------
AC_DEFUN([AM_SANITY_CHECK],
[AC_MSG_CHECKING([whether build environment is sane])
# Just in case
sleep 1
echo timestamp > conftest.file
# Do `set' in a subshell so we don't clobber the current shell's
# arguments. Must try -L first in case configure is actually a
# symlink; some systems play weird games with the mod time of symlinks
# (eg FreeBSD returns the mod time of the symlink's containing
# directory).
if (
set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null`
if test "$[*]" = "X"; then
# -L didn't work.
set X `ls -t $srcdir/configure conftest.file`
fi
rm -f conftest.file
if test "$[*]" != "X $srcdir/configure conftest.file" \
&& test "$[*]" != "X conftest.file $srcdir/configure"; then
# If neither matched, then we have a broken ls. This can happen
# if, for instance, CONFIG_SHELL is bash and it inherits a
# broken ls alias from the environment. This has actually
# happened. Such a system could not be considered "sane".
AC_MSG_ERROR([ls -t appears to fail. Make sure there is not a broken
alias in your environment])
fi
test "$[2]" = conftest.file
)
then
# Ok.
:
else
AC_MSG_ERROR([newly created file is older than distributed files!
Check your system clock])
fi
AC_MSG_RESULT(yes)])
# Copyright (C) 2001, 2003, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# AM_PROG_INSTALL_STRIP
# ---------------------
# One issue with vendor `install' (even GNU) is that you can't
# specify the program used to strip binaries. This is especially
# annoying in cross-compiling environments, where the build's strip
# is unlikely to handle the host's binaries.
# Fortunately install-sh will honor a STRIPPROG variable, so we
# always use install-sh in `make install-strip', and initialize
# STRIPPROG with the value of the STRIP variable (set by the user).
AC_DEFUN([AM_PROG_INSTALL_STRIP],
[AC_REQUIRE([AM_PROG_INSTALL_SH])dnl
# Installed binaries are usually stripped using `strip' when the user
# run `make install-strip'. However `strip' might not be the right
# tool to use in cross-compilation environments, therefore Automake
# will honor the `STRIP' environment variable to overrule this program.
dnl Don't test for $cross_compiling = yes, because it might be `maybe'.
if test "$cross_compiling" != no; then
AC_CHECK_TOOL([STRIP], [strip], :)
fi
INSTALL_STRIP_PROGRAM="\${SHELL} \$(install_sh) -c -s"
AC_SUBST([INSTALL_STRIP_PROGRAM])])
# Check how to create a tarball. -*- Autoconf -*-
# Copyright (C) 2004, 2005 Free Software Foundation, Inc.
#
# This file is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# serial 2
# _AM_PROG_TAR(FORMAT)
# --------------------
# Check how to create a tarball in format FORMAT.
# FORMAT should be one of `v7', `ustar', or `pax'.
#
# Substitute a variable $(am__tar) that is a command
# writing to stdout a FORMAT-tarball containing the directory
# $tardir.
# tardir=directory && $(am__tar) > result.tar
#
# Substitute a variable $(am__untar) that extract such
# a tarball read from stdin.
# $(am__untar) < result.tar
AC_DEFUN([_AM_PROG_TAR],
[# Always define AMTAR for backward compatibility.
AM_MISSING_PROG([AMTAR], [tar])
m4_if([$1], [v7],
[am__tar='${AMTAR} chof - "$$tardir"'; am__untar='${AMTAR} xf -'],
[m4_case([$1], [ustar],, [pax],,
[m4_fatal([Unknown tar format])])
AC_MSG_CHECKING([how to create a $1 tar archive])
# Loop over all known methods to create a tar archive until one works.
_am_tools='gnutar m4_if([$1], [ustar], [plaintar]) pax cpio none'
_am_tools=${am_cv_prog_tar_$1-$_am_tools}
# Do not fold the above two line into one, because Tru64 sh and
# Solaris sh will not grok spaces in the rhs of `-'.
for _am_tool in $_am_tools
do
case $_am_tool in
gnutar)
for _am_tar in tar gnutar gtar;
do
AM_RUN_LOG([$_am_tar --version]) && break
done
am__tar="$_am_tar --format=m4_if([$1], [pax], [posix], [$1]) -chf - "'"$$tardir"'
am__tar_="$_am_tar --format=m4_if([$1], [pax], [posix], [$1]) -chf - "'"$tardir"'
am__untar="$_am_tar -xf -"
;;
plaintar)
# Must skip GNU tar: if it does not support --format= it doesn't create
# ustar tarball either.
(tar --version) >/dev/null 2>&1 && continue
am__tar='tar chf - "$$tardir"'
am__tar_='tar chf - "$tardir"'
am__untar='tar xf -'
;;
pax)
am__tar='pax -L -x $1 -w "$$tardir"'
am__tar_='pax -L -x $1 -w "$tardir"'
am__untar='pax -r'
;;
cpio)
am__tar='find "$$tardir" -print | cpio -o -H $1 -L'
am__tar_='find "$tardir" -print | cpio -o -H $1 -L'
am__untar='cpio -i -H $1 -d'
;;
none)
am__tar=false
am__tar_=false
am__untar=false
;;
esac
# If the value was cached, stop now. We just wanted to have am__tar
# and am__untar set.
test -n "${am_cv_prog_tar_$1}" && break
# tar/untar a dummy directory, and stop if the command works
rm -rf conftest.dir
mkdir conftest.dir
echo GrepMe > conftest.dir/file
AM_RUN_LOG([tardir=conftest.dir && eval $am__tar_ >conftest.tar])
rm -rf conftest.dir
if test -s conftest.tar; then
AM_RUN_LOG([$am__untar <conftest.tar])
grep GrepMe conftest.dir/file >/dev/null 2>&1 && break
fi
done
rm -rf conftest.dir
AC_CACHE_VAL([am_cv_prog_tar_$1], [am_cv_prog_tar_$1=$_am_tool])
AC_MSG_RESULT([$am_cv_prog_tar_$1])])
AC_SUBST([am__tar])
AC_SUBST([am__untar])
]) # _AM_PROG_TAR
m4_include([acinclude.m4])

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

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

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

@ -0,0 +1,11 @@
#MIN_CONFIG(3.2)
CXXFLAGS="$CXXFLAGS $KDE_DEFAULT_CXXFLAGS"
if test "$build_arts" = "yes"; then
AC_DEFINE(USE_ARTS, 1, [If we use arts volume])
LIB_ARTS="-lartskde"
AC_SUBST(LIB_ARTS)
fi
KDE_INIT_DOXYGEN([The API Reference], [Version $VERSION])

@ -0,0 +1 @@
SUBDIRS = $(AUTODIRS)

@ -0,0 +1,2 @@
KDE_LANG = da
KDE_DOCS = filelight

@ -0,0 +1,981 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Danish "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>&filelight;-håndbogen</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
&erik.kjaer.pedersen.role;
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; viser rekursiv information om diskforbrug, i en stor en grafisk version af kommandolinjeværktøjet du. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>diskforbrug</keyword>
<keyword
>statistik</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Indledning</title>
<screenshot>
<screeninfo
>Skærmaftryk af Filelight</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skærmaftryk</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight; lader dig hurtigt forstå nøjagtigt hvordan din diskplads bruges ved at repræsentere filsystemet grafisk som et sæt koncentriske cirkelsegmenter. Du kan bruge det til at lokalisere samlinger af diskbrug og håndtere disse områder med Konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Indstil &filelight;</title>
<para
>&filelight;s opsætningsdialog har to faneblade til at indstille &filelight;s tilvalg. De to fanebladene er <guimenuitem
>Skanning</guimenuitem
> og <guimenuitem
>Udseende</guimenuitem
>. Nedenfor findes en beskrivelse af indstillingsfanebladene. &filelight;s indstillingsdialog findes ved at klikke på <menuchoice
><guimenu
>Opsætning</guimenu
> <guimenuitem
>Indstil Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Skanner</title>
<screenshot>
<screeninfo
>Skærmaftryk af skanning</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skærmaftryk</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Skanningsfanebladet lader dig indstille hvordan &filelight; gennemsøger mapper. <guimenuitem
>Skan ikke følgende mapper</guimenuitem
> bruges for til at udelukke visse mapper fra skanningen. Dette er meget nyttigt for at springe over mapper som du måske ikke har rettigheder til at læse, eller mapper som er en del af et virtuelt filsystem, såsom /proc. Klik på knappen <guibutton
>Tilføj...</guibutton
> for at tilføje en mappe til listen. Det viser en dialog hvor du kan vælge mappen du vil have i en trævisning. For at fjerne en mappe, markeres den du vil fjerne blot, og der klikkes på knappen <guibutton
>Fjern</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Udseende</title>
<screenshot>
<screeninfo
>Skærmaftryk af Udseende</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skærmaftryk</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Fanebladet <guimenuitem
>Udseende</guimenuitem
> lader dig indstille hvordan &filelight; ser ud.</para>
<para
>Afsnittet <guimenuitem
>Farvesammensætning</guimenuitem
> bruges til at vælge en farvesammensætning for &filelight;. Farvesammensætningerne er Regnbue, KDE's farver og Høj kontrast. Der er også en skyder, <guimenuitem
>Kontrast</guimenuitem
>, til at justere segmenternes kontrast, så de er lettere at se.</para>
<para
>Afkrydsningsfeltet <guimenuitem
>Brug antialias</guimenuitem
> bruges for at aktivere brug af antialias i &filelight;s visning. At markere dette gør at segmenterne får et meget renere udseende.</para>
<para
>Afkrydsningsfeltet <guimenuitem
>Variér tegnstørrelse for navne</guimenuitem
> er nyttigt når du har filer eller mapper med lange navne. Dette mindsker skrifttypens størrelse for at lade den passe bedre ind i visningen. Når dette er aktiveret, bliver spinfeltet <guimenuitem
>Minimal tegnstørrelse:</guimenuitem
> tilgængelig for at vælge den mindste tegnstørrelse der skal skaleres til</para>
<para
>Tilvalget <guimenuitem
>Vis små filer</guimenuitem
> er normalt deaktiveret eftersom små filer sædvanligvis gør &filelight;s visning rodet. Aktivér dette hvis du ønsker at små filer skal indgå i &filelight;s visning.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Brug &filelight;</title>
<sect1 id="starting">
<title
>Start &filelight;</title>
<para
>&filelight; kan startes fra K-menuen eller fra kommandolinjen.</para>
<sect2 id="starting-from-the-menu">
<title
>Fra K-menuen</title>
<para
>Åbn &kde;'s programmenu ved at klikke på ikonen med <guiicon
>stort K</guiicon
> i panelet. Det viser <guimenu
>programmenuen</guimenu
>. Flyt markøren til menupunktet <guimenu
>Tilbehør</guimenu
> i menuen. Vælg <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Fra kommandolinjen</title>
<para
>Du kan starte &filelight; ved at indtaste dets navn på kommandolinjen. Hvis du angiver et mappenavn, som i eksemplet oven, gennemsøges denne mappe. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Skan mapper</title>
<para
>At gennemsøge en mappe viser dens indhold som en filafbildning. Brug menuen Skan for at gennemsøge en mappe, eller skriv en URL direkte i stedlinjen. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Udforskning af filafbildninger</title>
<para
>Så snart en søgning er færdig vises en filafbildning som svarer til mapperne som du gennemsøgte. Filafbildningen er en serie cirkelsegmenter som ekspanderes fra centrum. Stærkt farvede segmenter er mapper, mens grå segment er filer. Segmenter har en størrelse som er proportionel med deres filstørrelse. Segmenter kan være hierarkiske, altså er for eksempel /home/mxcl et niveau udad og indenfor grænserne for segmentet som repræsenterer /home. Segmenter har navne, og at holde musen stille over et segment giver mere information om segmentet og underliggende segmenter. </para>
<screenshot>
<screeninfo
>Skærmaftryk af filafbildning</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skærmaftryk</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Du kan åbne mapper med Konqueror eller Konsole i segmentets sammenhængsafhængige menu. At klikke med den midterste knappen åbner filer ifølge Mime-type, så billeder åbnes med Kuickshow. Du kan højreklikke i den centrale cirkel for at vise en sammenhængsafhængig menu for mappen som bliver gennemsøgt. At venstreklikke på segmenter gencentrerer billederne i dette segment. </para>
<para
>Hvis du vil forbedre dokumentationen, modtager jeg gerne rettelser. Tak. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Menu og kommandoreference</title>
<sect1 id="scan_menu">
<title
>Menuen Skan</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>O</keycap
></keycombo
> </shortcut
> <guimenu
>Skan</guimenu
> <guimenuitem
>Skan mappe...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Tilbyder en dialog for mappevalg så du kan vælge en mappe at gennemsøge.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
> <guimenu
>Skan</guimenu
> <guimenuitem
>Skan hjemmemappe</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter en skanning i brugerens hjemmemappe.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Skan</guimenu
> <guimenuitem
>Skan rodmappe</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter en søgning i rodmappen.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Skan</guimenu
> <guimenuitem
>Nylige skanninger</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Sørger for en liste med de senest skannede mapper, hvilket tillader hurtig adgang til disse mapper.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Skan</guimenu
> <guimenuitem
>Skan igen</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter en ny gennemsøgning af nuværende arbejdsmappe. Dette er nyttigt når ændringer er sket i filsystemet.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Skan</guimenu
> <guimenuitem
>Stop</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Stopper nuværende søgning.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Q</keycap
></keycombo
> </shortcut
> <guimenu
>Skan</guimenu
> <guimenuitem
>Afslut</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Afslutter &filelight;</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>Kør-menuen</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Op</keycap
></keycombo
> </shortcut
> <guimenu
>Kør</guimenu
> <guimenuitem
>Op</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Går et skridt opad i filsystemet.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Venstre</keycap
></keycombo
> </shortcut
> <guimenu
>Kør</guimenu
> <guimenuitem
>Tilbage</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Går et skridt tilbage når du bladrer i filsystemet.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Højre</keycap
></keycombo
> </shortcut
> <guimenu
>Gå</guimenu
> <guimenuitem
>Fremad</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Går et skridt fremad når du bladrer i filsystemet.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>Opsætningsmenuen</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Opsætning</guimenu
> <guisubmenu
>Værktøjslinjer</guisubmenu
> <guimenuitem
>Vis hovedværktøjslinje</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Aktiverer eller deaktiverer programmets hovedværktøjslinje.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Opsætning</guimenu
> <guisubmenu
>Værktøjslinjer</guisubmenu
> <guimenuitem
>Vis stedværktøjslinje</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Aktiverer eller deaktiverer stedværktøjslinjen.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Opsætning</guimenu
> <guimenuitem
>Indstil genveje...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Lader dig indstille &filelight;s genveje.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Opsætning</guimenu
> <guimenuitem
>Indstil værktøjslinjer...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Lader dig indstille &filelight;s værktøjslinjestilvalg.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Opsætning</guimenu
> <guimenuitem
>Indstil Filelight...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter &filelight;s indstillingsdialog.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>Hjælpemenuen</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Hjælp</guimenu
> <guimenuitem
>Filelight-håndbogen</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Åbner dette hjælpedokument.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Skift</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Hjælp</guimenu
> <guimenuitem
>Hvad er dette?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Aktiverer musemarkøren "Hvad er dette?" som lader dig klikke på et objekt for at få et "Hvad er dette?" værktøjsvink.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Hjælp</guimenu
> <guimenuitem
>Rapportér fejl...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Start dialogvinduet med fejlrapporteringsværktøjet.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Hjælp</guimenu
> <guimenuitem
>Om Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter dialogvinduet Om &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Hjælp</guimenu
> <guimenuitem
>Om KDE</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Starter dialogvinduet Om &kde;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Medvirkende og licens</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Program ophavsret 2003 Max B. Howell <email
>max.howell@methylblue.com</email
></para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Dokumentation</title>
<para
>Dokumentation ophavsret 2003 Max B. Howell <email
>max.howell@methylblue.com</email
> </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Installation</title>
<sect1 id="getting-filelight">
<title
>Hvordan får man fat i &filelight;</title>
<para
>:&filelight; er endnu ikke en del af KDE-projektet. Det findes på: <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Kompilering og installation</title>
<para
>For at kompilere og installere &filelight; på dit system, skrives følgende i basismappen for &filelight;s distribution: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>Eftersom &filelight; bruger autoconf og automake, burde du ikke have nogen problemer med at kompilere den. Skulle du støde på problemer, så rapportér dem gerne til filelight@methylblue.com eller til &filelight;s forum.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

@ -0,0 +1,2 @@
KDE_LANG = es
KDE_DOCS = filelight

Binary file not shown.

Binary file not shown.

Binary file not shown.

@ -0,0 +1,995 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Spanish "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>El manual de &filelight;</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
> <firstname
>Santiago</firstname
> <surname
>Fernández Sancho</surname
> <affiliation
><address
><email
>santi@est.unileon.es</email
></address
></affiliation
> <contrib
>Traductor</contrib
> </othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; muestra información sobre la utilización del disco de forma recursiva, como una versión gráfica de la orden de línea de órdenes, du. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>uso del disco</keyword>
<keyword
>estadísticas</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Introducción</title>
<screenshot>
<screeninfo
>Captura de pantalla de Filelight</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Captura de pantalla</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight; le permite entender rápidamente en qué se está utilizando su espacio de disco a través de una representación gráfica del sistema de archivos como un conjunto de anillos concéntricos segmentados. Puede utilizarla para localizar puntos conflictivos en el uso del disco y manipular estas áreas utilizando konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Configurar &filelight;</title>
<para
>El diálogo de preferencias de &filelight; tiene dos pestañas para configurar las opciones de &filelight;. Las dos pestañas son <guimenuitem
>Explorar</guimenuitem
> y <guimenuitem
>Apariencia</guimenuitem
>. A continuación se muestra una descripción de la pestaña de preferencias. El diálogo de preferencias de &filelight; puede encontrarse pulsando <menuchoice
><guimenu
>Preferencias</guimenu
><guimenuitem
>Configurar Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Exploración</title>
<screenshot>
<screeninfo
>Captura de la pantalla de exploración</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Captura de pantalla</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>La pestaña exploración le permite configurar cómo &filelight; esplora los directorios. <guimenuitem
>No explorar estos directorios</guimenuitem
> se utiliza para excluir determinados directorios de la exploración. Esta opción es muy práctica para saltar directorios para los que no se tiene permisos de lectura, o directorios que forman parte del sistema de archivo virtual, como /proc. Para añadir un directorio a la lista, pulse el botón <guibutton
>Añadir...</guibutton
>, que iniciará el diálogo en el que podrá seleccionar el directorio de su elección desde la vista de árbol. Para eliminar un directorio selecciónelo y pulse el botón <guibutton
>Eliminar</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Apariencia</title>
<screenshot>
<screeninfo
>Captura de pantalla de la apariencia</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Captura de pantalla</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>La pestaña <guimenuitem
>Apariencia</guimenuitem
> le permite configurar el aspecto de &filelight;.</para>
<para
>La sección <guimenuitem
>Esquema</guimenuitem
> se utiliza para seleccionar un esquema de color para &filelight;. Los esquemas de color son arco iris, colores de KDE y alto contraste. También podemos encontrar el deslizador <guimenuitem
>Contraste</guimenuitem
> para ajustar el contraste de los segmentos del anillo para una visualización sencilla.</para>
<para
>La casilla <guimenuitem
>Utilizar suavizado</guimenuitem
> se utiliza para activar el uso del suavizado en la vista de &filelight;. Si está seleccionada, esta opción hace que los segmentos de los anillos tengan un aspecto mucho más limpio.</para>
<para
>La casilla <guimenuitem
>Variar los tamaños de los tipos de letra de las etiquetas</guimenuitem
> es práctica cuando tiene archivos o directorios con nombres largos para ajustarlos mejor en la vista. Cuando esta opción está marcada, se activará la edición del <guimenuitem
>Tamaño mínimo del tipo de letra</guimenuitem
> para seleccionar el tipo de letra más pequeña a la que realizar el escalado.</para>
<para
>La opción <guimenuitem
>Mostrar los archivos pequeños</guimenuitem
> está desactivada de forma predeterminada para evitar que la vista de &filelight; esté desordenada. Active esta opción si desea incluír sus archivos pequeños en la vista de &filelight;.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Utilización de &filelight;</title>
<sect1 id="starting">
<title
>Inicio de &filelight;</title>
<para
>&filelight; puede iniciarse desde el menú K, o desde la línea de órdenes.</para>
<sect2 id="starting-from-the-menu">
<title
>Desde el menú K</title>
<para
>Abre el menú de programas de &kde; pulsando en el icono con la <guiicon
>gran K</guiicon
> en su panel. Aparecerá el <guimenu
>menú de programas</guimenu
>. Muévase hasta el elemento de menú <guimenu
>Utilidades</guimenu
>. Seleccione <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Desde la línea de órdenes</title>
<para
>Puede iniciar &filelight; tecleando su nombre en la línea de órdenes. Si le da un nombre de directorio, como en el ejemplo siguiente, explorará este directorio. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Exploración de directorios</title>
<para
>Explorar un directorio muestra su contenido como un mapa de archivos. Para explorar un directorio, utilice el menú explorar, o teclee una url en la barra de dirección. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Exploración del mapa de archivos</title>
<para
>Una vez que la exploración se haya completado aparecerá un mapa de archivos que representa el directorio explorado. El mapa de archivos está formado por una serie de anillos segmentados que se expanden desde el centro. Los segmentos con colores brillantes son directorio, los grises son archivos. Los segmentos se dimensionan con un tamaño proporcional al tamaño de los archivos. Los segmentos se anidarán, así por ejemplo, /home/mxcl será un nivel externo vinculado al segmento que representa a home. Los segmentos se etiquetan y al mantener el ratón sobre los segmentos aparecerán más detalles de este segmento y de sus segmentos hijo. </para>
<screenshot>
<screeninfo
>Captura de pantalla del mapa de archivos</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Captura de pantalla</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Puede abrir un directorio con Konqueror o Konsole utilizando el menú contextual para este segmento. Pulsar el botón central abrirá el archivo de acuerdo con su tipo mime, así, las imágenes se abrirán con Kuickshow. Puede pulsar el botón derecho en el círculo central para obtener un menú contextual para el directorio explorado. Pulsar el botón izquierdo en el segmento, volverá a centrar el mapa en este segmento. </para>
<para
>Si desea, mejorar la documentación, estaré encantado de aceptar parches :) gracias. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Menú y referencia de órdenes</title>
<sect1 id="scan_menu">
<title
>El menú Explorar</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>o</keycap
></keycombo
> </shortcut
> <guimenu
>Explorar</guimenu
> <guimenuitem
>Explorar directorio..</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ofrece un diálogo de selección de directorio de forma que pueda seleccionar el directorio a explorar.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Inicio</keycap
></keycombo
> </shortcut
> <guimenu
>Explorar</guimenu
> <guimenuitem
>Explorar el directorio personal</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia la exploración del directorio personal del usuario.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Explorar</guimenu
> <guimenuitem
>Explorar el directorio raíz</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia la exploración del directorio raíz.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Explorar</guimenu
> <guimenuitem
>Exploraciones recientes</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Proporciona una lista de los directorios recientemente explorados permitiendo un acceso rápido a estos directorios.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Exploración</guimenu
> <guimenuitem
>Re-explorar</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia una nueva exploración del directorio de trabajo actual, lo que es práctico cuando se hacen cambios en el sistema de archivos.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Explorar</guimenu
> <guimenuitem
>Detener</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Detiene la exploración actual.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>q</keycap
></keycombo
> </shortcut
> <guimenu
>Explorar</guimenu
> <guimenuitem
>Salir</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Sale de &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>El menú Ir</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Arriba</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Arriba</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Se mueve hacia arriba en el sistema de archivos.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Izquierda</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Atrás</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Se desplaza un paso hacia atrás en la navegación de su sistema de archivos.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Derecha</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Adelante</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Se desplaza un paso hacia delante en la navegación de su sistema de archivos.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>El menú Preferencias</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Preferencias</guimenu
> <guisubmenu
>Barra de herramientas</guisubmenu
> <guimenuitem
>Barra de herramientas principal</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa o desactiva la barra de herramientas principal de la aplicación.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Preferencias</guimenu
> <guisubmenu
>Barra de herramientas</guisubmenu
> <guimenuitem
>Barra de dirección</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa o desactiva la barra de herramientas de dirección.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Preferencias</guimenu
> <guimenuitem
>Configurar accesos rápidos...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Le permite configurar los accesos rápidos de &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Preferencias</guimenu
> <guimenuitem
>Configurar barra de herramientas...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Le permite configurar las opciones de la barra de herramientas de &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Preferencias</guimenu
> <guimenuitem
>Configurar Filelight...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia el diálogo configurar de &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>El menú ayuda</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Ayuda</guimenu
> <guimenuitem
>Manual de Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Abre este documento de ayuda.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Mayúsculas</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Ayuda</guimenu
> <guimenuitem
>¿Qué es esto?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa el cursor del ratón «¿Qué es esto?» para permitirle pulsar sobre un objeto para obtener la información «¿Qué es esto?».</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ayuda</guimenu
> <guimenuitem
>Informar de fallo...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia la herramienta de informe de fallos de la ventana del diálogo.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ayuda</guimenu
> <guimenuitem
>Acerca de Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia la ventana del diálogo Acerca de &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ayuda</guimenu
> <guimenuitem
>Acerca de KDE</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia la ventana de diálogo Acerca de &kde;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Créditos y licencia</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Derechos de autor del programa. 2003. Max B. Howell <email
>max.howell@methylblue.com</email
>.</para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Documentación</title>
<para
>Derechos de autor de la documentación. 2003. Max B. Howell <email
>max.howell@methylblue.com</email
>. </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Instalación</title>
<sect1 id="getting-filelight">
<title
>Cómo obtener &filelight;</title>
<para
>&filelight; no forma todavía parte del proyecto KDE, se puede encontrar en: <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Compilación e instalación</title>
<para
>Para compilar e instalar &filelight; en su sistema, teclee lo siguiente en el directorio base de la distribución de &filelight;: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>Como &filelight; utiliza autoconf y automake no debería tener problemas para compilarlo. Si tiene problemas de ejecución informe de ello a filelight@methylblue.com o a los de &filelight;.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

Binary file not shown.

@ -0,0 +1,2 @@
KDE_LANG = et
KDE_DOCS = filelight

@ -0,0 +1,995 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Estonian "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>&filelight;i käsiraamat</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
><firstname
>Marek</firstname
><surname
>Laane</surname
><affiliation
><address
><email
>bald@starman.ee</email
></address
></affiliation
><contrib
>Tõlge eesti keelde</contrib
></othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; näitab rekursiivselt kettakasutuse infot, olles sisuliselt käsureatööriista du graafiline versioon. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>kettakasutus</keyword>
<keyword
>statistika</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Sissejuhatus</title>
<screenshot>
<screeninfo
>Filelighti pilt</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Pilt</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight;i abil saab hõlpsasti ülevaate oma kettaruumi jagunemisest. Rakendus näitab failisüsteemi graafiliselt kontsentriliste lõigustatud ringidena. Nii saad kergesti tuvastada suurimad ketast kasutavad failid või kataloogid ja seejärel soovi korral nendega midagi Konqueroris ette võtta. </para>
</chapter>
<chapter id="configuring">
<title
>&filelight;i seadistamine</title>
<para
>&filelight;i seadistustedialoogis on &filelight;i seadistamiseks kaks kaarti: <guimenuitem
>Skaneerimine</guimenuitem
> ja <guimenuitem
>Välimus</guimenuitem
>. Alljärgnevalt kirjeldame mõlemat kaarti. &filelight;i seadistustedialoogi saab avada menüükäsuga <menuchoice
><guimenu
>Seadistused</guimenu
><guimenuitem
>Filelighti seadistamine</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Skaneerimine</title>
<screenshot>
<screeninfo
>Skaneerimise pilt</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Pilt</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Skaneerimiskaardil saab määrata, kuidas &filelight; katalooge skaneerib. Kastis <guimenuitem
>Ei skaneerita katalooge</guimenuitem
> saab valida kataloogid, mis jäetakse skaneerimisel arvestamata. See on üsna kasulik kataloogide korral, milles sul puudub lugemisõigus, või kataloogide puhul, mis kuuluvad virtuaalsesse failisüsteemi (näiteks /proc). Kataloogi lisamiseks nimekirja klõpsa nupule <guibutton
>Lisa...</guibutton
> See avab dialoogi, kus saad kataloogipuust valida vajaliku kataloogi. Kataloogi eemaldamiseks vali see nimekirjast ja klõpsa nupule <guibutton
>Eemalda</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Välimus</title>
<screenshot>
<screeninfo
>Välimuse pilt</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Pilt</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Kaardil <guimenuitem
>Välimus</guimenuitem
> saab kohandada &filelight;i väljanägemist.</para>
<para
>Sektsioonis <guimenuitem
>Skeem</guimenuitem
> saab valida &filelight;i värviskeemi. Valikuteks on vikerkaar, KDE värvid ja kõrge kontrast. Liuguriga <guimenuitem
>Kontrast</guimenuitem
> saab muuta lõikude kontrasti, et need paremini näha oleks.</para>
<para
>Märkekastiga <guimenuitem
>Antialiase kasutamine</guimenuitem
> saab lubada või keelata antialiase kasutamise &filelight;i aknas. Märkimise korral on lõigud üldiselt märksa selgemini näha.</para>
<para
>Kasti <guimenuitem
>Muutuvad pealdisefondi suurused</guimenuitem
> märkimisest on kasu eriti siis, kui sul pikkade nimetustega faile või katalooge. Selle märkimisel muudetakse fondi suurust, et sellised nimetused paremini ära mahuksid. Sisselülitamisel saab kasutada ka kerimiskasti <guimenuitem
>Minimaalne fondisuurus</guimenuitem
>, mis võimaldab valida väikseima kasutatava fondisuuruse.</para>
<para
><guimenuitem
>Väikeste failide näitamine</guimenuitem
> on vaikimisi keelatud, sest need kipuvad enamasti &filelight;i vaate liiga kirjuks muutma. Kui aga soovid, et &filelight; näitaks ka väikseid faile, lülita see sisse.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>&filelight;i kasutamine</title>
<sect1 id="starting">
<title
>&filelight;i käivitamine</title>
<para
>&filelight;i võib käivitada K-menüüst või käsurealt.</para>
<sect2 id="starting-from-the-menu">
<title
>K-menüüst</title>
<para
>Ava &kde; programmide menüü klõpsuga paneeli paiknevale <guiicon
>suure K</guiicon
> ikoonile. See avab <guimenu
>programmide menüü</guimenu
>. Vii hiir kirje <guimenu
>Utiliidid</guimenu
> peale ja vali avanevast alammenüüst <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Käsurealt</title>
<para
>&filelight;i saab käivitada lihtsalt selle nime käsureal andes. Kui lisada ka kataloogi nimi, nagu alltoodud näites, hakkab rakendus kohe skaneerima määratud kataloogi. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Kataloogide skaneerimine</title>
<para
>Kataloogi skaneerimisel näidatakse selle sisu failikaardina. Kataloogi skaneerimiseks kasuta menüüd Skaneerimine või kirjuta vajalik URL otse asukohareale. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Failikaardi uurimine</title>
<para
>Kui skaneerimine on lõppenud, näidatakse skaneeritud kataloogi failikaardina. See kujutab endast mitut kontsentrilist lõikudeks jagatud ringi. Värvilised lõigud on kataloogid, hallid lõigud failid. Lõikude suurus vastab failide suurusele. Lõigud võivad olla pesastatud, see tähendab, et näiteks /home/marek on üks tase väljapool lõiku /home, kuid selle raames. Lõikudele on lisatud nimi ning hiire viimisel lõigu kohale näed antud lõigu ja selle alamlõikude üksikasju. </para>
<screenshot>
<screeninfo
>Failikaardi pilt</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Pilt</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Lõigu kontekstimenüüd kasutades võid avada kataloogid Konqueroris või Konsoolis. Klõps hiire keskmise nupuga avab elemendi vastavalt selle MIME tüübile, nii avatakse näiteks pildid rakenduses Kuickshow. Keskel paiknevale ringile hiire parema nupuga klõpsates avaneb skaneeritud kataloogi kontekstimenüü. Lõigule hiire vasaku nupuga klõpsates luuakse uus failikaart, mille keskmes seisab klõpsatud lõik. </para>
<para
>Kui soovid käsiraamatut paremaks muuta, ootan rõõmuga sinu ettepanekuid ja parandusi. Tänan sind juba ette. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Menüükäskude seletus</title>
<sect1 id="scan_menu">
<title
>Menüü Skaneerimine</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>o</keycap
></keycombo
> </shortcut
><guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Skaneeri kataloogi...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab kataloogi valimise dialoogi, kus saab valida skaneeritava kataloogi.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
><guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Skaneeri kodukataloogi</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Käivitab kasutaja kodukataloogi skaneerimise.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Skaneeri juurkataloogi</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Käivitab juurkataloogi skaneerimise.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Hiljutised skaneeringud</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Näitab hiljuti skaneeritud kataloogide nimekirja, mis võimaldab kiiresti neid vaadata.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Skaneeri uuesti</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Käivitab skaneeritud kataloogi uue skaneerimise, mis on kasulik juhul, kui vahepeal on failisüsteemis midagi muudetud.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Peata</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Peatab käimasoleva skaneerimise.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>q</keycap
></keycombo
> </shortcut
> <guimenu
>Skaneerimine</guimenu
> <guimenuitem
>Välju</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Lõpetab &filelight;i töö.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>Menüü Liikumine</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Nool üles</keycap
></keycombo
> </shortcut
> <guimenu
>Liikumine</guimenu
> <guimenuitem
>Üles</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Liigub failisüsteemis ühe taseme võrra ülespoole.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Nool vasakule</keycap
></keycombo
> </shortcut
> <guimenu
>Liikumine</guimenu
> <guimenuitem
>Tagasi</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Liigub failisüsteemi sirvimise ajaloos ühe sammu tagasi.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Nool paremale</keycap
></keycombo
> </shortcut
> <guimenu
>Liikumine</guimenu
> <guimenuitem
>Edasi</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Liigub failisüsteemi sirvimise ajaloos ühe sammu edasi.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>Menüü Seadistused</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Seadistused</guimenu
> <guisubmenu
>Tööriistaribad</guisubmenu
> <guimenuitem
>Peatööriistariba näitamine</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Lülitab peamise tööriistariba näitamise sisse või välja.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Seadistused</guimenu
> <guisubmenu
>Tööriistaribad</guisubmenu
> <guimenuitem
>Asukohariba näitamine</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Lülitab asukohariba näitamise sisse või välja.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Seadistused</guimenu
> <guimenuitem
>Kiirklahvide seadistamine...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Võimaldab seadistada &filelight;i kiirklahve.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Seadistused</guimenu
> <guimenuitem
>Tööriistaribade seadistamine...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Võimaldab seadistada &filelight;i tööriistaribasid.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Seadistused</guimenu
> <guimenuitem
>Filelighti seadistamine...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab &filelight;i seadistustedialoogi.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>Menüü Abi</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Abi</guimenu
> <guimenuitem
>Filelighti käsiraamat</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab käesoleva käsiraamatu.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Shift</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Abi</guimenu
> <guimenuitem
>Mis see on?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Aktiveerib "Mis see on?" hiirekursori, millega mõnele elemendile klõpsates saab näha "Mis see on?" abiteksti.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Abi</guimenu
> <guimenuitem
>Saada vearaport...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab vearaportide dialoogi.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Abi</guimenu
> <guimenuitem
>Filelighti info</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab &filelight;i infodialoogi.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Abi</guimenu
> <guimenuitem
>KDE info</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avab &kde; infodialoogi.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Autorid ja litsents</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Rakenduse autoriõigus 2003: Max B. Howell <email
>max.howell@methylblue.com</email
></para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Dokumentatsioon</title>
<para
>Dokumentatsiooni autoriõigus 2003: Max B. Howell <email
>max.howell@methylblue.com</email
> </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Paigaldamine</title>
<sect1 id="getting-filelight">
<title
>&filelight;i hankimine</title>
<para
>&filelight; ei kuulu veel KDE projekti, selle leiab aadressilt <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Kompileerimine ja paigaldamine</title>
<para
>&filelight;i kompileerimiseks ja paigaldamiseks anna &filelight;i baaskataloogis järgmised käsud: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>Et &filelight; kasutab autoconf'i ja automake'i, ei tohiks kompileerimisel probleeme esineda. Kui neid siiski tekib, anna neist teada aadressil filelight@methylblue.com või &filelight;i foorumil.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

@ -0,0 +1,2 @@
KDE_DOCS = AUTO
KDE_LANG = en

Binary file not shown.

Binary file not shown.

Binary file not shown.

@ -0,0 +1,613 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application>Filelight</application>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE"><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title>The &filelight; Handbook</title>
<authorgroup>
<author>
<firstname>Max</firstname>
<surname>Howell</surname>
<affiliation>
<address><email>max.howell@methylblue.com</email></address>
</affiliation>
</author>
</authorgroup>
<!-- TRANS:ROLES_OF_TRANSLATORS -->
<copyright>
<year>2003</year>
<holder>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date>03/11/2003</date>
<releaseinfo>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para>
&filelight; displays disk usage information recursively, effectively a graphical version of the command line tool, du.
</para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword>KDE</keyword>
<keyword>Filelight</keyword>
<keyword>du</keyword>
<keyword>disk usage</keyword>
<keyword>statistics</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title>Introduction</title>
<screenshot>
<screeninfo>Filelight Screenshot</screeninfo>
<mediaobject>
<imageobject><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject><phrase>Screenshot</phrase></textobject>
</mediaobject>
</screenshot>
<para>
&filelight; allows you to quickly understand exactly where your diskspace is being used by graphically representing your filesystem as a set of concentric segmented-rings. You can use it to locate hotspots of disk usage and then manipulate those areas using Konqueror.
</para>
</chapter>
<chapter id="configuring">
<title>Configuring &filelight;</title>
<para>The &filelight; settings dialog has two tabs for configuring the &filelight; options. The two tabs are <guimenuitem>Scanning</guimenuitem> and <guimenuitem>Appearance</guimenuitem>. Below is a description of the settings tabs. The &filelight; settings dialog can be found by clicking <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure Filelight</guimenuitem></menuchoice>.</para>
<sect1 id="scanning">
<title>Scanning</title>
<screenshot>
<screeninfo>Scanning Screenshot</screeninfo>
<mediaobject>
<imageobject><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject><phrase>Screenshot</phrase></textobject>
</mediaobject>
</screenshot>
<para>The scanning tab allows you to configure how &filelight; scans directories. The <guimenuitem> Don't scan these directories:</guimenuitem> is used to excluded certain directories from your scan. This option is very useful for skipping directories that you may not have permissions to read, or directories that are part of a virtual filesystem, such as /proc. To add a directory to the list, click the <guibutton>Add...</guibutton> button, this will start a dialog where you can choose the directory of your choice from a tree view. To remove a directory simply select the directory of your choice and click the <guibutton>Remove</guibutton> button.</para>
<!--<madpenguin8>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title>Appearance</title>
<screenshot>
<screeninfo>Appearance Screenshot</screeninfo>
<mediaobject>
<imageobject><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject><phrase>Screenshot</phrase></textobject>
</mediaobject>
</screenshot>
<para>The <guimenuitem>Appearance</guimenuitem> tab allows you to configure the way &filelight; looks.</para>
<para>The <guimenuitem>Scheme</guimenuitem> section is used to choose a color scheme for &filelight;. The color schemes are Rainbow, KDE Colours, and High Contrast. There is also a <guimenuitem>Contrast:</guimenuitem> slider to adjust the contrast of the ring segments for easier viewing.</para>
<para>The <guimenuitem>Use anti-aliasing</guimenuitem> checkbox is used to enable the use of anti-aliasing in the &filelight; view. Selected, this option makes the ring segments have a much cleaner look.</para>
<para>The <guimenuitem>Vary label font sizes</guimenuitem> check box is useful when you have files or directories with long names. This option will change the size of the font to allow it to fit in the view better. When this option is enabled a <guimenuitem>Minimum font size:</guimenuitem> spinbox becomes available for choosing the smallest size font to scale to.</para>
<para>The <guimenuitem>Show small files</guimenuitem> option is disabled by default as small files tend to clutter the &filelight; view. Enable this option if you would like to have your small files included in the &filelight; view.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title>Using &filelight;</title>
<sect1 id="starting">
<title>Starting &filelight;</title>
<para>&filelight; can be started from the K-Menu, or from the command-line</para>
<sect2 id="starting-from-the-menu">
<title>From the K-Menu</title>
<para>
Open the &kde; program menu by clicking on the
<guiicon>big K</guiicon> icon on your
panel. This will raise the <guimenu>program menu</guimenu>. Move your
cursor up the menu to the <guimenu>Utilities</guimenu> menu item. Choose
<guimenuitem>&filelight;</guimenuitem>.
</para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title>From the Command Line</title>
<para>
You can start &filelight; by typing its name on the command line.
If you give it a directory name, as in the example below, it will scan that directory.
</para>
<informalexample>
<screen>
<prompt>%</prompt><userinput><command>filelight</command> <option><replaceable>/home</replaceable></option></userinput>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title>Scanning Directories</title>
<para>
Scanning a directory shows it's contents as a filemap. To scan a directory, use the scan menu, or type a url straight into the location bar.
</para>
<!--<sect2 id="scan-home"><para>1</para></sect2>
<sect2 id="scan-root"><para>1</para></sect2>
<sect2 id="scan-directory"><para>1</para></sect2>
<sect2 id="scan-recent"><para>1</para></sect2>-->
</sect1>
<sect1 id="exploring-filemaps">
<title>Exploring Filemaps</title>
<para>
Once a scan has completed you will be presented with a filemap that represents the directory you scanned. The filemap is a series of segmented-rings that expand from the center. Brightly coloured segments are directories, grey segments are files. Segments are sized in proportion to their filesize. Segments can be nested, so for example, /home/mxcl will be one level outwards and within the bounds of the segment representing /home. Segments are labeled and hovering the mouse over segments will give you more details of that segment and its child segments.
</para>
<screenshot>
<screeninfo>Filemap Screenshot</screeninfo>
<mediaobject>
<imageobject><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject><phrase>Screenshot</phrase></textobject>
</mediaobject>
</screenshot>
<para>
You can open directories with Konqueror or Konsole using the context menu for that segment. Middle clicks open files by mimetype, so images with Kuickshow. You can right click the central circle to get a context menu for the scanned directory. Left clicking segments will re-center the map on that segment.
</para>
<para>
If you want to improve the documentation, I'll happily accept patches :) Thanks.
</para>
<!--<sect2 id="scan-home"><para>1</para></sect2>
<sect2 id="scan-root"><para>1</para></sect2>
<sect2 id="scan-directory"><para>1</para></sect2>
<sect2 id="scan-recent"><para>1</para></sect2>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para>-->
<chapter id="commands">
<title>Menu and Command Reference</title>
<sect1 id="scan_menu">
<title>The Scan Menu</title>
<variablelist>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>o</keycap></keycombo>
</shortcut>
<guimenu>Scan</guimenu>
<guimenuitem>Scan Directory..</guimenuitem>
</menuchoice></term>
<listitem><para><action>Offers a directory selection dialog so you can choose a directory to scan.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>Home</keycap></keycombo>
</shortcut>
<guimenu>Scan</guimenu>
<guimenuitem>Scan Home Directory</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts a scan of the user's home directory.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Scan</guimenu>
<guimenuitem>Scan Root Directory</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts a scan of the root directory.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Scan</guimenu>
<guimenuitem>Recent Scans</guimenuitem>
</menuchoice></term>
<listitem><para><action>Provides a list of your most recent scanned directories allowing quick access to these directories.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycap>F5</keycap>
</shortcut>
<guimenu>Scan</guimenu>
<guimenuitem>Rescan</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts a new scan of the current working directory, this is useful when changes have been made to the filesystem.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycap>Esc</keycap>
</shortcut>
<guimenu>Scan</guimenu>
<guimenuitem>Stop</guimenuitem>
</menuchoice></term>
<listitem><para><action>Stops the current scan.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>q</keycap></keycombo>
</shortcut>
<guimenu>Scan</guimenu>
<guimenuitem>Quit</guimenuitem>
</menuchoice></term>
<listitem><para><action>Quits &filelight;.</action></para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title>The Go Menu</title>
<variablelist>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Alt</keycap><keycap>Up</keycap></keycombo>
</shortcut>
<guimenu>Go</guimenu>
<guimenuitem>Up</guimenuitem>
</menuchoice></term>
<listitem><para><action>Moves you up once in the filesystem.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Alt</keycap><keycap>Left</keycap></keycombo>
</shortcut>
<guimenu>Go</guimenu>
<guimenuitem>Back</guimenuitem>
</menuchoice></term>
<listitem><para><action>Moves you one step back in your browsing of the filesystem.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Alt</keycap><keycap>Right</keycap></keycombo>
</shortcut>
<guimenu>Go</guimenu>
<guimenuitem>Forward</guimenuitem>
</menuchoice></term>
<listitem><para><action>Moves you one step forward in your browsing of the filesystem.</action></para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title>The Settings Menu</title>
<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guisubmenu>Toolbars</guisubmenu>
<guimenuitem>Show Main Toolbar</guimenuitem>
</menuchoice></term>
<listitem><para><action>Enables or disable the main application toolbar.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guisubmenu>Toolbars</guisubmenu>
<guimenuitem>Show Location Toolbar</guimenuitem>
</menuchoice></term>
<listitem><para><action>Enables or disable the location toolbar.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guimenuitem>Configure Shortcuts...</guimenuitem>
</menuchoice></term>
<listitem><para><action>Allows you to configure the &filelight; shortcuts.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guimenuitem>Configure Toolbars...</guimenuitem>
</menuchoice></term>
<listitem><para><action>Allows you to configure the &filelight; toolbar options.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guimenuitem>Configure Filelight...</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts the Configure &filelight; dialog.</action></para></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title>The Help Menu</title>
<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Help</guimenu>
<guimenuitem>Filelight Handbook</guimenuitem>
</menuchoice></term>
<listitem><para><action>Opens this help document.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Shift</keycap><keycap>F1</keycap></keycombo>
</shortcut>
<guimenu>Help</guimenu>
<guimenuitem>What's This?</guimenuitem>
</menuchoice></term>
<listitem><para><action>Activates the "What's This?" mouse cursor allowing you to click an object to get a "What's this?" tooltip.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Help</guimenu>
<guimenuitem>Report Bug...</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts the bug report tool dialog window.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Help</guimenu>
<guimenuitem>About Filelight</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts the About &filelight; dialog window.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Help</guimenu>
<guimenuitem>About KDE</guimenuitem>
</menuchoice></term>
<listitem><para><action>Starts the About &kde; dialog window.</action></para></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para>You silly goose! Check out the <link linkend="commands">Commands
Section</link> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Why can't I twiddle my documents?</para>
</question>
<answer>
<para>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title>Credits and License</title>
<sect1 id="kapp">
<title>&filelight;</title>
<para>Program copyright 2003 Max B. Howell <email>max.howell@methylblue.com</email></para>
&underGPL;
</sect1>
<sect1 id="Documentation">
<title>Documentation</title>
<para>
Documentation copyright 2003 Max B. Howell <email>max.howell@methylblue.com</email>
</para>
&underFDL;
</sect1>
</chapter>
<appendix id="installation">
<title>Installation</title>
<sect1 id="getting-filelight">
<title>How to obtain &filelight;</title>
<para>
&filelight; is not yet part of the KDE project, it can be found at:
<ulink url="http://www.methylblue.com/filelight/">http://www.methylblue.com/filelight/</ulink>.
</para>
</sect1>
<sect1 id="compilation">
<title>Compilation and Installation</title>
<para>
In order to compile and install &filelight; on your system, type the following in the base directory of the &filelight; distribution:
<screen width="40">
<prompt>%</prompt> <userinput>./configure --prefix=`kde-config --prefix`</userinput>
<prompt>%</prompt> <userinput>make</userinput>
<prompt>%</prompt> <userinput>make install</userinput>
</screen>
</para>
<para>Since &filelight; uses autoconf and automake you should have not trouble compiling it. Should you run into problems please report them to filelight@methylblue.com or the &filelight; Forums.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

Binary file not shown.

@ -0,0 +1,2 @@
KDE_LANG = it
KDE_DOCS = filelight

Binary file not shown.

Binary file not shown.

@ -0,0 +1,995 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Italian "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>Manuale di &filelight;</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
><firstname
>Federico</firstname
><surname
>Zenith</surname
><affiliation
><address
><email
>zenith@chemeng.ntnu.no</email
></address
></affiliation
><contrib
>Traduzione della documentazione</contrib
></othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; visualizza le informazioni sull'uso del disco ricorsivamente, è di fatto una versione grafica dello strumendo da riga di comando, du. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>uso del disco</keyword>
<keyword
>statistica</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Introduzione</title>
<screenshot>
<screeninfo
>Schermata di Filelight</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Schermata</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight; ti permette di capire al volo esattamente dove viene usato il tuo spazio su disco rappresentando graficamente il tuo file system come un insieme di anelli segmentati concentrici. Puoi usarlo per localizzare punti di alto uso del disco e manipolare quelle aree usando Konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Configurare &filelight;</title>
<para
>La finestra delle impostazioni di &filelight; ha due schede per configurare le opzioni di &filelight;. Le due schede sono <guimenuitem
>Scansione</guimenuitem
> e <guimenuitem
>Aspetto</guimenuitem
>. Sotto c'è una descrizione delle schede delle impostazioni. La finestra delle impostazioni di &filelight; si trova facendo clic su <menuchoice
><guimenu
>Impostazioni</guimenu
> <guimenuitem
>Configura Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Scansione</title>
<screenshot>
<screeninfo
>Schermata di Scansione</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Schermata</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>La scheda Scansione ti permette di configurare come &filelight; scansiona le cartelle. La casella <guimenuitem
>Non scansionare queste cartelle:</guimenuitem
> si usa per escludere certe cartelle dalla scansione. Questa opzione è molto utile per saltare le cartelle su cui tu potresti non avere il permesso di leggere, o cartelle che fanno parte di file system virtuali, come /proc. Per aggiungere una cartella all'elenco, fai clic sul pulsante <guibutton
>Aggiungi...</guibutton
>; ciò avvierà una finestra dove puoi scegliere la cartella da una vista ad albero. Per rimuovere una cartella, selezionala e fai clic sul pulsante <guibutton
>Rimuovi</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Aspetto</title>
<screenshot>
<screeninfo
>Schermata di Aspetto</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Schermata</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>La scheda <guimenuitem
>Aspetto</guimenuitem
> di permette di configurare l'aspetto di &filelight;.</para>
<para
>La sezione <guimenuitem
>Schema</guimenuitem
> è usata per scegliere uno schema di colori per &filelight;. Gli schemi di colori sono Arcobaleno, Colori di KDE e Alto contrasto. C'è anche un cursore del <guimenuitem
>Contrasto</guimenuitem
> per regolare il contrasto dei segmenti degli anelli per una visualizzazione più facile.</para>
<para
>La casella <guimenuitem
>Usa l'antialiasing</guimenuitem
> si usa per abilitare l'uso dell'antialiasing nella visualizzazione di &filelight;. Selezionata, questa opzione dà ai segmenti degli anelli un aspetto molto più pulito.</para>
<para
>La casella <guimenuitem
>Varia le dimensioni dei caratteri delle etichette</guimenuitem
> è utile quando hai file o cartelle con nomi lunghi. Questa opzione cambierà le dimensioni dei caratteri per fare in modo che stiano meglio nella visualizzazione. Quando questa opzione è abilitata appare una casella numerica, <guimenuitem
>Dimensione minima dei caratteri</guimenuitem
>, per scegliere la dimensione più piccola a cui riscalare i caratteri.</para>
<para
>L'opzione <guimenuitem
>Mostra i file piccoli</guimenuitem
> è disattivata come impostazione predefinita perché i file piccoli tendono a intasare la visualizzazione di &filelight;. Abilita questa opzione se vuoi che i file piccoli siano inclusi nella visualizzazione di &filelight;.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Usare &filelight;</title>
<sect1 id="starting">
<title
>Avviare &filelight;</title>
<para
>&filelight; può essere avviato dal menu K, o dalla riga di comando.</para>
<sect2 id="starting-from-the-menu">
<title
>Dal menu K</title>
<para
>Apri il menu dei programmi di &kde; facendo clic sull'icona con la <guiicon
>grande K</guiicon
> sul tuo pannello. Ciò farà apparire il <guimenu
>menu dei programmi</guimenu
>. Sposta il cursore su per il menu fino all'elemento <guimenu
>Accessori</guimenu
>. Scegli <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Dalla riga di comando</title>
<para
>Puoi avviare &filelight; digitandone il nome sulla riga di comando. Se passi il nome di una cartella, come nell'esempio sotto, scansionerà quella cartella. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Scansionare le cartelle</title>
<para
>Scansionare una cartella mostra i suoi contenuti come una mappa di file. Per scansionare una cartella, usa il menu di scansione, o scrivi un URL direttamente nella barra dell'indirizzo. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Esplorare le mappe di file</title>
<para
>Una volta che la scansione è completata, ti sarà presentata una mappa di file che rappresenta la cartella che hai scansionato. La mappa di file è una serie di anelli segmentati che si espandono dal centro. I segmenti colorati vivacemente sono cartelle, quelli grigi sono file. I segmenti sono dimensionati in proporzione alla dimensione del file. I segmenti possono essere annidati, quindi, per esempio, /home/mxcl sarà un livello al di fuori e all'interno dei limiti che rappresentano /home. I segmenti sono etichettati, e passare il mouse sopra di loro ti darà maggiori dettagli su quel segmento e i suoi segmenti figli. </para>
<screenshot>
<screeninfo
>Schermata di una mappa di file</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Schermata</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Puoi aprire le cartelle con Konqueror o Konsole usando il menu contestuale per un segmento. I clic centrali aprono i file secondo il loro tipo, per esempio le immagini con Kuickshow. Puoi fare clic destro sul disco centrale per avere un menu contestuale per la cartella scansionata. Fare clic sinistro sui segmenti centrerà la mappa su quel segmento. </para>
<para
>Se vuoi migliorare la documentazione, accetterò volentieri delle correzioni :) Grazie. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Guida ai menu e ai comandi</title>
<sect1 id="scan_menu">
<title
>Il menu Scansiona</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>o</keycap
></keycombo
> </shortcut
> <guimenu
>Scansiona</guimenu
> <guimenuitem
>Scansiona cartella...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Offre una finestra di selezione delle cartelle per poter scegliere una cartella da scansionare.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
> <guimenu
>Scansiona</guimenu
> <guimenuitem
>Scansiona la cartella Home</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia una scansione della cartella Home dell'utente.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Scansiona</guimenu
> <guimenuitem
>Scansiona la cartella radice</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia una scansione della cartella radice.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Scansiona</guimenu
> <guimenuitem
>Scansioni recenti</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Fornisce un elenco delle cartelle scansionate più di recente, permettendovi un accesso rapido.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Scansiona</guimenu
> <guimenuitem
>Riscansiona</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia una nuova scansione della cartella di lavoro attuale; è utile quando si sono apportati cambiamenti al file system.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Scansiona</guimenu
> <guimenuitem
>Interrompi</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Interrompe la scansione attuale.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>q</keycap
></keycombo
> </shortcut
> <guimenu
>Scansiona</guimenu
> <guimenuitem
>Esci</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Esce da &filelight;</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>Il menu Vai</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Su</keycap
></keycombo
> </shortcut
> <guimenu
>Vai</guimenu
> <guimenuitem
>Su</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ti sposta in alto nel file system.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Sinistra</keycap
></keycombo
> </shortcut
> <guimenu
>Vai</guimenu
> <guimenuitem
>Indietro</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ti sposta un passo indietro nella tua navigazione del file system.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Destra</keycap
></keycombo
> </shortcut
> <guimenu
>Vai</guimenu
> <guimenuitem
>Avanti</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ti sposta un passo avanti nella tua navigazione del file system.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>Il menu Impostazioni</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Impostazioni</guimenu
> <guisubmenu
>Barre degli strumenti</guisubmenu
> <guimenuitem
>Barra degli strumenti principale</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Abilita o disabilita la barra degli strumenti principale dell'applicazione.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Impostazioni</guimenu
> <guisubmenu
>Barre degli strumenti</guisubmenu
> <guimenuitem
>Barra di posizione</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Abilita o disabilita la barra di posizione.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Impostazioni</guimenu
> <guimenuitem
>Configura le scorciatoie...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ti permette di configurare le scorciatoie di &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Impostazioni</guimenu
> <guimenuitem
>Configura le barre degli strumenti...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Ti permette di configurare le opzioni delle barre degli strumenti di &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Impostazioni</guimenu
> <guimenuitem
>Configura Filelight...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia la finestra di configurazione di &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>Il menu Aiuto</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Aiuto</guimenu
> <guimenuitem
>Manuale di Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Apre questo documento.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Shift</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Aiuto</guimenu
> <guimenuitem
>Che cos'è?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Attiva il cursore del mouse "Che cos'è?" che ti permette di fare clic su un oggetto per avere un suggerimento.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Aiuto</guimenu
> <guimenuitem
>Segnala un bug...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia la finestra di segnalazione dei bug.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Aiuto</guimenu
> <guimenuitem
>Informazioni su Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia la finestra di informazioni su &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Aiuto</guimenu
> <guimenuitem
>Informazioni su KDE</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Avvia la finestra di informazioni su &kde;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Riconoscimenti e licenza</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Copyright del programma 2003 di Max B. Howell <email
>max.howell@methylblue.com</email
></para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Documentazione</title>
<para
>Copyright della documentazione 2003 di Max B. Howell <email
>max.howell@methylblue.com</email
> </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Installazione</title>
<sect1 id="getting-filelight">
<title
>Come ottenere &filelight;</title>
<para
>&filelight; non fa ancora parte del progetto KDE, e può essere trovato a: <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Compilazione e installazione</title>
<para
>Per compilare e installare &filelight; sul tuo sistema, digita ciò che segue nella cartella di base della distribuzione di &filelight;: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>Siccome &filelight; usa autoconf e automake non dovresti avere problemi a compilarlo. Se incontrassi problemi, per piacere segnalali a filelight@methylblue.com o sui forum di filelight@methylblue.com.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

Binary file not shown.

@ -0,0 +1,2 @@
KDE_LANG = pt
KDE_DOCS = filelight

@ -0,0 +1,995 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Portuguese "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>O Manual do &filelight;</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
><firstname
>José</firstname
><surname
>Pires</surname
><affiliation
><address
><email
>jncp@netcabo.pt</email
></address
></affiliation
><contrib
>Tradução</contrib
></othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>O &filelight; mostra a informação da utilização do disco de forma recursiva, sendo de facto uma versão gráfica da ferramenta da linha de comandos que é o 'du'. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>utilização de disco</keyword>
<keyword
>estatísticas</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Introdução</title>
<screenshot>
<screeninfo
>Imagem do Filelight</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Imagem</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>O &filelight; permite-lhe compreender exacta e rapidamente onde é que o seu espaço em disco está a ser usado, representando graficamente o seu sistema de ficheiros como um conjunto de anéis concêntricos segmentados. Pode usá-lo para localizar os pontos críticos de espaço em disco e manipular essas áreas com o Konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Configurar o &filelight;</title>
<para
>A janela de configuração do &filelight; tem duas páginas para configurar as opções do &filelight;. As duas páginas são a <guimenuitem
>Procurar</guimenuitem
> e a <guimenuitem
>Aparência</guimenuitem
>. Por baixo, está uma descrição das páginas de configuração. Esta janela pode ser acedida se carregar em <menuchoice
><guimenu
>Configuração</guimenu
><guimenuitem
>Configurar o Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Procurar</title>
<screenshot>
<screeninfo
>Imagem da Procura</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Imagem</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>A página de procura permite-lhe configurar a forma como o &filelight; analisa as pastas. O item <guimenuitem
> Não analisar estas directorias:</guimenuitem
> é usado para excluir certas pastas da sua pesquisa. Esta opção é muito útil para ignorar as pastas nas quais você possa não ter permissões de leitura ou pastas que façam parte de um sistema de ficheiros virtual, como o '/proc'. Para adicionar uma pasta à lista, carregue no botão <guibutton
>Adicionar...</guibutton
>, o que irá iniciar uma janela onde poderá escolher uma pasta à sua escolha na árvore que aparece. Para remover uma pasta, basta seleccionar a pasta que deseja e carregar no botão <guibutton
>Remover</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Aparência</title>
<screenshot>
<screeninfo
>Imagem da Aparência</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Imagem</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>A página de <guimenuitem
>Aparência</guimenuitem
> permite-lhe configurar a forma como aparece o &filelight;.</para>
<para
>A secção do <guimenuitem
>Esquema</guimenuitem
> é usada para escolher um esquema de cores para o &filelight;. Os esquemas de cores são o Arco-Íris, as Cores do KDE, e o Alto Contraste. Existe também uma barra de <guimenuitem
>Contraste:</guimenuitem
> para ajustar o contraste dos segmentos dos anéis e facilitar a visualização.</para>
<para
>A opção <guimenuitem
>Usar o 'anti-aliasing'</guimenuitem
> é usada para activar a utilização do 'anti-aliasing' (suavização) na janela do &filelight;. Se for seleccionada, esta opção faz com que os segmentos dos anéis tenham um aspecto mais limpo.</para>
<para
>A opção <guimenuitem
>Variar os tamanhos de letra das legendas</guimenuitem
> é útil quando você tiver ficheiros ou pastas com nomes compridos. Esta opção irá alterar o tamanho da letra, de modo a permitir que esta caiba melhor na janela. Quando esta opção estiver activa, ficará disponível uma opção <guimenuitem
>Tamanho mínimo da letra:</guimenuitem
> para escolher o tamanho de letra mais pequeno a ajustar.</para>
<para
>A opção <guimenuitem
>Mostrar os ficheiros pequenos</guimenuitem
> está desactivada por omissão, dado que os ficheiros pequenos tendem a sobrecarregar a janela do &filelight;. Active esta opção se quiser ter também incluídos os seus ficheiros pequenos na janela do &filelight;.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Utilizar o &filelight;</title>
<sect1 id="starting">
<title
>Iniciar o &filelight;</title>
<para
>O &filelight; pode ser iniciado a partir do Menu K ou a partir da linha de comandos</para>
<sect2 id="starting-from-the-menu">
<title
>Do Menu K</title>
<para
>Abra o menu de programas do &kde;, carregando no ícone com o <guiicon
>K grande</guiicon
> do seu painel. Este irá mostrar o <guimenu
>menu de programas</guimenu
>. Suba o seu cursor neste menu para o item <guimenu
>Utilitários</guimenu
>. Escolha o <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>A Partir da Linha de Comandos</title>
<para
>Poderá também iniciar o &filelight;, escrevendo o seu nome na linha de comandos. Se lhe atribuir um nome de uma pasta, como no exemplo abaixo, ele irá percorrer essa pasta. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Procurar em Directorias</title>
<para
>Se procurar numa directoria ou pasta, irá mostrar o seu conteúdo como um mapa de ficheiros. Para pesquisar uma pasta, use o menu de procura ou indique um URL directamente na barra de localização. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Explorar Mapas de Ficheiros</title>
<para
>Logo que tenha terminado uma análise, ser-lhe-á apresentado um mapa de ficheiros que representa a pasta ou directoria analisada. O mapa é uma série de anéis segmentados que se expandem a partir do centro. Os segmentos mais claros são directorias, enquanto os segmentos a cinzento são ficheiros. Os segmentos são dimensionados de acordo com o tamanho dos ficheiros. Estes segmentos poderão estar encadeados como, por exemplo, o '/home/mxcl' que estará um nível para fora e dentro dos limites do segmento que representa a '/home'. Os segmentos estão legendados e, se passar o rato por cima dos segmentos, irá obter mais detalhes sobre esse segmento e sobre os seus filhos. </para>
<screenshot>
<screeninfo
>Imagem do Mapa de Ficheiros</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Imagem</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Você poderá abrir as pastas com o Konqueror ou o Konsole com o menu de contexto para esse segmento. O botão do meio do rato abre os ficheiros de acordo com o seu tipo MIME, como as imagens com o Kuickshow. Você poderá carregar com o botão direito no círculo central para obter um menu de contexto para a pasta pesquisada. Se carregar com o botão esquerdo nos segmentos irá centrar o mapa nesse segmento. </para>
<para
>Se quiser melhorar a documentação, aceitam-se de bom grado alterações :) Obrigado. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Referência do Menu e dos Comandos</title>
<sect1 id="scan_menu">
<title
>O Menu Procurar</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>o</keycap
></keycombo
> </shortcut
> <guimenu
>Procurar</guimenu
> <guimenuitem
>Analisar a Directoria..</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Mostra uma janela de selecção de pastas, para que possa escolher a pasta a analisar.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
> <guimenu
>Procurar</guimenu
> <guimenuitem
>Analisar a Directoria Pessoal</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia uma pesquisa na pasta pessoal do utilizador.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Procurar</guimenu
> <guimenuitem
>Analisar a Directoria de Raiz</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia uma pesquisa na pasta de topo (ou directoria de raiz).</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Procurar</guimenu
> <guimenuitem
>Análises Recentes</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Oferece uma lista com as pastas analisadas mais recentemente, permitindo um acesso rápido a essas pastas.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Procurar</guimenu
> <guimenuitem
>Pesquisar de Novo</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia uma nova análise sobre a pasta de trabalho actual, o que poderá ser útil se tiverem sido feitas algumas alterações ao sistema de ficheiros.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Procurar</guimenu
> <guimenuitem
>Parar</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Interrompe a análise actual.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>q</keycap
></keycombo
> </shortcut
> <guimenu
>Procurar</guimenu
> <guimenuitem
>Sair</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Sai do &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>O Menu Ir</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Cima</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Subir</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Fá-lo subir um nível no sistema de ficheiros.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Esquerda</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Recuar</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Fá-lo andar um passo para trás no seu histórico de navegação no sistema de ficheiros.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Direita</keycap
></keycombo
> </shortcut
> <guimenu
>Ir</guimenu
> <guimenuitem
>Avançar</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Fá-lo andar um passo para a frente no seu histórico de navegação no sistema de ficheiros.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>O Menu Configuração</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Configuração</guimenu
> <guisubmenu
>Barras de Ferramentas</guisubmenu
> <guimenuitem
>Mostrar a Barra Principal</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa ou desactiva a barra de ferramentas principal da aplicação.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Configuração</guimenu
> <guisubmenu
>Barras de Ferramentas</guisubmenu
> <guimenuitem
>Mostrar a Barra de Localização</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa ou desactiva a barra de ferramentas da localização.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Configuração</guimenu
> <guimenuitem
>Configurar os Atalhos...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Permite-lhe configurar os atalhos de teclado do &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Configuração</guimenu
> <guimenuitem
>Configurar as Barras de Ferramentas...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Permite-lhe configurar as opções da barra de ferramentas do &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Configuração</guimenu
> <guimenuitem
>Configurar o Filelight...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia a janela de configuração do &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>O Menu Ajuda</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Ajuda</guimenu
> <guimenuitem
>Manual do Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Abre este documento de ajuda.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Shift</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Ajuda</guimenu
> <guimenuitem
>O Que É Isto?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Activa o cursor do rato "O Que É Isto?", que lhe permite carregar num objecto para obter uma dica "O Que É Isto?".</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ajuda</guimenu
> <guimenuitem
>Comunicar um Erro...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia a janela de relatórios de erros.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ajuda</guimenu
> <guimenuitem
>Acerca do Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia a janela de informações Acerca do &filelight;.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Ajuda</guimenu
> <guimenuitem
>Acerca do KDE</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Inicia a janela de informações Acerca do &kde;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Créditos e Licença</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Programa copyright 2003 Max B. Howell <email
>max.howell@methylblue.com</email
></para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Documentação</title>
<para
>Documentação copyright 2003 Max B. Howell <email
>max.howell@methylblue.com</email
> </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Instalação</title>
<sect1 id="getting-filelight">
<title
>Como obter o &filelight;</title>
<para
>O &filelight; ainda não faz parte do projecto do KDE, mas poderá ser encontrada em: <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Compilação e Instalação</title>
<para
>Para poder compilar e instalar o &filelight; no seu sistema, escreva o seguinte na pasta de base da distribuição do &filelight;: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>Dado que o &filelight; usa o 'autoconf' e o 'automake', você não deverá ter problemas a compilá-lo. Se porventura os tiver, por favor comunique-os em filelight@methylblue.com ou nos Fóruns do &filelight;.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

@ -0,0 +1,2 @@
KDE_LANG = ru
KDE_DOCS = filelight

@ -0,0 +1,993 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Russian "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>Руководство по &filelight;</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
><firstname
>Владимир</firstname
><surname
>Давыдов</surname
><affiliation
><address
><email
>trotski@inbox.ru</email
></address
></affiliation
><contrib
>Перевод на русский</contrib
></othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; рекурсивно отображает информацию об использовании диска, и является графической альтернативой команде du. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>использование диска</keyword>
<keyword
>статистика</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Введение</title>
<screenshot>
<screeninfo
>Снимок экрана</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Снимок экрана</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight; позволяет вам легко и наглядно посмотреть использование вашего дискового пространства, представляя файловую систему в виде круговых колец. Вы можете использовать это для нахождения "узких мест" в использовании диска и затем манипулировать ими используя Konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Настройки &filelight;</title>
<para
>Окно настроек &filelight; имеет две вкладки - <guimenuitem
>Сканирование</guimenuitem
> и <guimenuitem
>Внешний вид</guimenuitem
>. Ниже вы найдёте описание каждой из вкладок. Само окно может быть вызвано из меню <menuchoice
><guimenu
>Настройка</guimenu
><guimenuitem
>Настроить Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Сканирование</title>
<screenshot>
<screeninfo
>Сканирование. Снимок экрана</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Снимок экрана</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>На вкладке сканирования вы можете настроить то, как &filelight; будет сканировать папки. Опция <guimenuitem
>Пропустить следующие каталоги:</guimenuitem
> позволяет исключить определённые папки из сканирования; это очень полезно, например, для пропуска папок, на чтение которых у вас нет прав, или папок - частей виртуальной файловой системы (таких как /proc).Для добавления папки в список, нажмите кнопку <guibutton
>Добавить...</guibutton
> - будет запущен диалог, в котором вы сможете выбрать нужную папку из дерева. Для удаления папки просто, выделите её и нажмите кнопку <guibutton
>Удалить</guibutton
></para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Внешний вид</title>
<screenshot>
<screeninfo
>Внешний вид. Снимок экрана.</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Снимок экрана</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Вкладка <guimenuitem
>Внешний вид</guimenuitem
> позволяет вам настраивать то, как &filelight; выглядит.</para>
<para
>Группа <guimenuitem
>Схема</guimenuitem
> используется для выбора цветовой схемы &filelight;. Доступны цветовые схемы Rainbow, цвета KDE, и высоко-контрастный. Также имеется ползунок <guimenuitem
>Контраст:</guimenuitem
> для регулировки контраста секторов для удобства просмотра.</para>
<para
>Флажок <guimenuitem
>Сглаживание</guimenuitem
> используется для включения сглаживания (anti-aliasing) при работе &filelight;. Если он отмечен, то сектора прорисовываются более отчётливо.</para>
<para
>Флажок <guimenuitem
>Изменить размеры шрифтов для меток</guimenuitem
> полезен при наличии файлов или папок с длинными именами. С данной опцией размер шрифта будет меняться для лучшего отображения. Если этот флажок отмечен становится доступен ползунок <guimenuitem
>Мин. размер шрифта</guimenuitem
> для выбора наименьшего размера шрифта при масштабировании.</para>
<para
>Опция <guimenuitem
>Отображать маленькие файлы</guimenuitem
> по умолчанию выключена, так как маленькие файлы вносят некоторый хаос в диаграмме.Включите эту опцию, если вы хотите включить маленькие файлы при просмотре.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Использование &filelight;</title>
<sect1 id="starting">
<title
>Запуск &filelight;</title>
<para
>&filelight; может быть запущен из главного меню или из командной строки</para>
<sect2 id="starting-from-the-menu">
<title
>Запуск из K-меню</title>
<para
>Откройте меню программ &kde; щёлкнув на значке <guiicon
>K</guiicon
> на панели. В открывшемся меню выберите подменю <guimenu
>Служебные</guimenu
>, затем выберите <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Запуск из командной строки</title>
<para
>Вы можете запустить программу &filelight; введя её название в командной строке. Если вы передадите название папки в качестве параметра, как это показано в примере, то будет произведено сканирование этой папки. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Сканирование папок.</title>
<para
>Сканирование папки показывает её содержимое как файловую карту. Для запуска, используйте меню сканирования или введите url прямо в панели расположения. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Просмотр Файловой карты</title>
<para
>Сразу после завершения сканирования вам будет представлена файловая карта, представляющая сканируемую папку. Файловая карта - это серия (частей) круговых колец, расходящихся от центра. Кольца, раскрашенные ярко - это папки, а бледно - файлы. Колца имеют размер, пропорциональный размеру файла/папки на диске. Они могут быть вложенными, например, /home/mxcl будет на первом уровне наружу, и входить в рамки представленной папки /home. Каждое кольцо имеет подпись, а при наведении мыши будет показана более подробная информация о нём и о вложенных в него. </para>
<screenshot>
<screeninfo
>Файловая карта. Снимок экрана</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Снимок экрана</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Вы можете открывать папки с помощью Konqueror или Konsole из контекстного меню кольца. Щелчок средней клавишей мыши открывает файлы по их mime-типу, например, для изображений запускается Kuickshow. Вы можете щёлкнуть парвой клавишей мыши на центральном круге для получения контекстного меню сканированной папки. Левый щелчок на кольце отцентрирует карту по нему. </para>
<para
>Если вы захотите улучшить документацию, я с превеликим удовольствием приму ваши дополнения. :) Спасибо. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Меню и список команд</title>
<sect1 id="scan_menu">
<title
>Меню Сканирование</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>o</keycap
></keycombo
> </shortcut
> <guimenu
>Сканирование</guimenu
> <guimenuitem
>Сканировать папку..</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Вызывает диалог выбора папки для того, чтобы вы выбрали папку для сканирования.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
> <guimenu
>Сканирование</guimenu
> <guimenuitem
>Сканировать домашнюю папку</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает сканирование домашней папки пользователя.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Сканирование</guimenu
> <guimenuitem
>Сканировать корневой каталог</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает сканирование корневой папки.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Сканирование</guimenu
> <guimenuitem
>Последние сканирования</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Содержит список предыдущих сканированных папок позволяя быстро до них добраться.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Сканировать</guimenu
> <guimenuitem
>Пересканировать</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает новое сканирование для текущей рабочей папки. это бывает полезно при каких-либо сделанных изменениях в файловой системе.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Сканировать</guimenu
> <guimenuitem
>Стоп</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Останавливает запущенное сканирование.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>q</keycap
></keycombo
> </shortcut
> <guimenu
>Сканировать</guimenu
> <guimenuitem
>Выход</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Выход из &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="go_menu">
<title
>Меню Перейти</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Вверх</keycap
></keycombo
> </shortcut
> <guimenu
>Начать</guimenu
> <guimenuitem
>Вверх</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Перемещает вас на один уровень вверх по файловой системе.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Влево</keycap
></keycombo
> </shortcut
> <guimenu
>Начать</guimenu
> <guimenuitem
>Назад</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Перемещает вас на предыдущий шаг просмотра файловой системы.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Alt</keycap
><keycap
>Вправо</keycap
></keycombo
> </shortcut
> <guimenu
>Начать</guimenu
> <guimenuitem
>Вперёд</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Перемещает вас на шаг вперёд по истории просмотра файловой системы.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="settings_menu">
<title
>Меню Настройка</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Настройка</guimenu
> <guisubmenu
>Панели инструментов</guisubmenu
> <guimenuitem
>Показать панель инструментов Основная</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Делает доступной/недоступной главную панель инструментов программы.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Настройка</guimenu
> <guisubmenu
>Панели инструментов</guisubmenu
> <guimenuitem
>Показать Панель инструментов Расположение</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Делает доступной/недоступной панель расположения.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Настройка</guimenu
> <guimenuitem
>Комбинации клавиш...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Позволяет вам настраивать "горячие" клавиши &filelight;</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Настройка</guimenu
> <guimenuitem
>Настроить панели инструментов...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Позволяет вам настраивать параметры панели инструментов &filelight;</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Настройка</guimenu
> <guimenuitem
>Настроить Filelight...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает диалог Параметры &filelight;.</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="help_menu">
<title
>Меню Справка</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><guimenu
>Справка</guimenu
> <guimenuitem
>Руководство "Filelight"</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Открывает данный документ.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Shift</keycap
><keycap
>F1</keycap
></keycombo
> </shortcut
> <guimenu
>Справка</guimenu
> <guimenuitem
>Что это?</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Активирует курсор мыши "Что это?", позволяющий вам щёлкнуть на интересующем вас объекте мышью и получить подсказку по нему.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Справка</guimenu
> <guimenuitem
>Сообщить об ошибке...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает диалог инструмента сообщений об ошибках.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Справка</guimenu
> <guimenuitem
>О программе Filelight</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает диалог "О программе &filelight;".</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Справка</guimenu
> <guimenuitem
>О KDE</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Запускает диалог "О &kde;".</action
></para
></listitem>
</varlistentry>
</variablelist>
</sect1>
</chapter>
<!--
<chapter id="faq">
<title
>Questions and Answers</title>
(OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work.
&reporting.bugs;
&updating.documentation;
<qandaset id="faqlist">
<qandaentry>
<question>
<para
>My Mouse doesn't work. How do I quit &filelight;?</para>
</question>
<answer>
<para
>You silly goose! Check out the <link linkend="commands"
>Commands
Section</link
> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para
>Why can't I twiddle my documents?</para>
</question>
<answer>
<para
>You can only twiddle your documents if you have the foobar.lib
installed.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>
-->
<chapter id="credits">
<!-- Include credits for the programmers, documentation writers, and
contributors here. The license for your software should then be included below
the credits with a reference to the appropriate license file included in the KDE
distribution. -->
<title
>Лицензии и благодарности</title>
<sect1 id="kapp">
<title
>&filelight;</title>
<para
>Авторские права 2003 Max B. Howell <email
>max.howell@methylblue.com</email
></para>
&underGPL; </sect1>
<sect1 id="Documentation">
<title
>Документация</title>
<para
>&copy; 2003 Max B. Howell <email
>max.howell@methylblue.com</email
> </para>
&underFDL; </sect1>
</chapter>
<appendix id="installation">
<title
>Установка</title>
<sect1 id="getting-filelight">
<title
>Где взять &filelight;</title>
<para
>Программа &filelight; пока не является частью KDE, вы можете найти её: на сайте <ulink url="http://www.methylblue.com/filelight/"
>http://www.methylblue.com/filelight/</ulink
>. </para>
</sect1>
<sect1 id="compilation">
<title
>Компиляция и установка</title>
<para
>При необходимости компиляции и установки &filelight; в вашей системе, введите следующее в каталоге с дистрибутивом &filelight;: <screen width="40"
><prompt
>%</prompt
> <userinput
>./configure --prefix=`kde-config --prefix`</userinput>
<prompt
>%</prompt
> <userinput
>make</userinput>
<prompt
>%</prompt
> <userinput
>make install</userinput
>
</screen>
</para>
<para
>В виду того, что &filelight; использует autoconf и automake у вас не должны возникнуть затруднения при компиляции. Если же всё-таки что-то пойдёт не так, сообщите, пожалуйста, об этом письмом на filelight@methylblue.com или в форуме, посвящённом &filelight;.</para>
</sect1>
</appendix>
&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->

@ -0,0 +1,2 @@
KDE_LANG = sv
KDE_DOCS = filelight

Binary file not shown.

Binary file not shown.

@ -0,0 +1,995 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1.2-Based Variant V1.0//EN" "dtd/kdex.dtd" [
<!ENTITY kappname "&filelight;">
<!ENTITY filelight "<application
>Filelight</application
>">
<!ENTITY % addindex "IGNORE">
<!ENTITY % Swedish "INCLUDE"
><!-- change language only here -->
]>
<!-- Do not define any other entities; instead, use the entities
from kde-genent.entities and $LANG/user.entities. -->
<!-- kdoctemplate v0.8 October 1 1999
Minor update to "Credits and Licenses" section on August 24, 2000
Removed "Revision history" section on 22 January 2001 -->
<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.
You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.
In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags
> and attributes is relevant ;
- also, quote all attributes.
Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->
<!-- ................................................................ -->
<!-- The language must NOT be changed here. -->
<book lang="&language;">
<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->
<bookinfo>
<title
>Handbok &filelight;</title>
<authorgroup>
<author
><firstname
>Max</firstname
> <surname
>Howell</surname
> <affiliation
> <address
><email
>max.howell@methylblue.com</email
></address>
</affiliation>
</author>
</authorgroup>
<othercredit role="translator"
><firstname
>Stefan</firstname
> <surname
>Asserhäll</surname
><affiliation
><address
><email
>stefan.asserhall@comhem.se</email
></address
></affiliation
><contrib
>Översättare</contrib
></othercredit
>
<copyright>
<year
>2003</year>
<holder
>Max Howell</holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice. Read the explanation in fdl-notice.docbook
and in the FDL itself on how to use it. -->
<legalnotice
>&FDLNotice;</legalnotice>
<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->
<date
>03/11/2003</date>
<releaseinfo
>2</releaseinfo>
<!-- Abstract about this handbook -->
<abstract>
<para
>&filelight; visar rekursiv information om diskanvändning, i stort en grafisk version av kommandoradsverktyget du. </para>
</abstract>
<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
of your application, and a few relevant keywords. -->
<keywordset>
<keyword
>KDE</keyword>
<keyword
>Filelight</keyword>
<keyword
>du</keyword>
<keyword
>diskanvändning</keyword>
<keyword
>statistik</keyword>
</keywordset>
</bookinfo>
<!-- The contents of the documentation begin here. Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML files will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->
<chapter id="introduction">
<title
>Inledning</title>
<screenshot>
<screeninfo
>Skärmbild av Filelight</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="main.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skärmbild</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>&filelight; låter dig snabbt förstå exakt var ditt diskutrymme används genom att representera filsystemet grafiskt som en uppsättning koncentriska cirkelsegment. Du kan använda det för att lokalisera ansamlingar av diskanvändning och hantera dessa områden med Konqueror. </para>
</chapter>
<chapter id="configuring">
<title
>Anpassa &filelight;</title>
<para
>&filelight;s inställningsdialogruta har två flikar för att ställa in &filelight;s alternativ. De två flikarna är <guimenuitem
>Avsökning</guimenuitem
> och <guimenuitem
>Utseende</guimenuitem
>. Nedanför finns en beskrivning av inställningsflikarna. &filelight;s inställningsdialogruta hittas genom att klicka på <menuchoice
><guimenu
>Inställningar</guimenu
> <guimenuitem
>Anpassa Filelight</guimenuitem
></menuchoice
>.</para>
<sect1 id="scanning">
<title
>Söker</title>
<screenshot>
<screeninfo
>Skärmbild av Avsökning</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_scan.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skärmbild</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Avsökningsfliken låter dig anpassa hur &filelight; söker igenom kataloger. <guimenuitem
>Avsök inte följande kataloger</guimenuitem
> används för att utesluta vissa kataloger från ansökningen. Alternativet är mycket användbart för att hoppa över kataloger som du kanske inte har rättighet att läsa, eller kataloger som är en del av ett virtuellt filsystem, såsom /proc. Klicka på knappen <guibutton
>Lägg till...</guibutton
> för att lägga till en katalog i listan. Det visar en dialogruta där du kan välja katalogen du vill ha i en trädvy. För att ta bort en katalog, markera helt enkelt den du vill ta bort och klicka på knappen <guibutton
>Ta bort</guibutton
>.</para>
<!--<madpenguin8
>I'll add a description here about what the "Scan across fs boundries" option when the option works ;-)-->
</sect1>
<sect1 id="appearance">
<title
>Utseende</title>
<screenshot>
<screeninfo
>Skärmbild av Utseende</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="config_appear.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skärmbild</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Fliken <guimenuitem
>Utseende</guimenuitem
> låter dig anpassa hur &filelight; ser ut.</para>
<para
>Avdelningen <guimenuitem
>Schema</guimenuitem
> används för att välja ett färgschema för &filelight;. Färgscheman är Regnbåge, KDE färger och Hög kontrast. Det finns också ett skjutreglage, <guimenuitem
>Kontrast</guimenuitem
>, för att justera segmentens kontrast, så de är lättare att se.</para>
<para
>Kryssrutan <guimenuitem
>Använd kantutjämning</guimenuitem
> används för att aktivera användning av kantutjämning i &filelight;s vy. Att markera alternativet gör att segmenten får ett mycket renare utseende.</para>
<para
>Kryssrutan <guimenuitem
>Variera teckenstorlek för namn</guimenuitem
> är användbar när du har filer eller kataloger med långa namn. Alternativet minskar teckensnittets storlek för att låta det bättre passa in i vyn. När alternativet är aktiverat, blir nummerrutan <guimenuitem
>Minimal teckenstorlek:</guimenuitem
> tillgänglig för att välja den minsta teckenstorlek som ska skalas till</para>
<para
>Alternativet <guimenuitem
>Visa små filer</guimenuitem
> är normalt inaktiverat eftersom små filer brukar skräpa ner &filelight;s vy. Aktivera alternativet om du vill att små filer ska ingå i &filelight;s vy.</para>
</sect1>
</chapter>
<!-- REMOVE ME ************************************ -->
<chapter id="using">
<title
>Använda &filelight;</title>
<sect1 id="starting">
<title
>Starta &filelight;</title>
<para
>&filelight; kan startas från K-menyn eller från kommandoraden.</para>
<sect2 id="starting-from-the-menu">
<title
>Från K-menyn</title>
<para
>Öppna &kde;:s programmeny genom att klicka på ikonen med <guiicon
>stort K</guiicon
> i panelen. Det visar <guimenu
>programmenyn</guimenu
>. Flytta markören till menyalternativet <guimenu
>Tillbehör</guimenu
> i menyn. Välj <guimenuitem
>&filelight;</guimenuitem
>. </para>
</sect2>
<sect2 id="starting-from-the-command-line">
<title
>Från kommandoraden</title>
<para
>Du kan starta &filelight; genom att skriva in dess namn på kommandoraden. Om du anger ett katalognamn, som i exemplet ovan, söks den katalogen igenom. </para>
<informalexample>
<screen
><prompt
>%</prompt
><userinput
><command
>filelight</command
> <option
><replaceable
>/home</replaceable
></option
></userinput
>
</screen>
</informalexample>
</sect2>
</sect1>
<sect1 id="scanning-directories">
<title
>Avsöka kataloger</title>
<para
>Att söka igenom en katalog visar dess innehåll som en filavbildning. Använd menyn Avsök för att söka igenom en katalog, eller skriv in en webbadress direkt i platsraden. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
<sect1 id="exploring-filemaps">
<title
>Utforska filavbildningar</title>
<para
>Så fort en sökning är färdig visas en filavbildning som motsvarar katalogerna som du sökt igenom. Filavbildningen är en serie cirkelsegment som expanderas från centrum. Starkt färgade segment är kataloger, medan går segment är filer. Segment har en storlek som är proportionell mot deras filstorlek. Segment kan vara hierarkiska, alltså är till exempel /home/mxcl en nivå ut och inom gränserna för segmentet som representerar /home. Segment har namn, och att hålla musen stilla över ett segment ger mer information om segmentet och underliggande segment. </para>
<screenshot>
<screeninfo
>Skärmbild av filavbildning</screeninfo>
<mediaobject>
<imageobject
><imagedata fileref="filemap.png" format="PNG"/></imageobject>
<textobject
><phrase
>Skärmbild</phrase
></textobject>
</mediaobject>
</screenshot>
<para
>Du kan öppna kataloger med Konqueror eller Konsole i segmentets sammanhangsberoende meny. Att klicka med mittenknappen öppnar filer enligt Mime-typ, så bilder öppnas med Kuickshow. Du kan högerklicka i den centrala cirkeln för att visa en sammanhangsberoende meny för katalogen som sökts igenom. Att vänsterklicka på segment centrerar om bilden på det segmentet. </para>
<para
>Om du vill förbättra dokumentationen, tar jag gärna emot fixar. Tack. </para>
<!--<sect2 id="scan-home"
><para
>1</para
></sect2>
<sect2 id="scan-root"
><para
>1</para
></sect2>
<sect2 id="scan-directory"
><para
>1</para
></sect2>
<sect2 id="scan-recent"
><para
>1</para
></sect2
>-->
</sect1>
</chapter>
<!--<para>
<screenshot>
<screeninfo
>Here's a screenshot of &filelight;</screeninfo>
<mediaobject>
<imageobject>
<imagedata fileref="screenshot.png" format="PNG"/>
</imageobject>
<imageobject>
<imagedata fileref="screenshot.eps" format="EPS"/>
</imageobject>
<textobject>
<phrase
>Screenshot</phrase>
</textobject>
</mediaobject>
</screenshot>
</para
>-->
<chapter id="commands">
<title
>Meny och kommandoreferens</title>
<sect1 id="scan_menu">
<title
>Menyn Avsök</title>
<variablelist>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>O</keycap
></keycombo
> </shortcut
> <guimenu
>Avsök</guimenu
> <guimenuitem
>Avsök katalog...</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Erbjuder en dialogruta för katalogval så att du kan välja en katalog att söka igenom.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Home</keycap
></keycombo
> </shortcut
> <guimenu
>Avsök</guimenu
> <guimenuitem
>Avsök hemkatalog</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Startar en sökning i användarens hemkatalog.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Avsök</guimenu
> <guimenuitem
>Avsök rotkatalog</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Startar en sökning i rotkatalogen.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><guimenu
>Avsök</guimenu
> <guimenuitem
>Senaste avsökningarna</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Tillhandahåller en lista med de senast avsökta katalogerna, vilket tillåter snabb åtkomst till dessa kataloger.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>F5</keycap
> </shortcut
> <guimenu
>Avsök</guimenu
> <guimenuitem
>Avsök igen</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Startar en ny sökning av aktuell arbetskatalog. Det är användbart när ändringar har gjorts i filsystemet.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycap
>Esc</keycap
> </shortcut
> <guimenu
>Avsök</guimenu
> <guimenuitem
>Stoppa</guimenuitem
> </menuchoice
></term>
<listitem
><para
><action
>Stoppar nuvarande sökning.</action
></para
></listitem>
</varlistentry>
<varlistentry>
<term
><menuchoice
><shortcut
> <keycombo
><keycap
>Ctrl</keycap
><keycap
>Q</keycap
></keycombo
> </shortcut
> <guimenu
>Avsök</guimenu
> <guimenuitem