BUG:215923 git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdeedu@1054174 283d02a7-25f6-0310-bc7c-ecb5cbfe19dav3.5.13-sru
toma
15 years ago
commit
ce599e4f9f
@ -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,176 @@
|
||||
Basic Installation
|
||||
==================
|
||||
|
||||
These are generic installation instructions.
|
||||
|
||||
The `configure' shell script attempts to guess correct values for
|
||||
various system-dependent variables used during compilation. It uses
|
||||
those values to create a `Makefile' in each directory of the package.
|
||||
It may also create one or more `.h' files containing system-dependent
|
||||
definitions. Finally, it creates a shell script `config.status' that
|
||||
you can run in the future to recreate the current configuration, a file
|
||||
`config.cache' that saves the results of its tests to speed up
|
||||
reconfiguring, and a file `config.log' containing compiler output
|
||||
(useful mainly for debugging `configure').
|
||||
|
||||
If you need to do unusual things to compile the package, please try
|
||||
to figure out how `configure' could check whether to do them, and mail
|
||||
diffs or instructions to the address given in the `README' so they can
|
||||
be considered for the next release. If at some point `config.cache'
|
||||
contains results you don't want to keep, you may remove or edit it.
|
||||
|
||||
The file `configure.in' is used to create `configure' by a program
|
||||
called `autoconf'. You only need `configure.in' if you want to change
|
||||
it or regenerate `configure' using a newer version of `autoconf'.
|
||||
|
||||
The simplest way to compile this package is:
|
||||
|
||||
1. `cd' to the directory containing the package's source code and type
|
||||
`./configure' to configure the package for your system. If you're
|
||||
using `csh' on an old version of System V, you might need to type
|
||||
`sh ./configure' instead to prevent `csh' from trying to execute
|
||||
`configure' itself.
|
||||
|
||||
Running `configure' takes a while. While running, it prints some
|
||||
messages telling which features it is checking for.
|
||||
|
||||
2. Type `make' to compile the package.
|
||||
|
||||
3. Optionally, type `make check' to run any self-tests that come with
|
||||
the package.
|
||||
|
||||
4. Type `make install' to install the programs and any data files and
|
||||
documentation.
|
||||
|
||||
5. You can remove the program binaries and object files from the
|
||||
source code directory by typing `make clean'. To also remove the
|
||||
files that `configure' created (so you can compile the package for
|
||||
a different kind of computer), type `make distclean'. There is
|
||||
also a `make maintainer-clean' target, but that is intended mainly
|
||||
for the package's developers. If you use it, you may have to get
|
||||
all sorts of other programs in order to regenerate files that came
|
||||
with the distribution.
|
||||
|
||||
Compilers and Options
|
||||
=====================
|
||||
|
||||
Some systems require unusual options for compilation or linking that
|
||||
the `configure' script does not know about. You can give `configure'
|
||||
initial values for variables by setting them in the environment. Using
|
||||
a Bourne-compatible shell, you can do that on the command line like
|
||||
this:
|
||||
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
|
||||
|
||||
Or on systems that have the `env' program, you can do it like this:
|
||||
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
|
||||
|
||||
Compiling For Multiple Architectures
|
||||
====================================
|
||||
|
||||
You can compile the package for more than one kind of computer at the
|
||||
same time, by placing the object files for each architecture in their
|
||||
own directory. To do this, you must use a version of `make' that
|
||||
supports the `VPATH' variable, such as GNU `make'. `cd' to the
|
||||
directory where you want the object files and executables to go and run
|
||||
the `configure' script. `configure' automatically checks for the
|
||||
source code in the directory that `configure' is in and in `..'.
|
||||
|
||||
If you have to use a `make' that does not supports the `VPATH'
|
||||
variable, you have to compile the package for one architecture at a time
|
||||
in the source code directory. After you have installed the package for
|
||||
one architecture, use `make distclean' before reconfiguring for another
|
||||
architecture.
|
||||
|
||||
Installation Names
|
||||
==================
|
||||
|
||||
By default, `make install' will install the package's files in
|
||||
`/usr/local/kde/bin', `/usr/local/kde/lib', etc. You can specify an
|
||||
installation prefix other than `/usr/local/kde' by giving `configure'
|
||||
the option `--prefix=PATH'.
|
||||
|
||||
You can specify separate installation prefixes for
|
||||
architecture-specific files and architecture-independent files. If you
|
||||
give `configure' the option `--exec-prefix=PATH', the package will use
|
||||
PATH as the prefix for installing programs and libraries.
|
||||
Documentation and other data files will still use the regular prefix.
|
||||
|
||||
If the package supports it, you can cause programs to be installed
|
||||
with an extra prefix or suffix on their names by giving `configure' the
|
||||
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
|
||||
|
||||
Optional Features
|
||||
=================
|
||||
|
||||
Some packages pay attention to `--enable-FEATURE' options to
|
||||
`configure', where FEATURE indicates an optional part of the package.
|
||||
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
|
||||
is something like `gnu-as' or `x' (for the X Window System). The
|
||||
`README' should mention any `--enable-' and `--with-' options that the
|
||||
package recognizes.
|
||||
|
||||
For packages that use the X Window System, `configure' can usually
|
||||
find the X include and library files automatically, but if it doesn't,
|
||||
you can use the `configure' options `--x-includes=DIR' and
|
||||
`--x-libraries=DIR' to specify their locations.
|
||||
|
||||
Specifying the System Type
|
||||
==========================
|
||||
|
||||
There may be some features `configure' can not figure out
|
||||
automatically, but needs to determine by the type of host the package
|
||||
will run on. Usually `configure' can figure that out, but if it prints
|
||||
a message saying it can not guess the host type, give it the
|
||||
`--host=TYPE' option. TYPE can either be a short name for the system
|
||||
type, such as `sun4', or a canonical name with three fields:
|
||||
CPU-COMPANY-SYSTEM
|
||||
|
||||
See the file `config.sub' for the possible values of each field. If
|
||||
`config.sub' isn't included in this package, then this package doesn't
|
||||
need to know the host type.
|
||||
|
||||
If you are building compiler tools for cross-compiling, you can also
|
||||
use the `--target=TYPE' option to select the type of system they will
|
||||
produce code for and the `--build=TYPE' option to select the type of
|
||||
system on which you are compiling the package.
|
||||
|
||||
Sharing Defaults
|
||||
================
|
||||
|
||||
If you want to set default values for `configure' scripts to share,
|
||||
you can create a site shell script called `config.site' that gives
|
||||
default values for variables like `CC', `cache_file', and `prefix'.
|
||||
`configure' looks for `PREFIX/share/config.site' if it exists, then
|
||||
`PREFIX/etc/config.site' if it exists. Or, you can set the
|
||||
`CONFIG_SITE' environment variable to the location of the site script.
|
||||
A warning: not all `configure' scripts look for a site script.
|
||||
|
||||
Operation Controls
|
||||
==================
|
||||
|
||||
`configure' recognizes the following options to control how it
|
||||
operates.
|
||||
|
||||
`--cache-file=FILE'
|
||||
Use and save the results of the tests in FILE instead of
|
||||
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
|
||||
debugging `configure'.
|
||||
|
||||
`--help'
|
||||
Print a summary of the options to `configure', and exit.
|
||||
|
||||
`--quiet'
|
||||
`--silent'
|
||||
`-q'
|
||||
Do not print messages saying which checks are being made.
|
||||
|
||||
`--srcdir=DIR'
|
||||
Look for the package's source code in directory DIR. Usually
|
||||
`configure' can determine that directory automatically.
|
||||
|
||||
`--version'
|
||||
Print the version of Autoconf used to generate the `configure'
|
||||
script, and exit.
|
||||
|
||||
`configure' also accepts some other, not widely useful, options.
|
||||
|
||||
@ -0,0 +1,41 @@
|
||||
/**
|
||||
* @mainpage KDE Educational Software
|
||||
*
|
||||
* This section contains the API references for KDE's collection
|
||||
* of educational software. These include:
|
||||
*
|
||||
* - <a href="kalzium/html/index.html"><b>kalzium</b></a>\n
|
||||
* <i>Periodic table of elements.</i>
|
||||
* - <a href="kbruch/html/index.html"><b>kbruch</b></a>\n
|
||||
* <i>Fraction excercise trainer.</i>
|
||||
* - <a href="keduca/html/index.html"><b>keduca</b></a>\n
|
||||
* <i>Creation and revision of form-based tests and exams.</i>
|
||||
* - <a href="khangman/html/index.html"><b>khangman</b></a>\n
|
||||
* <i>Hangman game. The child should guess a word letter by letter.</i>
|
||||
* - <a href="kig/html/index.html"><b>kig</b></a>\n
|
||||
* <i>Interactive geometry.</i>
|
||||
* - <a href="kiten/html/index.html"><b>kiten</b></a>\n
|
||||
* <i>Japanese reference tool.</i>
|
||||
* - <a href="klatin/html/index.html"><b>klatin</b></a>\n
|
||||
* <i>Aims to help revise or learn latin.</i>
|
||||
* - <a href="klettres/html/index.html"><b>klettres</b></a>\n
|
||||
* <i>Helps child to learn the alphabet and to read some syllables.</i>
|
||||
* - <a href="kmplot/html/index.html"><b>kmplot</b></a>\n
|
||||
* <i>Mathematical function plotter.</i>
|
||||
* - <a href="kpercentage/html/index.html"><b>kpercentage</b></a>\n
|
||||
* - <a href="kstars/html/index.html"><b>kstars</b></a>\n
|
||||
* <i>Desktop planetarium.</i>
|
||||
* - <a href="ktouch/html/index.html"><b>ktouch</b></a>\n
|
||||
* <i>Program for learning touch typing.</i>
|
||||
* - <a href="kturtle/html/index.html"><b>kturtle</b></a>\n
|
||||
* - <a href="kverbos/html/index.html"><b>kverbos</b></a>\n
|
||||
* - <a href="kvoctrain/html/index.html"><b>kvoctrain</b></a>\n
|
||||
* <i>Vocabulary trainer.</i>
|
||||
* - <a href="kwordquiz/html/index.html"><b>kwordquiz</b></a>\n
|
||||
*
|
||||
* And a support library <a href="libkdeedu/html/index.html"><b>libkdeedu</b></a>.
|
||||
*
|
||||
* You can find more information about the <i>KDE Edutainment Project</i> at
|
||||
* <a href="http://edu.kde.org">edu.kde.org</a>.
|
||||
*
|
||||
*/
|
||||
@ -0,0 +1,7 @@
|
||||
AUTOMAKE_OPTIONS = foreign 1.6.1
|
||||
COMPILE_FIRST = libkdeedu
|
||||
DISTCLEANFILES = inst-apps
|
||||
|
||||
MAINTAINERCLEANFILES = subdirs configure.in acinclude.m4 SUBDIRS
|
||||
include admin/deps.am
|
||||
|
||||
@ -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,54 @@
|
||||
In this file:
|
||||
|
||||
* What it is
|
||||
* Common Mistakes
|
||||
* Debugging
|
||||
* More Info
|
||||
|
||||
What it is
|
||||
----------
|
||||
|
||||
* blinken: the KDE version of the well-known game Simon Says
|
||||
* kalzium: periodic table of elements
|
||||
* kanagram: an anagram game
|
||||
* kbruch: fraction excercise trainer
|
||||
* keduca: creation and revision of form-based tests and exams.
|
||||
* kgeography: geography learning program
|
||||
* khangman: hangman game. The child should guess a word letter by letter.
|
||||
* kig: interactive geometry
|
||||
* kiten: japanese reference tool
|
||||
* klatin: aims to help revise or learn Latin
|
||||
* klettres: helps child to learn the alphabet and to read some syllables
|
||||
* kmplot: mathematical function plotter
|
||||
* kpercentage: math application to improve skills in calculating percentages
|
||||
* kstars: desktop planetarium
|
||||
* ktouch: program for learning touch typing
|
||||
* kturtle: educational programming environment using the Logo programming language
|
||||
* kverbos: tudy Spanish verb forms
|
||||
* kvoctrain: vocabulary trainer
|
||||
* kwordquiz: a powerful way to master new vocabularies
|
||||
|
||||
Common Mistakes
|
||||
---------------
|
||||
|
||||
If configure claims Qt cannot be found, have a look at http://www.trolltech.com
|
||||
to get a copy of latest Qt 3.3.x version.
|
||||
|
||||
Debugging
|
||||
---------
|
||||
|
||||
You can use --enable-debug with the configure script, if you want to have
|
||||
debug code in your KDE apps and libs. I recommend to do this, since this
|
||||
is alpha software and this makes debugging things a whole lot easier.
|
||||
|
||||
More Info
|
||||
---------
|
||||
|
||||
Have a look at the individual subdirectories, if you want to know, what
|
||||
versions of apps are included.
|
||||
|
||||
Please direct any bug reports to our bug list by visiting
|
||||
http://bugs.kde.org.
|
||||
|
||||
General KDE discussions should go to the KDE mailing list (kde@kde.org).
|
||||
|
||||
@ -0,0 +1,25 @@
|
||||
edu_folder = $(kde_appsdir)/Edutainment
|
||||
|
||||
install-data-local:
|
||||
$(mkinstalldirs) $(DESTDIR)$(edu_folder)/Languages
|
||||
$(INSTALL_DATA) $(srcdir)/languages.desktop $(DESTDIR)$(edu_folder)/Languages/.directory
|
||||
|
||||
$(mkinstalldirs) $(DESTDIR)$(edu_folder)/Mathematics
|
||||
$(INSTALL_DATA) $(srcdir)/mathematics.desktop $(DESTDIR)$(edu_folder)/Mathematics/.directory
|
||||
|
||||
$(mkinstalldirs) $(DESTDIR)$(edu_folder)/Science
|
||||
$(INSTALL_DATA) $(srcdir)/science.desktop $(DESTDIR)$(edu_folder)/Science/.directory
|
||||
|
||||
$(mkinstalldirs) $(DESTDIR)$(edu_folder)/Tools
|
||||
$(INSTALL_DATA) $(srcdir)/tools.desktop $(DESTDIR)$(edu_folder)/Tools/.directory
|
||||
|
||||
$(mkinstalldirs) $(DESTDIR)$(edu_folder)/Miscellaneous
|
||||
$(INSTALL_DATA) $(srcdir)/miscellaneous.desktop $(DESTDIR)$(edu_folder)/Miscellaneous/.directory
|
||||
|
||||
uninstall-local:
|
||||
-rm -f $(DESTDIR)$(kde_appsdir)/Settings/Databases/.directory
|
||||
-rm -f $(DESTDIR)$(edu_folder)/Languages/.directory
|
||||
-rm -f $(DESTDIR)$(edu_folder)/Mathematics/.directory
|
||||
-rm -f $(DESTDIR)$(edu_folder)/Sience/.directory
|
||||
-rm -f $(DESTDIR)$(edu_folder)/Tools/.directory
|
||||
-rm -f $(DESTDIR)$(edu_folder)/Miscellaneous/.directory
|
||||
@ -0,0 +1,70 @@
|
||||
[Desktop Entry]
|
||||
Icon=edu_languages
|
||||
Name=Languages
|
||||
Name[af]=Tale
|
||||
Name[ar]=اللغات
|
||||
Name[be]=Мовы
|
||||
Name[bg]=Езици
|
||||
Name[bn]=ভাষা
|
||||
Name[br]=Yezhoù
|
||||
Name[bs]=Jezici
|
||||
Name[ca]=Idiomes
|
||||
Name[cs]=Jazyky
|
||||
Name[csb]=Jãzëczi
|
||||
Name[cy]=Ieithoedd
|
||||
Name[da]=Sprog
|
||||
Name[de]=Sprachen
|
||||
Name[el]=Γλώσσες
|
||||
Name[eo]=Lingvoj
|
||||
Name[es]=Idiomas
|
||||
Name[et]=Keeled
|
||||
Name[eu]=Hizkuntzak
|
||||
Name[fa]=زبانها
|
||||
Name[fi]=Kielet
|
||||
Name[fo]=Mál
|
||||
Name[fr]=Langues
|
||||
Name[ga]=Teangacha
|
||||
Name[gl]=Linguas
|
||||
Name[he]=שפות
|
||||
Name[hi]=भाषाएँ
|
||||
Name[hr]=Jezici
|
||||
Name[hu]=Nyelvek
|
||||
Name[is]=Tungumál
|
||||
Name[it]=Lingue
|
||||
Name[ja]=言語
|
||||
Name[ka]=ენები
|
||||
Name[km]=ភាសា
|
||||
Name[lt]=Kalbos
|
||||
Name[lv]=Valodas
|
||||
Name[mk]=Јазици
|
||||
Name[mn]=Хэл
|
||||
Name[ms]=Bahasa
|
||||
Name[nb]=Språk
|
||||
Name[nds]=Spraken
|
||||
Name[ne]=भाषा
|
||||
Name[nl]=Talen
|
||||
Name[nn]=Språk
|
||||
Name[nso]=Maleme
|
||||
Name[pa]=ਭਾਸ਼ਾਵਾਂ
|
||||
Name[pl]=Języki
|
||||
Name[pt]=Línguas
|
||||
Name[pt_BR]=Idiomas
|
||||
Name[ru]=Языки
|
||||
Name[se]=Gielat
|
||||
Name[sk]=Jazyky
|
||||
Name[sl]=Jeziki
|
||||
Name[sr]=Језици
|
||||
Name[sr@Latn]=Jezici
|
||||
Name[sv]=Språk
|
||||
Name[ta]=மொழிகள்
|
||||
Name[tg]=Забонҳо
|
||||
Name[tr]=Diller
|
||||
Name[uk]=Мови
|
||||
Name[uz]=Tillar
|
||||
Name[uz@cyrillic]=Тиллар
|
||||
Name[ven]=Dzinyambo
|
||||
Name[vi]=Ngôn ngữ
|
||||
Name[xh]=Iilwimi
|
||||
Name[zh_CN]=语言
|
||||
Name[zh_TW]=語言
|
||||
Name[zu]=Izilimi
|
||||
@ -0,0 +1,70 @@
|
||||
[Desktop Entry]
|
||||
Icon=edu_mathematics
|
||||
Name=Mathematics
|
||||
Name[af]=Wiskunde
|
||||
Name[ar]=رياضيات
|
||||
Name[be]=Матэматыка
|
||||
Name[bg]=Математика
|
||||
Name[bn]=গণিত
|
||||
Name[br]=Jedoniel
|
||||
Name[bs]=Matematika
|
||||
Name[ca]=Matemàtiques
|
||||
Name[cs]=Matematika
|
||||
Name[csb]=Matematika
|
||||
Name[cy]=Mathemateg
|
||||
Name[da]=Matematik
|
||||
Name[de]=Mathematik
|
||||
Name[el]=Μαθηματικά
|
||||
Name[eo]=Matematiko
|
||||
Name[es]=Matemáticas
|
||||
Name[et]=Matemaatika
|
||||
Name[eu]=Matematikak
|
||||
Name[fa]=ریاضیات
|
||||
Name[fi]=Matematiikka
|
||||
Name[fo]=Støddfrøði
|
||||
Name[fr]=Mathématiques
|
||||
Name[ga]=Matamaitic
|
||||
Name[gl]=Matemáticas
|
||||
Name[he]=מתמטיקה
|
||||
Name[hi]=गणित
|
||||
Name[hr]=Matematika
|
||||
Name[hu]=Matematika
|
||||
Name[is]=Stærðfræði
|
||||
Name[it]=Matematica
|
||||
Name[ja]=数学
|
||||
Name[ka]=მათემატიკა
|
||||
Name[km]=គណិតវិទ្យា
|
||||
Name[lt]=Matematika
|
||||
Name[lv]=Matemātika
|
||||
Name[mk]=Математика
|
||||
Name[mn]=Математикийн
|
||||
Name[ms]=Matematik
|
||||
Name[nb]=Matematikk
|
||||
Name[nds]=Reken
|
||||
Name[ne]=गणित
|
||||
Name[nl]=Wiskunde
|
||||
Name[nn]=Matematikk
|
||||
Name[nso]=Dipalontshetshere
|
||||
Name[pa]=ਗਣਿਤ
|
||||
Name[pl]=Matematyka
|
||||
Name[pt]=Matemática
|
||||
Name[pt_BR]=Matemática
|
||||
Name[ru]=Математика
|
||||
Name[se]=Matematihkka
|
||||
Name[sk]=Matematika
|
||||
Name[sl]=Matematika
|
||||
Name[sr]=Математика
|
||||
Name[sr@Latn]=Matematika
|
||||
Name[sv]=Matematik
|
||||
Name[ta]=கணிதம்
|
||||
Name[tg]=Математика
|
||||
Name[tr]=Matematik
|
||||
Name[uk]=Математика
|
||||
Name[uz]=Matematika
|
||||
Name[uz@cyrillic]=Математика
|
||||
Name[ven]=Zwa dzimbalo
|
||||
Name[vi]=Toán học
|
||||
Name[xh]=Imathematika
|
||||
Name[zh_CN]=数学
|
||||
Name[zh_TW]=數學
|
||||
Name[zu]=Ezezibalo
|
||||
@ -0,0 +1,65 @@
|
||||
[Desktop Entry]
|
||||
Icon=edu_miscellaneous
|
||||
Name=Miscellaneous
|
||||
Name[af]=Allerande
|
||||
Name[ar]=منوعات
|
||||
Name[be]=Рознае
|
||||
Name[bg]=Разни
|
||||
Name[bn]=বিবিধ
|
||||
Name[br]=A bep seurt
|
||||
Name[bs]=Razno
|
||||
Name[ca]=Diversos
|
||||
Name[cs]=Různé
|
||||
Name[csb]=Jine
|
||||
Name[cy]=Amrywiol
|
||||
Name[da]=Diverse
|
||||
Name[de]=Verschiedenes
|
||||
Name[el]=Διάφορα
|
||||
Name[eo]=Diversoj
|
||||
Name[es]=Varios
|
||||
Name[et]=Mitmesugust
|
||||
Name[eu]=Miszelanea
|
||||
Name[fa]=گوناگون
|
||||
Name[fi]=Sekalainen
|
||||
Name[fr]=Divers
|
||||
Name[ga]=Éagsúil
|
||||
Name[gl]=Varios
|
||||
Name[he]=שונות
|
||||
Name[hi]=विविध
|
||||
Name[hr]=Razno
|
||||
Name[hu]=Egyéb
|
||||
Name[is]=Ýmislegt
|
||||
Name[it]=Varie
|
||||
Name[ja]=その他
|
||||
Name[ka]=სხვადასხვა
|
||||
Name[km]=ផ្សេងៗ
|
||||
Name[lt]=Įvairūs dalykai
|
||||
Name[lv]=Dažādi
|
||||
Name[mk]=Разно
|
||||
Name[ms]=Pelbagai
|
||||
Name[nb]=Diverse
|
||||
Name[nds]=Anner Saken
|
||||
Name[ne]=विविध
|
||||
Name[nl]=Diversen
|
||||
Name[nn]=Ymse
|
||||
Name[pa]=ਫੁਟਕਲ
|
||||
Name[pl]=Różne
|
||||
Name[pt]=Vários
|
||||
Name[pt_BR]=Variados
|
||||
Name[ro]=Diverse
|
||||
Name[ru]=Разное
|
||||
Name[se]=Feará mii
|
||||
Name[sk]=Rôzne
|
||||
Name[sl]=Razno
|
||||
Name[sr]=Разно
|
||||
Name[sr@Latn]=Razno
|
||||
Name[sv]=Diverse
|
||||
Name[ta]=இதர தேர்வுகள்
|
||||
Name[tg]=Гуногун
|
||||
Name[tr]=Çeşitli
|
||||
Name[uk]=Різне
|
||||
Name[uz]=Har xil
|
||||
Name[uz@cyrillic]=Ҳар хил
|
||||
Name[vi]=Linh tinh
|
||||
Name[zh_CN]=杂项
|
||||
Name[zh_TW]=雜項
|
||||
@ -0,0 +1,71 @@
|
||||
[Desktop Entry]
|
||||
Icon=edu_science
|
||||
Name=Science
|
||||
Name[af]=Wetenskap
|
||||
Name[ar]=العلم
|
||||
Name[az]=Elm
|
||||
Name[be]=Навука
|
||||
Name[bg]=Наука
|
||||
Name[bn]=বিজ্ঞান
|
||||
Name[br]=Skiantoù
|
||||
Name[bs]=Nauka
|
||||
Name[ca]=Ciència
|
||||
Name[cs]=Věda
|
||||
Name[csb]=Ùczba
|
||||
Name[cy]=Gwyddoniaeth
|
||||
Name[da]=Videnskab
|
||||
Name[de]=Wissenschaft
|
||||
Name[el]=Επιστήμη
|
||||
Name[eo]=Sciencumoj
|
||||
Name[es]=Ciencia
|
||||
Name[et]=Loodusteadused
|
||||
Name[eu]=Zientzia
|
||||
Name[fa]=علم
|
||||
Name[fi]=Luonnontieteet
|
||||
Name[fo]=Náttúruvísind
|
||||
Name[ga]=Eolaíocht
|
||||
Name[gl]=Ciencia
|
||||
Name[he]=מדע
|
||||
Name[hi]=विज्ञान
|
||||
Name[hr]=Znanost
|
||||
Name[hu]=Tudományok
|
||||
Name[is]=Vísindi
|
||||
Name[it]=Scienza
|
||||
Name[ja]=サイエンス
|
||||
Name[ka]=მეცნიერება
|
||||
Name[km]=វិទ្យាសាស្ត្រ
|
||||
Name[lt]=Mokslas
|
||||
Name[lv]=Zinātne
|
||||
Name[mk]=Наука
|
||||
Name[mn]=Шинжлэх Ухааны
|
||||
Name[ms]=Sains
|
||||
Name[nb]=Vitenskap
|
||||
Name[nds]=Wetenschap
|
||||
Name[ne]=विज्ञान
|
||||
Name[nl]=Wetenschappelijk
|
||||
Name[nn]=Vitskap
|
||||
Name[nso]=Mahlale
|
||||
Name[pa]=ਵਿਗਿਆਨ
|
||||
Name[pl]=Nauka
|
||||
Name[pt]=Ciência
|
||||
Name[pt_BR]=Ciências
|
||||
Name[ro]=Ştiinţă
|
||||
Name[ru]=Другие науки
|
||||
Name[se]=Dieđa
|
||||
Name[sk]=Vedecký
|
||||
Name[sl]=Znanost
|
||||
Name[sr]=Наука
|
||||
Name[sr@Latn]=Nauka
|
||||
Name[sv]=Vetenskap
|
||||
Name[ta]=அறிவியல்
|
||||
Name[tg]=Фан
|
||||
Name[tr]=Bilim
|
||||
Name[uk]=Наука
|
||||
Name[uz]=Fan
|
||||
Name[uz@cyrillic]=Фан
|
||||
Name[ven]=Vhutsila
|
||||
Name[vi]=Khoa học
|
||||
Name[xh]=Inzulu lwazi
|
||||
Name[zh_CN]=科学
|
||||
Name[zh_TW]=科學
|
||||
Name[zu]=Ubuchwepheshe bezesayensi
|
||||
@ -0,0 +1 @@
|
||||
Albert Astals Cid <tsdgeos AT terra DOT es>
|
||||
@ -0,0 +1,2 @@
|
||||
2005-02-16 Albert Astals Cid <tsdgeos@terra.es>
|
||||
* Initial import
|
||||
@ -0,0 +1,4 @@
|
||||
SUBDIRS = src images icons sounds fonts
|
||||
|
||||
docsdir = $(kde_datadir)/blinken/
|
||||
docs_DATA = README.packagers
|
||||
@ -0,0 +1,16 @@
|
||||
blinKen uses a special handwriting font called Steve that is in the
|
||||
fonts directory to show the status text. If this font is not currently installed
|
||||
on the target system, on first run blinKen uses the fonts:/ ioslave to copy it
|
||||
to the user's fonts location.
|
||||
|
||||
This can cause problems, because if the program
|
||||
is used by 100 users there will be 100 copies of the font, one for each user.
|
||||
|
||||
To solve that we suggest making a package with "Some Juicy Fonts"
|
||||
(http://www.sourceforge.net/projects/sjfonts) that includes the Steve font
|
||||
and make the blinKen package depend on it.
|
||||
|
||||
If you do not want/cannot do that, please make blinKen depend on
|
||||
having kdebase installed as the fonts:/ ioslave is there.
|
||||
|
||||
- blinKen developers
|
||||
@ -0,0 +1,2 @@
|
||||
fontsdir = $(kde_datadir)/blinken/fonts
|
||||
fonts_DATA = steve.ttf
|
||||
Binary file not shown.
@ -0,0 +1 @@
|
||||
KDE_ICON = blinken
|
||||
|
After Width: | Height: | Size: 9.0 KiB |
|
After Width: | Height: | Size: 844 B |
|
After Width: | Height: | Size: 1.2 KiB |
|
After Width: | Height: | Size: 2.0 KiB |
|
After Width: | Height: | Size: 3.1 KiB |
|
After Width: | Height: | Size: 4.4 KiB |
Binary file not shown.
@ -0,0 +1,2 @@
|
||||
imagesdir = $(kde_datadir)/blinken/images
|
||||
images_DATA = blinken.png redh.png blueh.png greenh.png yellowh.png quit.png quit_hover.png menu.png menu_hover.png highscore.png highscore_hover.png mark.png
|
||||
|
After Width: | Height: | Size: 54 KiB |
|
After Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 785 B |
|
After Width: | Height: | Size: 1005 B |
|
After Width: | Height: | Size: 516 B |
|
After Width: | Height: | Size: 1.8 KiB |
|
After Width: | Height: | Size: 7.9 KiB |
|
After Width: | Height: | Size: 1.6 KiB |
|
After Width: | Height: | Size: 1.8 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -0,0 +1,2 @@
|
||||
soundsdir = $(kde_datadir)/blinken/sounds
|
||||
sounds_DATA = 1.wav 2.wav 3.wav 4.wav lose.wav
|
||||
Binary file not shown.
@ -0,0 +1,23 @@
|
||||
if include_ARTS
|
||||
artslib = -lartskde
|
||||
else
|
||||
artslib =
|
||||
endif
|
||||
|
||||
bin_PROGRAMS = blinken
|
||||
|
||||
INCLUDES = $(all_includes)
|
||||
|
||||
blinken_LDFLAGS = $(all_libraries) $(KDE_RPATH)
|
||||
blinken_LDADD = $(LIB_KDEUI) $(LIB_KIO) $(artslib)
|
||||
|
||||
blinken_SOURCES = main.cpp blinken.cpp artsplayer.cpp blinkengame.cpp number.cpp highscoredialog.cpp counter.cpp fontutils.cpp fontchecker.cpp button.cpp settings.kcfgc
|
||||
|
||||
METASOURCES = AUTO
|
||||
|
||||
xdg_apps_DATA = blinken.desktop
|
||||
|
||||
kde_kcfg_DATA = blinken.kcfg
|
||||
|
||||
messages: rc.cpp
|
||||
$(XGETTEXT) *.cpp -o $(podir)/blinken.pot
|
||||
@ -0,0 +1,147 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qtimer.h>
|
||||
|
||||
#include <config.h>
|
||||
|
||||
#ifdef WITHOUT_ARTS
|
||||
#include <klocale.h>
|
||||
#include <kmessagebox.h>
|
||||
#endif
|
||||
#include <kstandarddirs.h>
|
||||
|
||||
#include "artsplayer.h"
|
||||
#include "settings.h"
|
||||
|
||||
artsPlayer::artsPlayer() : m_playobj(0)
|
||||
{
|
||||
m_endChecker = new QTimer(this);
|
||||
connect(m_endChecker, SIGNAL(timeout()), this, SLOT(checkEnded()));
|
||||
|
||||
#ifndef WITHOUT_ARTS
|
||||
m_dispatcher = new KArtsDispatcher;
|
||||
m_server = new KArtsServer;
|
||||
m_factory = new KDE::PlayObjectFactory(m_server->server());
|
||||
|
||||
m_allPath = locate("appdata","sounds/lose.wav");
|
||||
m_greenPath = locate("appdata","sounds/1.wav");
|
||||
m_redPath = locate("appdata","sounds/2.wav");
|
||||
m_bluePath = locate("appdata","sounds/3.wav");
|
||||
m_yellowPath = locate("appdata","sounds/4.wav");
|
||||
#else
|
||||
KMessageBox::information(0, i18n("aRts was not found, therefore the sounds will be disabled."), i18n("Sounds Disabled"), "infoaboutartsnotfound");
|
||||
#endif
|
||||
}
|
||||
|
||||
artsPlayer::~artsPlayer()
|
||||
{
|
||||
#ifndef WITHOUT_ARTS
|
||||
delete m_playobj;
|
||||
delete m_factory;
|
||||
delete m_server;
|
||||
delete m_dispatcher;
|
||||
#endif
|
||||
}
|
||||
|
||||
void artsPlayer::play(blinkenGame::color c, bool stopCurrent)
|
||||
{
|
||||
int check;
|
||||
#ifndef WITHOUT_ARTS
|
||||
if (blinkenSettings::playSounds())
|
||||
{
|
||||
if (m_playobj && m_playobj -> state() == Arts::posPlaying)
|
||||
{
|
||||
if (stopCurrent)
|
||||
{
|
||||
m_nextSounds.clear();
|
||||
m_nextSounds.append(c);
|
||||
m_playobj -> halt();
|
||||
play();
|
||||
}
|
||||
else m_nextSounds.append(c);
|
||||
}
|
||||
else
|
||||
{
|
||||
m_nextSounds.append(c);
|
||||
play();
|
||||
}
|
||||
check = 50;
|
||||
}
|
||||
else check = 250;
|
||||
#else
|
||||
//shut up gcc
|
||||
(void)c;
|
||||
(void)stopCurrent;
|
||||
check = 250;
|
||||
#endif
|
||||
if (!m_endChecker -> isActive()) m_endChecker -> start(check);
|
||||
}
|
||||
|
||||
void artsPlayer::play()
|
||||
{
|
||||
#ifndef WITHOUT_ARTS
|
||||
QString path;
|
||||
blinkenGame::color c = m_nextSounds.first();
|
||||
m_nextSounds.pop_front();
|
||||
switch (c)
|
||||
{
|
||||
case blinkenGame::red:
|
||||
path = m_redPath;
|
||||
break;
|
||||
|
||||
case blinkenGame::green:
|
||||
path = m_greenPath;
|
||||
break;
|
||||
|
||||
case blinkenGame::blue:
|
||||
path = m_bluePath;
|
||||
break;
|
||||
|
||||
case blinkenGame::yellow:
|
||||
path = m_yellowPath;
|
||||
break;
|
||||
|
||||
case blinkenGame::all:
|
||||
path = m_allPath;
|
||||
break;
|
||||
|
||||
case blinkenGame::none:
|
||||
break;
|
||||
}
|
||||
delete m_playobj;
|
||||
m_playobj = m_factory -> createPlayObject(path, true);
|
||||
m_playobj -> play();
|
||||
#endif
|
||||
}
|
||||
|
||||
void artsPlayer::checkEnded()
|
||||
{
|
||||
#ifndef WITHOUT_ARTS
|
||||
if (blinkenSettings::playSounds())
|
||||
{
|
||||
if (m_playobj -> state() != Arts::posPlaying)
|
||||
{
|
||||
m_endChecker -> stop();
|
||||
emit ended();
|
||||
if (m_nextSounds.size() > 0) play();
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
m_endChecker -> stop();
|
||||
emit ended();
|
||||
}
|
||||
#else
|
||||
m_endChecker -> stop();
|
||||
emit ended();
|
||||
#endif
|
||||
}
|
||||
|
||||
#include "artsplayer.moc"
|
||||
@ -0,0 +1,66 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef ARTSPLAYER_H
|
||||
#define ARTSPLAYER_H
|
||||
|
||||
#include <config.h>
|
||||
|
||||
#ifdef WITHOUT_ARTS
|
||||
class KArtsDispatcher;
|
||||
class KArtsServer;
|
||||
|
||||
namespace KDE
|
||||
{
|
||||
class PlayObjectFactory;
|
||||
class PlayObject;
|
||||
}
|
||||
#else
|
||||
#include <arts/kartsdispatcher.h>
|
||||
#include <arts/kartsserver.h>
|
||||
#include <arts/kplayobject.h>
|
||||
#include <arts/kplayobjectfactory.h>
|
||||
#endif
|
||||
|
||||
#include <qvaluelist.h>
|
||||
|
||||
#include "blinkengame.h"
|
||||
|
||||
class QTimer;
|
||||
|
||||
class artsPlayer : public QObject
|
||||
{
|
||||
Q_OBJECT
|
||||
public:
|
||||
artsPlayer();
|
||||
~artsPlayer();
|
||||
|
||||
void play(blinkenGame::color c, bool stopCurrent = false);
|
||||
|
||||
signals:
|
||||
void ended();
|
||||
|
||||
private slots:
|
||||
void play();
|
||||
void checkEnded();
|
||||
|
||||
private:
|
||||
QValueList<blinkenGame::color> m_nextSounds;
|
||||
|
||||
QString m_greenPath, m_redPath, m_bluePath, m_yellowPath, m_allPath;
|
||||
|
||||
QTimer *m_endChecker;
|
||||
|
||||
KArtsDispatcher *m_dispatcher;
|
||||
KArtsServer *m_server;
|
||||
KDE::PlayObjectFactory *m_factory;
|
||||
KDE::PlayObject *m_playobj;
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,855 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qcursor.h>
|
||||
#include <qpainter.h>
|
||||
#include <qpixmap.h>
|
||||
#include <qtimer.h>
|
||||
|
||||
#include <kaction.h>
|
||||
#include <kapplication.h>
|
||||
#include <kconfig.h>
|
||||
#include <khelpmenu.h>
|
||||
#include <kinputdialog.h>
|
||||
#include <klocale.h>
|
||||
#include <kmessagebox.h>
|
||||
#include <kpopupmenu.h>
|
||||
#include <kstandarddirs.h>
|
||||
|
||||
#include "blinken.h"
|
||||
#include "button.h"
|
||||
#include "counter.h"
|
||||
#include "fontutils.h"
|
||||
#include "number.h"
|
||||
#include "highscoredialog.h"
|
||||
#include "settings.h"
|
||||
|
||||
blinken::blinken() : QWidget(0, 0, WStaticContents | WNoAutoErase), m_overHighscore(false), m_overQuit(false), m_overCentralText(false), m_overMenu(false), m_overAboutKDE(false), m_overAboutBlinken(false), m_overManual(false), m_overCentralLetters(false), m_overCounter(false), m_overFont(false), m_overSound(false), m_showPreferences(false), m_updateButtonHighlighting(false), m_highlighted(blinkenGame::none)
|
||||
{
|
||||
m_back = new QPixmap(locate("appdata", "images/blinken.png"));
|
||||
|
||||
m_buttons[0] = new button(blinkenGame::blue);
|
||||
m_buttons[1] = new button(blinkenGame::yellow);
|
||||
m_buttons[2] = new button(blinkenGame::red);
|
||||
m_buttons[3] = new button(blinkenGame::green);
|
||||
|
||||
m_highscore = new QPixmap(locate("appdata", "images/highscore.png"));
|
||||
m_highscoreHover = new QPixmap(locate("appdata", "images/highscore_hover.png"));
|
||||
m_quit = new QPixmap(locate("appdata", "images/quit.png"));
|
||||
m_quitHover = new QPixmap(locate("appdata", "images/quit_hover.png"));
|
||||
m_menu = new QPixmap(locate("appdata", "images/menu.png"));
|
||||
m_menuHover = new QPixmap(locate("appdata", "images/menu_hover.png"));
|
||||
m_mark = new QPixmap(locate("appdata", "images/mark.png"));
|
||||
m_highscoreRect = QRect(10, 10, 72, 72);
|
||||
m_quitRect = QRect(562, 10, 72, 73);
|
||||
m_menuRect = QRect(562, 443, 72, 72);
|
||||
m_aboutKDERect = QRect(452, 461, 54, 54);
|
||||
m_aboutBlinkenRect = QRect(506, 461, 56, 54);
|
||||
m_manualRect = QRect(578, 389, 54, 54);
|
||||
m_centralLettersRect = QRect(192, 194, 254, 54);
|
||||
m_counterRect = QRect(268, 110, 102, 52);
|
||||
|
||||
m_fillColor = QColor(40, 40, 40);
|
||||
m_fontColor = QColor(126, 126, 126);
|
||||
m_fontHighlightColor = QColor(230, 230, 230);
|
||||
m_countDownColor = QColor(55, 55, 55);
|
||||
|
||||
setMouseTracking(true);
|
||||
setFixedSize(644, 525);
|
||||
show();
|
||||
|
||||
m_unhighlighter = new QTimer(this);
|
||||
connect(m_unhighlighter, SIGNAL(timeout()), this, SLOT(unhighlight()));
|
||||
|
||||
connect(&m_game, SIGNAL(gameEnded()), this, SLOT(checkHS()));
|
||||
connect(&m_game, SIGNAL(phaseChanged()), this, SLOT(update()));
|
||||
connect(&m_game, SIGNAL(highlight(blinkenGame::color, bool)), this, SLOT(highlight(blinkenGame::color, bool)));
|
||||
|
||||
m_helpMenu = new KHelpMenu(this, kapp->aboutData());
|
||||
|
||||
for (int i = 0; i < 3; i++) m_overLevels[i] = false;
|
||||
|
||||
QString aux = i18n("If the Steve font that is used by bliken by default to show status messages does not support any of the characters of your language, please translate that message to 1 and KDE standard font will be used to show the texts, if not translate it to 0", "0");
|
||||
|
||||
m_alwaysUseNonCoolFont = aux == "1";
|
||||
}
|
||||
|
||||
blinken::~blinken()
|
||||
{
|
||||
delete m_back;
|
||||
for (int i = 0; i < 4; i++) delete m_buttons[i];
|
||||
delete m_highscore;
|
||||
delete m_highscoreHover;
|
||||
delete m_quit;
|
||||
delete m_quitHover;
|
||||
delete m_menu;
|
||||
delete m_menuHover;
|
||||
delete m_mark;
|
||||
delete m_helpMenu;
|
||||
}
|
||||
|
||||
void blinken::paintEvent(QPaintEvent *)
|
||||
{
|
||||
QPixmap buf(width(), height());
|
||||
QPainter p(&buf);
|
||||
|
||||
p.drawPixmap(0, 0, *m_back);
|
||||
|
||||
drawMenuQuit(p);
|
||||
QFont f1, f = p.font();
|
||||
f1 = f;
|
||||
f.setBold(true);
|
||||
p.setFont(f);
|
||||
switch (m_game.phase())
|
||||
{
|
||||
case blinkenGame::starting:
|
||||
drawText(p, i18n("Start"), QPoint(318, 316), true, 10, 5, &m_centralTextRect, m_overCentralText, false);
|
||||
break;
|
||||
|
||||
case blinkenGame::choosingLevel:
|
||||
drawLevel(p);
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting3:
|
||||
case blinkenGame::waiting2:
|
||||
case blinkenGame::waiting1:
|
||||
case blinkenGame::learningTheSequence:
|
||||
case blinkenGame::typingTheSequence:
|
||||
drawText(p, i18n("Restart"), QPoint(318, 316), true, 10, 5, &m_centralTextRect, m_overCentralText, false);
|
||||
break;
|
||||
}
|
||||
p.setFont(f1);
|
||||
|
||||
if (m_showPreferences)
|
||||
{
|
||||
// draw the current keys
|
||||
drawText(p, m_buttons[0]->shortcut(), QPoint(115, 285), true, 20, 5, 0, m_buttons[0]->selected(), false);
|
||||
drawText(p, m_buttons[1]->shortcut(), QPoint(115, 155), true, 20, 5, 0, m_buttons[1]->selected(), false);
|
||||
drawText(p, m_buttons[2]->shortcut(), QPoint(520, 155), true, 20, 5, 0, m_buttons[2]->selected(), false);
|
||||
drawText(p, m_buttons[3]->shortcut(), QPoint(520, 285), true, 20, 5, 0, m_buttons[3]->selected(), false);
|
||||
|
||||
const QPen &oPen = p.pen();
|
||||
const QBrush &oBrush = p.brush();
|
||||
const QFont &oFont = p.font();
|
||||
|
||||
// draw the internal square plus a bit of ellipse on the sides and the
|
||||
// two delimiter lines
|
||||
p.setPen(NoPen);
|
||||
p.setBrush(m_fillColor);
|
||||
p.drawPie(169, 192, 4, 58, 1440, 2880);
|
||||
p.drawPie(465, 192, 4, 58, -1440, 2880);
|
||||
p.setPen(QPen(Qt::black, 3));
|
||||
p.fillRect(171, 192, 296, 58, m_fillColor);
|
||||
p.drawLine(169, 192, 469, 192);
|
||||
p.drawLine(169, 250, 469, 250);
|
||||
|
||||
// draw the two squares of the options
|
||||
p.setPen(QPen(m_fontColor, 2, Qt::SolidLine, Qt::SquareCap, Qt::MiterJoin));
|
||||
|
||||
m_soundRect = QRect(181, 209, 25, 25);
|
||||
m_fontRect = QRect(432, 209, 25, 25);
|
||||
#ifndef WITHOUT_ARTS
|
||||
p.drawRect(m_soundRect);
|
||||
if (blinkenSettings::playSounds())
|
||||
{
|
||||
p.drawLine(186, 214, 199, 227);
|
||||
p.drawLine(186, 227, 199, 214);
|
||||
}
|
||||
#endif
|
||||
if (!m_alwaysUseNonCoolFont)
|
||||
{
|
||||
p.drawRect(m_fontRect);
|
||||
if (blinkenSettings::customFont())
|
||||
{
|
||||
p.drawLine(437, 214, 450, 227);
|
||||
p.drawLine(437, 227, 450, 214);
|
||||
}
|
||||
}
|
||||
|
||||
// draw the options' text
|
||||
QFont f1 = QFont();
|
||||
p.setFont(f1);
|
||||
int size, sizeAux;
|
||||
QRect area;
|
||||
QString sounds = i18n("Sounds");
|
||||
QString font = i18n("Font");
|
||||
size = fontUtils::fontSize(p, sounds, 95, 20);
|
||||
sizeAux = fontUtils::fontSize(p, font, 95, 20);
|
||||
if (sizeAux > size) size = sizeAux;
|
||||
f1.setPointSize(size);
|
||||
#ifndef WITHOUT_ARTS
|
||||
area = p.boundingRect(QRect(), Qt::AlignAuto, sounds);
|
||||
area.moveBy(212, 221 - (area.height() / 2));
|
||||
p.drawText(area, Qt::AlignCenter, sounds);
|
||||
m_soundRect = m_soundRect.unite(area);
|
||||
#endif
|
||||
if (!m_alwaysUseNonCoolFont)
|
||||
{
|
||||
area = p.boundingRect(QRect(), Qt::AlignAuto, font);
|
||||
area.moveBy(426 - area.width(), 221 - (area.height() / 2));
|
||||
p.drawText(area, Qt::AlignCenter, font);
|
||||
m_fontRect = m_fontRect.unite(area);
|
||||
}
|
||||
|
||||
p.setFont(oFont);
|
||||
p.setPen(oPen);
|
||||
p.setBrush(oBrush);
|
||||
}
|
||||
|
||||
drawScoreAndCounter(p);
|
||||
|
||||
if (m_highlighted & blinkenGame::blue) p.drawPixmap(14, 225, *m_buttons[0] -> pixmap());
|
||||
if (m_highlighted & blinkenGame::yellow) p.drawPixmap(14, 16, *m_buttons[1] -> pixmap());
|
||||
if (m_highlighted & blinkenGame::red) p.drawPixmap(322, 16, *m_buttons[2] -> pixmap());
|
||||
if (m_highlighted & blinkenGame::green) p.drawPixmap(322, 225, *m_buttons[3] -> pixmap());
|
||||
|
||||
drawStatusText(p);
|
||||
|
||||
bitBlt(this, 0, 0, &buf);
|
||||
|
||||
if (m_updateButtonHighlighting) updateButtonHighlighting(mapFromGlobal(QCursor::pos()));
|
||||
}
|
||||
|
||||
void blinken::keyPressEvent(QKeyEvent *e)
|
||||
{
|
||||
if (e -> isAutoRepeat()) return;
|
||||
|
||||
if (m_showPreferences)
|
||||
{
|
||||
int i = 0;
|
||||
while (i < 4 && !m_buttons[i] -> selected()) i++;
|
||||
|
||||
if (i < 4)
|
||||
{
|
||||
if (e -> key() == Qt::Key_Escape)
|
||||
{
|
||||
m_buttons[i] -> setSelected(false);
|
||||
update();
|
||||
}
|
||||
else
|
||||
{
|
||||
KShortcut ks(e -> key());
|
||||
if (!ks.toString().isEmpty())
|
||||
{
|
||||
bool different = true;
|
||||
int j = 0;
|
||||
while (different && j < 4)
|
||||
{
|
||||
different = (ks.toString() != m_buttons[j] -> shortcut());
|
||||
j++;
|
||||
}
|
||||
|
||||
if (different)
|
||||
{
|
||||
m_buttons[i] -> setShortcut(ks);
|
||||
update();
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
if (e -> key() == m_buttons[0] -> key()) pressedBlue();
|
||||
else if (e -> key() == m_buttons[1] -> key()) pressedYellow();
|
||||
else if (e -> key() == m_buttons[2] -> key()) pressedRed();
|
||||
else if (e -> key() == m_buttons[3] -> key()) pressedGreen();
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::keyReleaseEvent(QKeyEvent *e)
|
||||
{
|
||||
if (e -> isAutoRepeat()) return;
|
||||
|
||||
if (e -> state() == Qt::ControlButton && e -> stateAfter() != Qt::ControlButton && (m_game.phase() == blinkenGame::starting || m_game.phase() == blinkenGame::choosingLevel))
|
||||
{
|
||||
m_showPreferences = !m_showPreferences;
|
||||
for (int i = 0; i < 4; i++) m_buttons[i] -> setSelected(false);
|
||||
updateButtonHighlighting(mapFromGlobal(QCursor::pos()));
|
||||
update();
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::mouseMoveEvent(QMouseEvent *e)
|
||||
{
|
||||
updateButtonHighlighting(e->pos());
|
||||
}
|
||||
|
||||
void blinken::mousePressEvent(QMouseEvent *e)
|
||||
{
|
||||
if (m_overHighscore || m_overCounter)
|
||||
{
|
||||
highScoreDialog *hsd = new highScoreDialog(this);
|
||||
hsd->showLevel(1);
|
||||
m_updateButtonHighlighting = true;
|
||||
}
|
||||
else if (m_showPreferences && m_fontRect.contains(e -> pos()) && !m_alwaysUseNonCoolFont)
|
||||
{
|
||||
blinkenSettings::setCustomFont(!blinkenSettings::customFont());
|
||||
blinkenSettings::writeConfig();
|
||||
update();
|
||||
}
|
||||
else if (m_showPreferences && m_soundRect.contains(e -> pos()))
|
||||
{
|
||||
blinkenSettings::setPlaySounds(!blinkenSettings::playSounds());
|
||||
blinkenSettings::writeConfig();
|
||||
update();
|
||||
}
|
||||
else if (m_overQuit) kapp->quit();
|
||||
else if (m_overAboutBlinken || m_overCentralLetters) m_helpMenu -> aboutApplication();
|
||||
else if (m_overAboutKDE) m_helpMenu -> aboutKDE();
|
||||
else if (m_overManual) m_helpMenu -> appHelpActivated();
|
||||
else if (m_game.phase() != blinkenGame::choosingLevel && m_overCentralText)
|
||||
{
|
||||
highlight(blinkenGame::none, true);
|
||||
m_overCentralText = false;
|
||||
for(int i = 0; i < 3; i++) m_overLevels[i] = false;
|
||||
m_game.setPhase(blinkenGame::choosingLevel);
|
||||
m_updateButtonHighlighting = true;
|
||||
}
|
||||
else if (m_game.phase() == blinkenGame::choosingLevel)
|
||||
{
|
||||
int level = 0;
|
||||
if (m_levelsRect[1].contains(e -> pos())) level = 1;
|
||||
else if (m_levelsRect[0].contains(e -> pos())) level = 2;
|
||||
else if (m_levelsRect[2].contains(e -> pos())) level = 3;
|
||||
if (level)
|
||||
{
|
||||
for(int i = 0; i < 3; i++) m_overLevels[i] = false;
|
||||
m_game.start(level);
|
||||
if (m_showPreferences) m_showPreferences = false;
|
||||
m_updateButtonHighlighting = true;
|
||||
}
|
||||
}
|
||||
|
||||
QPoint p = e->pos();
|
||||
p -= QPoint(319, 221);
|
||||
if (insideGreen(p))
|
||||
{
|
||||
if (m_showPreferences) selectButton(3);
|
||||
else pressedGreen();
|
||||
}
|
||||
else if (insideBlue(p))
|
||||
{
|
||||
if (m_showPreferences) selectButton(0);
|
||||
else pressedBlue();
|
||||
}
|
||||
else if (insideYellow(p))
|
||||
{
|
||||
if (m_showPreferences) selectButton(1);
|
||||
else pressedYellow();
|
||||
}
|
||||
else if (insideRed(p))
|
||||
{
|
||||
if (m_showPreferences) selectButton(2);
|
||||
else pressedRed();
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::checkHS()
|
||||
{
|
||||
highScoreDialog *hsd = new highScoreDialog(this);
|
||||
if (hsd->scoreGoodEnough(m_game.level(), m_game.score()))
|
||||
{
|
||||
bool ok;
|
||||
QString name = KInputDialog::getText(i18n("Enter Your Name"), i18n("Name:"), m_lastName, &ok);
|
||||
if (!name.isNull() && ok)
|
||||
{
|
||||
m_lastName = name;
|
||||
hsd->addScore(m_game.level(), m_game.score(), name);
|
||||
}
|
||||
hsd->showLevel(m_game.level());
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::highlight(blinkenGame::color c, bool unhighlight)
|
||||
{
|
||||
m_highlighted = c;
|
||||
update();
|
||||
if (unhighlight) m_unhighlighter -> start(250);
|
||||
else if (c == blinkenGame::none)
|
||||
{
|
||||
m_unhighlighter -> stop();
|
||||
updateCursor(mapFromGlobal(QCursor::pos()));
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::unhighlight()
|
||||
{
|
||||
highlight(blinkenGame::none, false);
|
||||
}
|
||||
|
||||
void blinken::pressedYellow()
|
||||
{
|
||||
if (m_game.canType())
|
||||
{
|
||||
highlight(blinkenGame::yellow, true);
|
||||
m_game.clicked(blinkenGame::yellow);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::pressedRed()
|
||||
{
|
||||
if (m_game.canType())
|
||||
{
|
||||
highlight(blinkenGame::red, true);
|
||||
m_game.clicked(blinkenGame::red);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::pressedGreen()
|
||||
{
|
||||
if (m_game.canType())
|
||||
{
|
||||
highlight(blinkenGame::green, true);
|
||||
m_game.clicked(blinkenGame::green);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::pressedBlue()
|
||||
{
|
||||
if (m_game.canType())
|
||||
{
|
||||
highlight(blinkenGame::blue, true);
|
||||
m_game.clicked(blinkenGame::blue);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::selectButton(int button)
|
||||
{
|
||||
int i = 0;
|
||||
bool selected = false;
|
||||
while (i < 4 && !selected)
|
||||
{
|
||||
selected = m_buttons[i] -> selected();
|
||||
if (!selected) i++;
|
||||
}
|
||||
|
||||
if (selected)
|
||||
{
|
||||
if (i == button)
|
||||
{
|
||||
m_buttons[button] -> setSelected(false);
|
||||
update();
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
m_buttons[button] -> setSelected(true);
|
||||
update();
|
||||
}
|
||||
}
|
||||
|
||||
bool blinken::insideGreen(const QPoint &p) const
|
||||
{
|
||||
return insideButtonsArea(p) && p.x() > 6 && p.y() > 6;
|
||||
}
|
||||
|
||||
bool blinken::insideBlue(const QPoint &p) const
|
||||
{
|
||||
return insideButtonsArea(p) && p.x() < -6 && p.y() > 6;
|
||||
}
|
||||
|
||||
bool blinken::insideYellow(const QPoint &p) const
|
||||
{
|
||||
return insideButtonsArea(p) && p.x() < -6 && p.y() < -6;
|
||||
}
|
||||
|
||||
bool blinken::insideRed(const QPoint &p) const
|
||||
{
|
||||
return insideButtonsArea(p) && p.x() > 6 && p.y() < -6;
|
||||
}
|
||||
|
||||
bool blinken::insideButtonsArea(const QPoint &p) const
|
||||
{
|
||||
double x, y, x2, y2;
|
||||
x = (double)p.x();
|
||||
y = (double)p.y();
|
||||
x2 = x * x;
|
||||
y2 = y * y;
|
||||
if (x2 + y2 > 162.5 * 162.5)
|
||||
{
|
||||
// Outside the circle
|
||||
double x3, y3;
|
||||
x3 = x2 / (301 * 301);
|
||||
y3 = y2 / (201 * 201);
|
||||
if (x3 + y3 < 1) return true;
|
||||
}
|
||||
return false;
|
||||
}
|
||||
|
||||
void blinken::drawMenuQuit(QPainter &p)
|
||||
{
|
||||
if (!m_overHighscore) p.drawPixmap(10, 10, *m_highscore);
|
||||
else p.drawPixmap(10, 10, *m_highscoreHover);
|
||||
|
||||
if (!m_overQuit) p.drawPixmap(562, 10, *m_quit);
|
||||
else p.drawPixmap(562, 10, *m_quitHover);
|
||||
|
||||
if (!m_overMenu) p.drawPixmap(562, 443, *m_menu);
|
||||
else p.drawPixmap(454, 389, *m_menuHover);
|
||||
|
||||
if (m_overAboutKDE) p.drawPixmap(462, 433, *m_mark);
|
||||
else if (m_overAboutBlinken) p.drawPixmap(516, 433, *m_mark);
|
||||
else if (m_overManual)
|
||||
{
|
||||
p.translate(550, 430);
|
||||
p.rotate(-90.0);
|
||||
p.drawPixmap(0, 0, *m_mark);
|
||||
p.rotate(90.0);
|
||||
p.translate(-550, -430);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::drawScoreAndCounter(QPainter &p)
|
||||
{
|
||||
QColor c1, c2, c3;
|
||||
p.translate(268, 110);
|
||||
|
||||
switch (m_game.phase())
|
||||
{
|
||||
case blinkenGame::waiting3:
|
||||
c1 = red;
|
||||
c2 = red;
|
||||
c3 = red;
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting2:
|
||||
c1 = m_countDownColor;
|
||||
c2 = red;
|
||||
c3 = red;
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting1:
|
||||
c1 = m_countDownColor;
|
||||
c2 = c1;
|
||||
c3 = red;
|
||||
break;
|
||||
|
||||
default:
|
||||
c1 = m_countDownColor;
|
||||
c2 = c1;
|
||||
c3 = c1;
|
||||
break;
|
||||
}
|
||||
|
||||
counter::paint(p, m_game.phase() != blinkenGame::starting, m_game.score(), true, c1, c2, c3);
|
||||
|
||||
p.translate(-268, -110);
|
||||
}
|
||||
|
||||
void blinken::drawStatusText(QPainter &p)
|
||||
{
|
||||
p.translate(25, 505);
|
||||
p.rotate(-3.29);
|
||||
p.setPen(blue);
|
||||
|
||||
QString restartText = i18n("Restart the game");
|
||||
QString text;
|
||||
if (m_overQuit) text = i18n("Quit blinKen");
|
||||
else if (m_overHighscore || m_overCounter) text = i18n("View Highscore Table");
|
||||
else if (m_overAboutBlinken || m_overCentralLetters) text = m_helpMenu -> menu() -> text(KHelpMenu::menuAboutApp).remove("&");
|
||||
else if (m_overAboutKDE) text = m_helpMenu -> menu() -> text(KHelpMenu::menuAboutKDE).remove("&");
|
||||
else if (m_overManual) text = m_helpMenu -> menu() -> text(KHelpMenu::menuHelpContents).remove("&");
|
||||
else if (m_overLevels[0]) text = i18n("2nd Level");
|
||||
else if (m_overLevels[1]) text = i18n("1st Level");
|
||||
else if (m_overLevels[2]) text = i18n("Random Level");
|
||||
else if (m_buttons[0]->selected() || m_buttons[1]->selected() || m_buttons[2]->selected() || m_buttons[3]->selected()) text = i18n("Press the key for this button");
|
||||
else if (m_showPreferences) text = i18n("Click any button to change its key");
|
||||
else
|
||||
{
|
||||
switch (m_game.phase())
|
||||
{
|
||||
case blinkenGame::starting:
|
||||
text = i18n("Press Start to begin!");
|
||||
break;
|
||||
|
||||
case blinkenGame::choosingLevel:
|
||||
text = i18n("Set the Difficulty Level...");
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting3:
|
||||
if (m_overCentralText) text = restartText;
|
||||
else text = i18n("Next sequence in 3...");
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting2:
|
||||
if (m_overCentralText) text = restartText;
|
||||
else if (m_game.level() == 1) text = i18n("Next sequence in 3, 2...");
|
||||
else text = i18n("Next sequence in 2...");
|
||||
break;
|
||||
|
||||
case blinkenGame::waiting1:
|
||||
if (m_overCentralText) text = restartText;
|
||||
else if (m_game.level() == 1) text = i18n("Next sequence in 3, 2, 1...");
|
||||
else text = i18n("Next sequence in 2, 1...");
|
||||
break;
|
||||
|
||||
case blinkenGame::learningTheSequence:
|
||||
if (m_overCentralText) text = restartText;
|
||||
else text = i18n("Remember this sequence...");
|
||||
break;
|
||||
|
||||
case blinkenGame::typingTheSequence:
|
||||
if (m_overCentralText) text = restartText;
|
||||
else text = i18n("Repeat the sequence!");
|
||||
break;
|
||||
}
|
||||
}
|
||||
|
||||
QFont f;
|
||||
if (blinkenSettings::customFont() && !m_alwaysUseNonCoolFont) f = QFont("Steve");
|
||||
p.setFont(f);
|
||||
f.setPointSize(fontUtils::fontSize(p, text, 380, 30));
|
||||
p.setFont(f);
|
||||
p.drawText(0, 0, text);
|
||||
}
|
||||
|
||||
void blinken::drawLevel(QPainter &p)
|
||||
{
|
||||
QString n[3];
|
||||
n[0] = i18n("2");
|
||||
n[1] = i18n("1");
|
||||
n[2] = i18n("?");
|
||||
|
||||
drawText(p, i18n("Level"), QPoint(322, 281), false, 0, 0, 0, false, true);
|
||||
|
||||
QPoint cp;
|
||||
for (int i = 0; i < 3; i++)
|
||||
{
|
||||
if (i == 0) cp = QPoint(319, 315);
|
||||
else if (i == 1) cp = QPoint(m_levelsRect[0].left() - m_levelsRect[0].width(), 315);
|
||||
else if (i == 2) cp = QPoint(m_levelsRect[0].right() + m_levelsRect[0].width(), 315);
|
||||
drawText(p, n[i], cp, true, 20, 5, &(m_levelsRect[i]), m_overLevels[i], true);
|
||||
}
|
||||
}
|
||||
|
||||
void blinken::drawText(QPainter &p, const QString &text, const QPoint ¢er, bool withMargin, int xMargin, int yMargin, QRect *rect, bool highlight, bool bold)
|
||||
{
|
||||
QRect r;
|
||||
QFont oldFont, f = p.font();
|
||||
oldFont = f;
|
||||
f.setPointSize(fontUtils::fontSize(p, text, 190, 30));
|
||||
if (bold) f.setBold(true);
|
||||
p.setFont(f);
|
||||
|
||||
r = p.boundingRect(QRect(), Qt::AlignAuto, text);
|
||||
r = QRect(0, 0, r.width() + xMargin, r.height() + yMargin);
|
||||
r.moveBy(center.x() - r.width() / 2, center.y() - r.height() / 2);
|
||||
|
||||
if (withMargin)
|
||||
{
|
||||
p.fillRect(r, m_fillColor);
|
||||
p.setPen(QPen(black, 3));
|
||||
p.drawRoundRect(r.left(), r.top(), r.width(), r.height(), 15, 15);
|
||||
}
|
||||
|
||||
if (!highlight) p.setPen(m_fontColor);
|
||||
else p.setPen(m_fontHighlightColor);
|
||||
p.drawText(r, Qt::AlignCenter, text);
|
||||
|
||||
if (rect) *rect = r;
|
||||
p.setFont(oldFont);
|
||||
}
|
||||
|
||||
|
||||
void blinken::updateButtonHighlighting(const QPoint &p)
|
||||
{
|
||||
bool haveToUpdate;
|
||||
m_updateButtonHighlighting = false;
|
||||
haveToUpdate = false;
|
||||
|
||||
if (m_highscoreRect.contains(p))
|
||||
{
|
||||
if (!m_overHighscore)
|
||||
{
|
||||
m_overHighscore = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_overHighscore)
|
||||
{
|
||||
m_overHighscore = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
if (m_menuRect.contains(p))
|
||||
{
|
||||
if (!m_overMenu)
|
||||
{
|
||||
m_overMenu = true;
|
||||
m_overAboutKDE = false;
|
||||
m_overAboutBlinken = false;
|
||||
m_overManual = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
else if (m_overAboutKDE || m_overAboutBlinken || m_overManual)
|
||||
{
|
||||
m_overAboutKDE = false;
|
||||
m_overAboutBlinken = false;
|
||||
m_overManual = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_overMenu)
|
||||
{
|
||||
if (m_aboutKDERect.contains(p))
|
||||
{
|
||||
if (!m_overAboutKDE)
|
||||
{
|
||||
m_overAboutKDE = true;
|
||||
m_overAboutBlinken = false;
|
||||
m_overManual = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_aboutBlinkenRect.contains(p))
|
||||
{
|
||||
if (!m_overAboutBlinken)
|
||||
{
|
||||
m_overAboutKDE = false;
|
||||
m_overAboutBlinken = true;
|
||||
m_overManual = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_manualRect.contains(p))
|
||||
{
|
||||
if (!m_overManual)
|
||||
{
|
||||
m_overAboutKDE = false;
|
||||
m_overAboutBlinken = false;
|
||||
m_overManual = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
m_overMenu = false;
|
||||
m_overAboutKDE = false;
|
||||
m_overAboutBlinken = false;
|
||||
m_overManual = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
|
||||
if (!m_showPreferences && m_centralLettersRect.contains(p))
|
||||
{
|
||||
m_overCentralLetters = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
else if (m_overCentralLetters)
|
||||
{
|
||||
m_overCentralLetters = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
if (m_showPreferences && m_soundRect.contains(p))
|
||||
{
|
||||
m_overSound = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
else if (m_overSound)
|
||||
{
|
||||
m_overSound = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
if (m_showPreferences && m_fontRect.contains(p) && !m_alwaysUseNonCoolFont)
|
||||
{
|
||||
m_overFont = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
else if (m_overFont)
|
||||
{
|
||||
m_overFont = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
if (m_counterRect.contains(p))
|
||||
{
|
||||
m_overCounter = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
else if (m_overCounter)
|
||||
{
|
||||
m_overCounter = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
if (m_quitRect.contains(p))
|
||||
{
|
||||
if (!m_overQuit)
|
||||
{
|
||||
m_overQuit = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_overQuit)
|
||||
{
|
||||
m_overQuit = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
|
||||
switch (m_game.phase())
|
||||
{
|
||||
case blinkenGame::starting:
|
||||
case blinkenGame::waiting3:
|
||||
case blinkenGame::waiting2:
|
||||
case blinkenGame::waiting1:
|
||||
case blinkenGame::learningTheSequence:
|
||||
case blinkenGame::typingTheSequence:
|
||||
if (m_centralTextRect.contains(p))
|
||||
{
|
||||
if (!m_overCentralText)
|
||||
{
|
||||
m_overCentralText = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_overCentralText)
|
||||
{
|
||||
m_overCentralText = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
break;
|
||||
|
||||
case blinkenGame::choosingLevel:
|
||||
for (int i = 0; i < 3; i++)
|
||||
{
|
||||
if (m_levelsRect[i].contains(p))
|
||||
{
|
||||
if (!m_overLevels[i])
|
||||
{
|
||||
m_overLevels[i] = true;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
else if (m_overLevels[i])
|
||||
{
|
||||
m_overLevels[i] = false;
|
||||
haveToUpdate = true;
|
||||
}
|
||||
}
|
||||
break;
|
||||
}
|
||||
|
||||
updateCursor(p);
|
||||
if (haveToUpdate) update();
|
||||
}
|
||||
|
||||
void blinken::updateCursor(const QPoint &p)
|
||||
{
|
||||
QPoint p2 = p - QPoint(319, 221);
|
||||
|
||||
if (m_overHighscore || m_overQuit || m_overCentralText || m_overMenu || m_overAboutKDE || m_overAboutBlinken || m_overManual || m_overLevels[0] || m_overLevels[1] || m_overLevels[2] || m_overCentralLetters || m_overCounter || (m_game.canType() && (insideGreen(p2) || insideRed(p2) || insideBlue(p2) || insideYellow(p2))) || m_overFont || m_overSound) setCursor(PointingHandCursor);
|
||||
else setCursor(ArrowCursor);
|
||||
}
|
||||
|
||||
#include "blinken.moc"
|
||||
@ -0,0 +1,92 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef BLINKEN_H
|
||||
#define BLINKEN_H
|
||||
|
||||
#include <qwidget.h>
|
||||
|
||||
#include "blinkengame.h"
|
||||
|
||||
class QTimer;
|
||||
|
||||
class KAction;
|
||||
class KHelpMenu;
|
||||
|
||||
class button;
|
||||
class highScoreDialog;
|
||||
|
||||
class blinken : public QWidget
|
||||
{
|
||||
Q_OBJECT
|
||||
public:
|
||||
blinken();
|
||||
~blinken();
|
||||
|
||||
protected:
|
||||
void paintEvent(QPaintEvent *);
|
||||
void mouseMoveEvent(QMouseEvent *e);
|
||||
void mousePressEvent(QMouseEvent *e);
|
||||
void keyPressEvent(QKeyEvent *e);
|
||||
void keyReleaseEvent(QKeyEvent *e);
|
||||
|
||||
private slots:
|
||||
void checkHS();
|
||||
void highlight(blinkenGame::color c, bool unhighlight);
|
||||
void unhighlight();
|
||||
|
||||
void pressedYellow();
|
||||
void pressedRed();
|
||||
void pressedGreen();
|
||||
void pressedBlue();
|
||||
|
||||
private:
|
||||
void selectButton(int button);
|
||||
bool insideGreen(const QPoint &p) const;
|
||||
bool insideYellow(const QPoint &p) const;
|
||||
bool insideRed(const QPoint &p) const;
|
||||
bool insideBlue(const QPoint &p) const;
|
||||
bool insideButtonsArea(const QPoint &p) const;
|
||||
void updateCursor(const QPoint &p);
|
||||
|
||||
void drawMenuQuit(QPainter &p);
|
||||
void drawScoreAndCounter(QPainter &p);
|
||||
void drawStatusText(QPainter &p);
|
||||
void drawLevel(QPainter &p);
|
||||
void drawText(QPainter &p, const QString &text, const QPoint ¢er, bool withMargin, int xMargin, int yMargin, QRect *rect, bool highlight, bool bold);
|
||||
void updateButtonHighlighting(const QPoint &p);
|
||||
|
||||
|
||||
button *m_buttons[4];
|
||||
QPixmap *m_back, *m_highscore, *m_highscoreHover, *m_quit, *m_quitHover, *m_menu, *m_menuHover, *m_mark;
|
||||
bool m_overHighscore, m_overQuit, m_overCentralText, m_overMenu, m_overAboutKDE, m_overAboutBlinken, m_overManual, m_overLevels[3], m_overCentralLetters, m_overCounter, m_overFont, m_overSound;
|
||||
// i obviously suck but m_levelsRect[0] is 2, m_levelsRect[1] is 1 and m_levelsRect[3] is ?
|
||||
QRect m_highscoreRect, m_quitRect, m_centralTextRect, m_menuRect, m_aboutKDERect, m_aboutBlinkenRect, m_manualRect, m_levelsRect[3], m_centralLettersRect, m_counterRect, m_soundRect, m_fontRect;
|
||||
QColor m_fillColor, m_fontColor, m_fontHighlightColor, m_countDownColor;
|
||||
|
||||
// Preferences setting handling
|
||||
bool m_showPreferences;
|
||||
|
||||
// if should update the highlighting after the next repaint
|
||||
bool m_updateButtonHighlighting;
|
||||
|
||||
// use always the non-cool font?
|
||||
bool m_alwaysUseNonCoolFont;
|
||||
|
||||
blinkenGame::color m_highlighted;
|
||||
QTimer *m_unhighlighter;
|
||||
|
||||
QString m_lastName;
|
||||
|
||||
blinkenGame m_game;
|
||||
|
||||
KHelpMenu *m_helpMenu;
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,18 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<kcfg xmlns="http://www.kde.org/standards/kcfg/1.0"
|
||||
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
||||
xsi:schemaLocation="http://www.kde.org/standards/kcfg/1.0
|
||||
http://www.kde.org/standards/kcfg/1.0/kcfg.xsd" >
|
||||
<kcfgfile name="blinkenrc"/>
|
||||
<group name="general">
|
||||
<entry name="playSounds" type="Bool">
|
||||
<label>Play sounds</label>
|
||||
<default>true</default>
|
||||
</entry>
|
||||
<entry name="customFont" type="Bool">
|
||||
<label>Use custom font for status text</label>
|
||||
<default>true</default>
|
||||
</entry>
|
||||
</group>
|
||||
</kcfg>
|
||||
|
||||
@ -0,0 +1,181 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <stdlib.h> // for RAND_MAX
|
||||
|
||||
#include <qtimer.h>
|
||||
|
||||
#include <kapplication.h>
|
||||
|
||||
#include "artsplayer.h"
|
||||
#include "blinkengame.h"
|
||||
|
||||
blinkenGame::blinkenGame() : m_phase(starting)
|
||||
{
|
||||
m_artsPlayer = new artsPlayer;
|
||||
m_waitTimer = new QTimer(this);
|
||||
connect(m_waitTimer, SIGNAL(timeout()), this, SLOT(waiting()));
|
||||
}
|
||||
|
||||
blinkenGame::~blinkenGame()
|
||||
{
|
||||
delete m_artsPlayer;
|
||||
}
|
||||
|
||||
int blinkenGame::level() const
|
||||
{
|
||||
return m_level;
|
||||
}
|
||||
|
||||
bool blinkenGame::canType() const
|
||||
{
|
||||
return m_phase == typingTheSequence || m_phase == starting;
|
||||
}
|
||||
|
||||
blinkenGame::gamePhase blinkenGame::phase() const
|
||||
{
|
||||
return m_phase;
|
||||
}
|
||||
|
||||
int blinkenGame::score() const
|
||||
{
|
||||
if (m_phase == starting || m_phase == choosingLevel) return 0;
|
||||
return m_sequenceLength - 1;
|
||||
}
|
||||
|
||||
void blinkenGame::clicked(color c)
|
||||
{
|
||||
if (m_phase == starting)
|
||||
{
|
||||
m_artsPlayer -> play(c);
|
||||
return;
|
||||
}
|
||||
if (c == *m_nextColor)
|
||||
{
|
||||
++m_nextColor;
|
||||
m_artsPlayer -> play(c);
|
||||
|
||||
if (m_nextColor == m_sequence.end())
|
||||
{
|
||||
m_sequenceLength++;
|
||||
nextRound();
|
||||
}
|
||||
}
|
||||
else
|
||||
{
|
||||
m_artsPlayer -> play(all, true);
|
||||
emit highlight(all, true);
|
||||
emit gameEnded();
|
||||
setPhase(choosingLevel);
|
||||
}
|
||||
}
|
||||
|
||||
void blinkenGame::setPhase(gamePhase p)
|
||||
{
|
||||
if (p != waiting3 && p != waiting2 && p != waiting1) m_waitTimer -> stop();
|
||||
m_phase = p;
|
||||
emit phaseChanged();
|
||||
}
|
||||
|
||||
void blinkenGame::start(int level)
|
||||
{
|
||||
m_level = level;
|
||||
m_sequenceLength = 1;
|
||||
|
||||
nextRound();
|
||||
|
||||
m_sequence.clear();
|
||||
}
|
||||
|
||||
void blinkenGame::nextSound()
|
||||
{
|
||||
if (m_nextColor != m_sequence.end())
|
||||
{
|
||||
color c;
|
||||
c = *m_nextColor;
|
||||
++m_nextColor;
|
||||
m_artsPlayer -> play(c);
|
||||
emit highlight(c, false);
|
||||
}
|
||||
else
|
||||
{
|
||||
setPhase(typingTheSequence);
|
||||
m_nextColor = m_sequence.begin();
|
||||
emit highlight(none, false);
|
||||
m_artsPlayer->disconnect();
|
||||
}
|
||||
}
|
||||
|
||||
void blinkenGame::soundEnded()
|
||||
{
|
||||
QTimer::singleShot(100, this, SLOT(nextSound()));
|
||||
QTimer::singleShot(50, this, SLOT(unhighlight()));
|
||||
}
|
||||
|
||||
void blinkenGame::unhighlight()
|
||||
{
|
||||
emit highlight(none, false);
|
||||
}
|
||||
|
||||
void blinkenGame::waiting()
|
||||
{
|
||||
if (m_phase == waiting1)
|
||||
{
|
||||
setPhase(blinkenGame::learningTheSequence);
|
||||
if (m_level == 3)
|
||||
{
|
||||
m_sequence.clear();
|
||||
for (int i = 0; i < m_sequenceLength; i++) m_sequence.append(generateColor());
|
||||
}
|
||||
else m_sequence.append(generateColor());
|
||||
|
||||
connect(m_artsPlayer, SIGNAL(ended()), this, SLOT(soundEnded()));
|
||||
m_nextColor = m_sequence.begin();
|
||||
soundEnded();
|
||||
}
|
||||
else if (m_phase == waiting3) setPhase(waiting2);
|
||||
else /* m_phase == waiting2 */ setPhase(waiting1);
|
||||
}
|
||||
|
||||
void blinkenGame::nextRound()
|
||||
{
|
||||
if (m_level == 1) setPhase(waiting3);
|
||||
else setPhase(waiting2);
|
||||
m_waitTimer -> start(1000);
|
||||
}
|
||||
|
||||
blinkenGame::color blinkenGame::generateColor()
|
||||
{
|
||||
int r;
|
||||
// make the compiler happy :-D
|
||||
color c = none;
|
||||
|
||||
r = 1 + (int)(4.0 * kapp -> random() / (RAND_MAX + 1.0));
|
||||
switch(r)
|
||||
{
|
||||
case 1:
|
||||
c = red;
|
||||
break;
|
||||
|
||||
case 2:
|
||||
c = green;
|
||||
break;
|
||||
|
||||
case 3:
|
||||
c = blue;
|
||||
break;
|
||||
|
||||
case 4:
|
||||
c = yellow;
|
||||
break;
|
||||
}
|
||||
return c;
|
||||
}
|
||||
|
||||
#include "blinkengame.moc"
|
||||
@ -0,0 +1,72 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef BLINKENGAME_H
|
||||
#define BLINKENGAME_H
|
||||
|
||||
#include <qobject.h>
|
||||
#include <qvaluelist.h>
|
||||
|
||||
class QTimer;
|
||||
|
||||
class artsPlayer;
|
||||
|
||||
class blinkenGame : public QObject
|
||||
{
|
||||
Q_OBJECT
|
||||
public:
|
||||
blinkenGame();
|
||||
~blinkenGame();
|
||||
|
||||
enum gamePhase { starting, choosingLevel, waiting3, waiting2, waiting1, learningTheSequence, typingTheSequence };
|
||||
enum color
|
||||
{
|
||||
none = 0,
|
||||
red = 1,
|
||||
green = 2,
|
||||
blue = 4,
|
||||
yellow = 8,
|
||||
all = 15};
|
||||
|
||||
int level() const;
|
||||
bool canType() const;
|
||||
gamePhase phase() const;
|
||||
int score() const;
|
||||
|
||||
void clicked(color c);
|
||||
void setPhase(gamePhase p);
|
||||
void start(int level);
|
||||
|
||||
signals:
|
||||
void gameEnded();
|
||||
void phaseChanged();
|
||||
void highlight(blinkenGame::color c, bool unhighlight);
|
||||
|
||||
private slots:
|
||||
void nextSound();
|
||||
void soundEnded();
|
||||
void unhighlight();
|
||||
void waiting();
|
||||
|
||||
private:
|
||||
void nextRound();
|
||||
color generateColor();
|
||||
|
||||
gamePhase m_phase;
|
||||
int m_level;
|
||||
int m_sequenceLength;
|
||||
|
||||
QTimer *m_waitTimer;
|
||||
|
||||
artsPlayer *m_artsPlayer;
|
||||
QValueList<color> m_sequence;
|
||||
QValueList<color>::const_iterator m_nextColor;
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,119 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <kaction.h>
|
||||
#include <kapplication.h>
|
||||
#include <kconfig.h>
|
||||
#include <kstandarddirs.h>
|
||||
#include <kdebug.h>
|
||||
|
||||
#include "button.h"
|
||||
|
||||
button::button(blinkenGame::color c) : m_selected(false), m_color(c)
|
||||
{
|
||||
KConfig *kc = kapp->config();
|
||||
kc->setGroup("General");
|
||||
QString cs = getColorString();
|
||||
QString pixmap = QString("images/%1h.png").arg(cs);
|
||||
|
||||
switch (c)
|
||||
{
|
||||
case blinkenGame::blue:
|
||||
m_key = kc->readNumEntry(cs, Qt::Key_3);
|
||||
break;
|
||||
|
||||
case blinkenGame::yellow:
|
||||
m_key = kc->readNumEntry(cs, Qt::Key_1);
|
||||
break;
|
||||
|
||||
case blinkenGame::red:
|
||||
m_key = kc->readNumEntry(cs, Qt::Key_2);
|
||||
break;
|
||||
|
||||
case blinkenGame::green:
|
||||
m_key = kc->readNumEntry(cs, Qt::Key_4);
|
||||
break;
|
||||
|
||||
default:
|
||||
// never happens
|
||||
break;
|
||||
}
|
||||
|
||||
m_highlighted = new QPixmap(locate("appdata", pixmap));
|
||||
}
|
||||
|
||||
button::~button()
|
||||
{
|
||||
delete m_highlighted;
|
||||
}
|
||||
|
||||
void button::setShortcut(int key)
|
||||
{
|
||||
m_key = key;
|
||||
m_selected = false;
|
||||
|
||||
KConfig *kc = kapp->config();
|
||||
kc->setGroup("General");
|
||||
kc->writeEntry(getColorString(), key);
|
||||
kc->sync();
|
||||
}
|
||||
|
||||
QString button::shortcut() const
|
||||
{
|
||||
return KShortcut(m_key).toString();
|
||||
}
|
||||
|
||||
int button::key() const
|
||||
{
|
||||
return m_key;
|
||||
}
|
||||
|
||||
void button::setSelected(bool b)
|
||||
{
|
||||
m_selected = b;
|
||||
}
|
||||
|
||||
bool button::selected() const
|
||||
{
|
||||
return m_selected;
|
||||
}
|
||||
|
||||
QPixmap *button::pixmap() const
|
||||
{
|
||||
return m_highlighted;
|
||||
}
|
||||
|
||||
QString button::getColorString() const
|
||||
{
|
||||
switch (m_color)
|
||||
{
|
||||
case blinkenGame::blue:
|
||||
return "blue";
|
||||
break;
|
||||
|
||||
case blinkenGame::yellow:
|
||||
return "yellow";
|
||||
break;
|
||||
|
||||
case blinkenGame::red:
|
||||
return "red";
|
||||
break;
|
||||
|
||||
case blinkenGame::green:
|
||||
return "green";
|
||||
break;
|
||||
|
||||
default:
|
||||
// never happens
|
||||
break;
|
||||
}
|
||||
|
||||
// never happens
|
||||
return QString::null;
|
||||
}
|
||||
@ -0,0 +1,43 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef BUTTON_H
|
||||
#define BUTTON_H
|
||||
|
||||
#include <qobject.h>
|
||||
|
||||
#include "blinkengame.h"
|
||||
|
||||
class KAction;
|
||||
class KActionCollection;
|
||||
class KShortcut;
|
||||
|
||||
class button
|
||||
{
|
||||
public:
|
||||
button(blinkenGame::color c);
|
||||
~button();
|
||||
|
||||
void setShortcut(int key);
|
||||
QString shortcut() const;
|
||||
int key() const;
|
||||
void setSelected(bool b);
|
||||
bool selected() const;
|
||||
QPixmap *pixmap() const;
|
||||
|
||||
private:
|
||||
QString getColorString() const;
|
||||
|
||||
QPixmap *m_highlighted;
|
||||
bool m_selected;
|
||||
int m_key;
|
||||
blinkenGame::color m_color;
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,57 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qcolor.h>
|
||||
#include <qpainter.h>
|
||||
|
||||
#include "counter.h"
|
||||
#include "number.h"
|
||||
|
||||
void counter::paint(QPainter &p, bool drawScore, int score, bool drawTimer, const QColor &c1, const QColor &c2, const QColor &c3)
|
||||
{
|
||||
p.save();
|
||||
p.translate(45, 15);
|
||||
p.setPen(QPen(Qt::black, 3));
|
||||
p.setBrush(QColor(40, 40, 40));
|
||||
if (drawTimer)
|
||||
{
|
||||
p.fillRect(-44, -13, 98, 48, p.brush());
|
||||
p.drawRoundRect(-45, -15, 100, 50, 15, 15);
|
||||
}
|
||||
else
|
||||
{
|
||||
p.fillRect(-44, -13, 70, 48, p.brush());
|
||||
p.drawRoundRect(-45, -15, 73, 50, 15, 15);
|
||||
}
|
||||
|
||||
if (drawScore)
|
||||
{
|
||||
number n(score);
|
||||
n.paint(p, 2);
|
||||
}
|
||||
|
||||
if (drawTimer)
|
||||
{
|
||||
p.fillRect(35, -6, 11, 9, c1);
|
||||
p.fillRect(35, 6, 11, 9, c2);
|
||||
p.fillRect(35, 18, 11, 9, c3);
|
||||
}
|
||||
p.restore();
|
||||
}
|
||||
|
||||
int counter::width(bool drawTimer)
|
||||
{
|
||||
if (drawTimer) return 100;
|
||||
else return 73;
|
||||
}
|
||||
|
||||
int counter::height()
|
||||
{
|
||||
return 50;
|
||||
}
|
||||
@ -0,0 +1,23 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef COUNTER_H
|
||||
#define COUNTER_H
|
||||
|
||||
class QPainter;
|
||||
|
||||
class counter
|
||||
{
|
||||
public:
|
||||
static void paint(QPainter &p, bool drawScore, int score, bool drawTimer, const QColor &c1, const QColor &c2, const QColor &c3);
|
||||
static int width(bool drawTimer);
|
||||
static int height();
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,27 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qfont.h>
|
||||
#include <qfontinfo.h>
|
||||
|
||||
#include <kio/netaccess.h>
|
||||
|
||||
#include "fontchecker.h"
|
||||
|
||||
bool fontChecker::checkInstalled(const QFont &font, const QString &fontPath)
|
||||
{
|
||||
QFontInfo fi(font);
|
||||
// Works with Steve may need some tweaking to work with other fonts
|
||||
if (!fi.exactMatch())
|
||||
{
|
||||
bool success = KIO::NetAccess::copy(fontPath, "fonts:/Personal/", 0);
|
||||
return !success;
|
||||
}
|
||||
return true;
|
||||
}
|
||||
@ -0,0 +1,21 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef FONTCHECKER_H
|
||||
#define FONTCHECKER_H
|
||||
|
||||
class QFont;
|
||||
|
||||
class fontChecker
|
||||
{
|
||||
public:
|
||||
static bool checkInstalled(const QFont &font, const QString &fontPath);
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,33 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qpainter.h>
|
||||
|
||||
#include "fontutils.h"
|
||||
|
||||
int fontUtils::fontSize(QPainter &p, const QString &s1, int w, int h)
|
||||
{
|
||||
int size;
|
||||
QRect aux1;
|
||||
bool done = false;
|
||||
|
||||
size = 28;
|
||||
|
||||
while (!done)
|
||||
{
|
||||
QFont f = p.font();
|
||||
f.setPointSize(size);
|
||||
p.setFont(f);
|
||||
aux1 = p.boundingRect(QRect(), Qt::AlignAuto, s1);
|
||||
if (aux1.width() > w || aux1.height() > h) size = QMIN(w * size / aux1.width(), h * size / aux1.height());
|
||||
else done = true;
|
||||
}
|
||||
|
||||
return size;
|
||||
}
|
||||
@ -0,0 +1,18 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef FONTUTILS_H
|
||||
#define FONTUTILS_H
|
||||
|
||||
namespace fontUtils
|
||||
{
|
||||
int fontSize(QPainter &p, const QString &s1, int w, int h);
|
||||
}
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,198 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qpainter.h>
|
||||
#include <qpixmap.h>
|
||||
#include <qtabbar.h>
|
||||
#include <qtabwidget.h>
|
||||
|
||||
#include <kapplication.h>
|
||||
#include <kconfig.h>
|
||||
#include <klocale.h>
|
||||
|
||||
#include "highscoredialog.h"
|
||||
#include "counter.h"
|
||||
#include "fontutils.h"
|
||||
#include "settings.h"
|
||||
|
||||
static const int margin = 15;
|
||||
static const int smallMargin = 5;
|
||||
static const int namesFontSize = 25;
|
||||
|
||||
/* scoresWidget */
|
||||
|
||||
class scoresWidget : public QWidget
|
||||
{
|
||||
public:
|
||||
scoresWidget(QWidget *parent, const QValueList< QPair<int, QString> > &scores);
|
||||
QSize calcSize();
|
||||
|
||||
protected:
|
||||
void paintEvent(QPaintEvent *);
|
||||
|
||||
private:
|
||||
const QValueList< QPair<int, QString> > &m_scores;
|
||||
};
|
||||
|
||||
scoresWidget::scoresWidget(QWidget *parent, const QValueList< QPair<int, QString> > &scores) : QWidget(parent, 0, WStaticContents | WNoAutoErase), m_scores(scores)
|
||||
{
|
||||
}
|
||||
|
||||
void scoresWidget::paintEvent(QPaintEvent *)
|
||||
{
|
||||
int w = width();
|
||||
int h = height();
|
||||
QFont f;
|
||||
QPixmap buf(w, h);
|
||||
QPainter p(&buf);
|
||||
QRect r;
|
||||
QColor bg = paletteBackgroundColor();
|
||||
|
||||
// bg color
|
||||
p.fillRect(0, 0, w, h, bg);
|
||||
|
||||
p.setPen(black);
|
||||
|
||||
if (blinkenSettings::customFont()) f = QFont("Steve");
|
||||
p.setFont(f);
|
||||
f.setPointSize(fontUtils::fontSize(p, "A", 1000, namesFontSize));
|
||||
p.setFont(f);
|
||||
|
||||
p.translate(margin, margin);
|
||||
|
||||
QValueList< QPair<int, QString> >::const_iterator it;
|
||||
for (it = m_scores.begin(); it != m_scores.end(); ++it)
|
||||
{
|
||||
counter::paint(p, !(*it).second.isEmpty(), (*it).first, false, QColor(), QColor(), QColor());
|
||||
p.setPen(black);
|
||||
p.drawText(counter::width(false) + 2 * smallMargin, 30, (*it).second);
|
||||
p.translate(0, counter::height() + smallMargin);
|
||||
}
|
||||
|
||||
bitBlt(this, 0, 0, &buf);
|
||||
}
|
||||
|
||||
QSize scoresWidget::calcSize()
|
||||
{
|
||||
int mw, mh, lt;
|
||||
QRect r;
|
||||
QPainter p(this);
|
||||
QFont f;
|
||||
|
||||
if (blinkenSettings::customFont()) f = QFont("Steve");
|
||||
p.setFont(f);
|
||||
f.setPointSize(fontUtils::fontSize(p, "A", 1000, namesFontSize));
|
||||
p.setFont(f);
|
||||
for (int i = 0; i < 3; i++)
|
||||
{
|
||||
lt = 0;
|
||||
QValueList< QPair<int, QString> >::const_iterator it;
|
||||
for (it = m_scores.begin(); it != m_scores.end(); ++it)
|
||||
{
|
||||
r = p.boundingRect(QRect(), Qt::AlignAuto, (*it).second);
|
||||
lt = QMAX(lt, r.width());
|
||||
}
|
||||
}
|
||||
|
||||
mw = margin + counter::width(false) + 2 * smallMargin + lt + margin;
|
||||
mh = margin * 2 + counter::height() * 5 + smallMargin * 4;
|
||||
|
||||
QSize size(mw, mh);
|
||||
setMinimumSize(size);
|
||||
resize(size);
|
||||
|
||||
return size;
|
||||
}
|
||||
|
||||
/* myTabWidget */
|
||||
|
||||
class myTabWidget : public QTabWidget
|
||||
{
|
||||
public:
|
||||
myTabWidget(QWidget *parent) : QTabWidget(parent) {}
|
||||
|
||||
QSize tabBarSizeHint() const
|
||||
{
|
||||
return tabBar() -> sizeHint();
|
||||
}
|
||||
};
|
||||
|
||||
/* highScoreDialog */
|
||||
|
||||
highScoreDialog::highScoreDialog(QWidget *parent) : KDialogBase(parent, 0, true, i18n("Highscores"), KDialogBase::Close)
|
||||
{
|
||||
m_tw = new myTabWidget(this);
|
||||
setMainWidget(m_tw);
|
||||
|
||||
KConfig *cfg = kapp -> config();
|
||||
for (int i = 1; i <= 3; i++)
|
||||
{
|
||||
cfg -> setGroup(QString("Level%1").arg(i));
|
||||
for (int j = 1; j <= 5; j++)
|
||||
{
|
||||
m_scores[i-1].append(qMakePair(cfg->readNumEntry(QString("Score%1").arg(j)), cfg->readEntry(QString("Name%1").arg(j))));
|
||||
}
|
||||
}
|
||||
|
||||
m_tw -> addTab(new scoresWidget(m_tw, m_scores[0]), i18n("Level 1"));
|
||||
m_tw -> addTab(new scoresWidget(m_tw, m_scores[1]), i18n("Level 2"));
|
||||
m_tw -> addTab(new scoresWidget(m_tw, m_scores[2]), i18n("Level ?"));
|
||||
}
|
||||
|
||||
bool highScoreDialog::scoreGoodEnough(int level, int score)
|
||||
{
|
||||
level--;
|
||||
QValueList< QPair<int, QString> >::iterator it, itEnd;
|
||||
it = m_scores[level].begin();
|
||||
itEnd = m_scores[level].end();
|
||||
while (it != itEnd && (*it).first >= score) it++;
|
||||
|
||||
return (it != itEnd);
|
||||
}
|
||||
|
||||
void highScoreDialog::addScore(int level, int score, const QString &name)
|
||||
{
|
||||
level--;
|
||||
QValueList< QPair<int, QString> >::iterator it, itEnd;
|
||||
it = m_scores[level].begin();
|
||||
itEnd = m_scores[level].end();
|
||||
while (it != itEnd && (*it).first >= score) it++;
|
||||
|
||||
if (it != itEnd)
|
||||
{
|
||||
m_scores[level].insert(it, qMakePair(score, name));
|
||||
m_scores[level].remove(--m_scores[level].end());
|
||||
|
||||
KConfig *cfg = kapp -> config();
|
||||
cfg -> setGroup(QString("Level%1").arg(level + 1));
|
||||
int j;
|
||||
for (it = m_scores[level].begin(), j = 1; it != m_scores[level].end(); ++it, j++)
|
||||
{
|
||||
cfg->writeEntry(QString("Score%1").arg(j), (*it).first);
|
||||
cfg->writeEntry(QString("Name%1").arg(j), (*it).second);
|
||||
}
|
||||
cfg -> sync();
|
||||
}
|
||||
}
|
||||
|
||||
void highScoreDialog::showLevel(int level)
|
||||
{
|
||||
QSize max, aux;
|
||||
m_tw -> setCurrentPage(level -1);
|
||||
|
||||
for (int i = 0; i < 3; i++)
|
||||
{
|
||||
aux = static_cast<scoresWidget*>(m_tw -> page(i)) -> calcSize();
|
||||
max = max.expandedTo(aux);
|
||||
}
|
||||
if (max.width() < m_tw -> tabBarSizeHint().width() + 5) m_tw -> setMinimumSize(m_tw -> tabBarSizeHint().width() + 5, max.height() + m_tw -> tabBarSizeHint().height() + 5);
|
||||
|
||||
exec();
|
||||
delete this;
|
||||
}
|
||||
@ -0,0 +1,33 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef HIGHSCOREDIALOG_H
|
||||
#define HIGHSCOREDIALOG_H
|
||||
|
||||
#include <qpair.h>
|
||||
#include <qvaluelist.h>
|
||||
|
||||
#include <kdialogbase.h>
|
||||
|
||||
class myTabWidget;
|
||||
|
||||
class highScoreDialog : private KDialogBase
|
||||
{
|
||||
public:
|
||||
highScoreDialog(QWidget *parent);
|
||||
|
||||
bool scoreGoodEnough(int level, int score);
|
||||
void addScore(int level, int score, const QString &name);
|
||||
void showLevel(int level);
|
||||
|
||||
QValueList< QPair<int, QString> > m_scores[3];
|
||||
myTabWidget *m_tw;
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,41 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <kaboutdata.h>
|
||||
#include <kapplication.h>
|
||||
#include <kcmdlineargs.h>
|
||||
#include <kprocess.h>
|
||||
#include <kstandarddirs.h>
|
||||
|
||||
#include "fontchecker.h"
|
||||
#include "blinken.h"
|
||||
|
||||
int main(int argc, char *argv[])
|
||||
{
|
||||
KAboutData about("blinken", I18N_NOOP("blinKen"), "0.1.1", I18N_NOOP("A memory enhancement game"), KAboutData::License_GPL, "© 2005 Albert Astals Cid\n© 2005 Danny Allen");
|
||||
about.addAuthor("Albert Astals Cid", I18N_NOOP("Coding"), "tsdgeos@terra.es");
|
||||
about.addAuthor("Danny Allen", I18N_NOOP("Design, Graphics and Sounds"), "danny@dannyallen.co.uk");
|
||||
about.addCredit("Steve Jordi", I18N_NOOP("GPL'ed his 'Steve' font so that we could use it"), "steve@sjordi.com");
|
||||
KCmdLineArgs::init(argc, argv, &about);
|
||||
KApplication app;
|
||||
app.connect(&app, SIGNAL(lastWindowClosed()), &app, SLOT(quit()));
|
||||
|
||||
QFont f("Steve", 12, QFont::Normal, true);
|
||||
if (!fontChecker::checkInstalled(f, locate("appdata", "fonts/steve.ttf")))
|
||||
{
|
||||
KProcess *proc = new KProcess;
|
||||
for (int i = 0; i < argc; i++) *proc << argv[i];
|
||||
proc->start();
|
||||
}
|
||||
else
|
||||
{
|
||||
app.setTopWidget(new blinken());
|
||||
return app.exec();
|
||||
}
|
||||
}
|
||||
@ -0,0 +1,196 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#include <qbrush.h>
|
||||
#include <qcolor.h>
|
||||
#include <qpainter.h>
|
||||
|
||||
#include "number.h"
|
||||
|
||||
const int number::m_number0[20] = {1, 0, 0, 2,
|
||||
0, 5, 5, 0,
|
||||
0, 5, 5, 0,
|
||||
0, 5, 5, 0,
|
||||
4, 0, 0, 3};
|
||||
|
||||
const int number::m_number1[20] = {5, 1, 0, 5,
|
||||
5, 5, 0, 5,
|
||||
5, 5, 0, 5,
|
||||
5, 5, 0, 5,
|
||||
5, 5, 0, 5};
|
||||
|
||||
const int number::m_number2[20] = {0, 0, 0, 2,
|
||||
5, 5, 5, 0,
|
||||
1, 0, 0, 3,
|
||||
0, 5, 5, 5,
|
||||
0, 0, 0, 0};
|
||||
|
||||
const int number::m_number3[20] = {0, 0, 0, 2,
|
||||
5, 5, 5, 0,
|
||||
5, 0, 0, 3,
|
||||
5, 5, 5, 2,
|
||||
0, 0, 0, 3};
|
||||
|
||||
|
||||
const int number::m_number4[20] = {0, 5, 5, 0,
|
||||
0, 5, 5, 0,
|
||||
0, 5, 5, 0,
|
||||
4, 0, 0, 0,
|
||||
5, 5, 5, 0};
|
||||
|
||||
const int number::m_number5[20] = {0, 0, 0, 0,
|
||||
0, 5, 5, 5,
|
||||
4, 0, 0, 2,
|
||||
5, 5, 5, 0,
|
||||
0, 0, 0, 3};
|
||||
|
||||
const int number::m_number6[20] = {1, 0, 0, 0,
|
||||
0, 5, 5, 5,
|
||||
0, 0, 0, 2,
|
||||
0, 5, 5, 0,
|
||||
4, 0, 0, 3};
|
||||
|
||||
const int number::m_number7[20] = {0, 0, 0, 2,
|
||||
5, 5, 5, 0,
|
||||
5, 5, 5, 0,
|
||||
5, 5, 5, 0,
|
||||
5, 5, 5, 0};
|
||||
|
||||
const int number::m_number8[20] = {1, 0, 0, 2,
|
||||
0, 5, 5, 0,
|
||||
4, 0, 0, 3,
|
||||
1, 5, 5, 2,
|
||||
4, 0, 0, 3};
|
||||
|
||||
const int number::m_number9[20] = {1, 0, 0, 2,
|
||||
0, 5, 5, 0,
|
||||
4, 0, 0, 3,
|
||||
5, 5, 5, 0,
|
||||
0, 0, 0, 3};
|
||||
|
||||
number::number(int n)
|
||||
{
|
||||
m_number = n;
|
||||
}
|
||||
|
||||
void number::paint(QPainter &p, int digits) const
|
||||
{
|
||||
int nDigits, digit, number;
|
||||
nDigits = 0;
|
||||
number = m_number;
|
||||
|
||||
while(nDigits < digits || number != 0)
|
||||
{
|
||||
digit = number % 10;
|
||||
number /= 10;
|
||||
paintDigit(p, digit);
|
||||
nDigits++;
|
||||
p.translate(-30, 0);
|
||||
}
|
||||
p.translate(30 * nDigits, 0);
|
||||
}
|
||||
|
||||
void number::paintDigit(QPainter &p, int number) const
|
||||
{
|
||||
// make gcc happy
|
||||
const int *n = m_number0;
|
||||
int shape;
|
||||
|
||||
switch (number)
|
||||
{
|
||||
case 1:
|
||||
n = m_number1;
|
||||
break;
|
||||
|
||||
case 2:
|
||||
n = m_number2;
|
||||
break;
|
||||
|
||||
case 3:
|
||||
n = m_number3;
|
||||
break;
|
||||
|
||||
case 4:
|
||||
n = m_number4;
|
||||
break;
|
||||
|
||||
case 5:
|
||||
n = m_number5;
|
||||
break;
|
||||
|
||||
case 6:
|
||||
n = m_number6;
|
||||
break;
|
||||
|
||||
case 7:
|
||||
n = m_number7;
|
||||
break;
|
||||
|
||||
case 8:
|
||||
n = m_number8;
|
||||
break;
|
||||
|
||||
case 9:
|
||||
n = m_number9;
|
||||
break;
|
||||
}
|
||||
|
||||
p.setBrush(Qt::red);
|
||||
p.setPen(Qt::red);
|
||||
for (int i = 0; i < 5; i++)
|
||||
{
|
||||
for (int j = 0; j < 4; j++)
|
||||
{
|
||||
shape = n[j + i * 4];
|
||||
if (shape == 0)
|
||||
{
|
||||
p.fillRect(7 * (j-1), 7 * (i-1), 6, 6, Qt::red);
|
||||
}
|
||||
else if (shape != 5)
|
||||
{
|
||||
if (shape == 1) p.translate(7 * (j-1), 7 * (i-1));
|
||||
else if (shape == 2)
|
||||
{
|
||||
p.translate(7 * j - 2, 7 * (i-1));
|
||||
p.rotate(90);
|
||||
}
|
||||
else if (shape == 3)
|
||||
{
|
||||
p.translate(7 * j - 2, 7 * i - 2);
|
||||
p.rotate(180);
|
||||
}
|
||||
else if (shape == 4)
|
||||
{
|
||||
p.translate(7 * (j-1), 7 * i - 2);
|
||||
p.rotate(270);
|
||||
}
|
||||
|
||||
p.drawPie(0, 0, 11, 11, 90 * 16, 16 * 90);
|
||||
|
||||
if (shape == 1) p.translate(-7 * (j-1), -7 * (i-1));
|
||||
else if (shape == 2)
|
||||
{
|
||||
p.rotate(-90);
|
||||
p.translate(-(7 * j - 2), -7 * (i-1));
|
||||
|
||||
}
|
||||
else if (shape == 3)
|
||||
{
|
||||
p.rotate(-180);
|
||||
p.translate(-(7 * j - 2), -(7 * i - 2));
|
||||
}
|
||||
else if (shape == 4)
|
||||
{
|
||||
p.rotate(-270);
|
||||
p.translate(- (7 * (j-1)), -(7 * i - 2));
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -0,0 +1,39 @@
|
||||
/***************************************************************************
|
||||
* Copyright (C) 2005 by Albert Astals Cid <tsdgeos@terra.es> *
|
||||
* *
|
||||
* 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. *
|
||||
***************************************************************************/
|
||||
|
||||
#ifndef NUMBER_H
|
||||
#define NUMBER_H
|
||||
|
||||
class QPainter;
|
||||
|
||||
class number
|
||||
{
|
||||
public:
|
||||
number(int n);
|
||||
|
||||
void paint(QPainter &p, int digits) const;
|
||||
|
||||
private:
|
||||
void paintDigit(QPainter &p, int n) const;
|
||||
|
||||
int m_number;
|
||||
|
||||
static const int m_number0[20];
|
||||
static const int m_number1[20];
|
||||
static const int m_number2[20];
|
||||
static const int m_number3[20];
|
||||
static const int m_number4[20];
|
||||
static const int m_number5[20];
|
||||
static const int m_number6[20];
|
||||
static const int m_number7[20];
|
||||
static const int m_number8[20];
|
||||
static const int m_number9[20];
|
||||
};
|
||||
|
||||
#endif
|
||||
@ -0,0 +1,4 @@
|
||||
File=blinken.kcfg
|
||||
ClassName=blinkenSettings
|
||||
Singleton=true
|
||||
Mutators=true
|
||||
@ -0,0 +1,6 @@
|
||||
#MIN_CONFIG
|
||||
CXXFLAGS="$CXXFLAGS $KDE_DEFAULT_CXXFLAGS"
|
||||
AC_CHECK_SETENV
|
||||
AC_CHECK_UNSETENV
|
||||
|
||||
KDE_INIT_DOXYGEN([KDE Education API Reference], [Version $VERSION])
|
||||
@ -0,0 +1,3 @@
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
SUBDIRS = $(AUTODIRS)
|
||||
|
After Width: | Height: | Size: 1.1 KiB |
|
After Width: | Height: | Size: 3.4 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 73 KiB |
|
After Width: | Height: | Size: 74 KiB |
|
After Width: | Height: | Size: 72 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 885 B |
|
After Width: | Height: | Size: 9.5 KiB |
|
After Width: | Height: | Size: 1.8 KiB |
@ -0,0 +1,361 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY blinken "<application>blinKen</application>">
|
||||
<!ENTITY kappname "&blinken;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &blinken; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Danny</firstname>
|
||||
<surname>Allen</surname>
|
||||
<affiliation>
|
||||
<address>&Danny.Allen.mail;</address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2005</year>
|
||||
<holder>&Danny.Allen;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-08-20</date>
|
||||
<releaseinfo>1.0</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&blinken; brings a retro electronic memory game from the 1970's to &kde;.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>blinKen</keyword>
|
||||
<keyword>game</keyword>
|
||||
<keyword>child</keyword>
|
||||
<keyword>electronic</keyword>
|
||||
<keyword>retro</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&blinken; is based on an electronic game released in 1978, which challenges players to remember sequences of increasing length. On the face of the device, there are 4 different color buttons, each one with their own distinctive sound. These buttons light up randomly, creating the sequence that the player must then recall. If the player is successful in remembering the sequence of lights in the correct order, they advance to the next stage, where an identical sequence with one extra step is presented. If they are incorrect, the game is lost, and the player must start again from the beginning.
|
||||
|
||||
The goal is to get a high score - each step in the sequence is worth one point, so correct entry of a sequence of 8 lights is worth 8 points on the high score table.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="using-blinken">
|
||||
<title>Using &blinken;</title>
|
||||
|
||||
<para>
|
||||
Here is the screen that is presented on startup of &blinken;, showing the general interface to the application. Most of the screen is taken up by the <interface>device</interface>, with the <interface>4 colored buttons</interface>, with the device controls (<interface>score counter</interface>, <guibutton>Start</guibutton> button, &etc;) in the center of the screen. The current status of the application is displayed on the <interface>piece of paper</interface> under the device. In the corners of the application, there are 3 buttons:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here is the screen that is presented on startup of &blinken;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here is the screen that is presented on startup of &blinken;</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The <guiicon>Highscores</guiicon> button <action>opens a dialog that displays the <guilabel>Highscores table</guilabel></action> for each of the 3 difficulty levels (the <guilabel>Highscores</guilabel> table can also be accessed by <action>clicking on the <interface>score counter</interface>)</action>:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo><guiicon>Highscores</guiicon> button</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken_highscoresbutton.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase><guiicon>Highscores</guiicon> button</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The <guiicon>Quit</guiicon> button <action>closes the application</action>:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo><guiicon>Quit</guiicon> button</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken_quitbutton.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase><guiicon>Quit</guiicon> button</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The <guiicon>Help</guiicon> button is special, in that it <action>reveals 3 sub-buttons</action>. These buttons are shown when the <guiicon>Help</guiicon> button is <action>hovered over</action>, and provide access to the <guilabel>&blinken; handbook</guilabel> (this document), and the <guilabel>About &blinken;</guilabel> and <guilabel>About &kde;</guilabel> dialogs:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo><guiicon>Help</guiicon> button</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken_helpbutton.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase><guiicon>Help</guiicon> button</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
To become familiar with the workings of the game, you can interact with the <interface>colored buttons</interface> whilst on the main screen. The buttons will illuminate and produce a tone upon being pressed.
|
||||
</para>
|
||||
|
||||
<note><para>You need to have &arts; support in kdelibs to hear the sounds.</para></note>
|
||||
<sect1 id="starting-game">
|
||||
<title>Starting a Game</title>
|
||||
|
||||
<para>
|
||||
Once you are familiar with the workings of the application, a game can be started by pressing the <guibutton>Start</guibutton> button in the center of the screen. This <quote>powers on</quote> the device, as shown by the illuminated <interface>score counter</interface>. You can then <action>choose the difficulty level</action> that you want to attempt:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Select difficulty level</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Select difficulty level</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
There are 3 levels in &blinken;:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Level 1 is the easiest level, as it provides the longest time break between each sequence playback.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Level 2 is the intermediate level. It is identical to the previous level, but has a smaller time break between each sequence playback.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Level ? is the most difficult level of &blinken;. It takes the timings from Level 2, but each sequence is totally random, rather than following on from the previous sequence, as in the standard game type.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="enter-highscore">
|
||||
<title>Entering a New Highscore</title>
|
||||
|
||||
<para>
|
||||
If you are lucky enough to get a highscore, it will be entered into the <guilabel>Highscores</guilabel> table. A dialog will ask for a name to associate with your score in the table:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Highscore nickname prompt dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken_nickprompt.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Highscore nickname prompt dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Only 5 scores are kept for each level, so try not to be disappointed if you don't make it!
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="playing-tips">
|
||||
<title>Playing Tips</title>
|
||||
<para>
|
||||
&blinken; is the ultimate memory game, though you need not possess the ultimate memory to be successful. These tips will help you in your pursuit of the best score:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
If you have PC speakers, turn them on with the sound at a good level so that you can hear the tones alongside seeing the flashing lights.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Experiment with both the mouse and <link
|
||||
linkend="accessibility">keyboard</link> interaction methods, to see which one suites your memory best.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Try remembering the sequence as a list of colors.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Try remembering the sequence as positions on the screen.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="accessibility">
|
||||
<title>Accessibility Options</title>
|
||||
|
||||
<para>
|
||||
To allow &blinken; to be more easily enjoyed by certain users, there are several accessibility options built into &blinken;.
|
||||
</para>
|
||||
<para>
|
||||
To view and modify the accessibility options of &blinken;, press the <keycap>&Ctrl;</keycap> key (whilst a game is not in progress):
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&blinken; access keys</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blinken_accesskeys.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&blinken; access keys</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
To return to the game screen, press the <keycap>&Ctrl;</keycap> key again.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Alongside use of the mouse, &blinken; also allows the user to operate the game using the keyboard.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The keys are <keycap>1</keycap>, <keycap>2</keycap>, <keycap>3</keycap>, <keycap>4</keycap> by default.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To change the mapping of any button, click it using the mouse. It will then be highlighted, waiting for input. Press the desired key on the keyboard to change the currently assigned key.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There are other options available in the middle of the window: <interface>sounds</interface> and <interface>font</interface>.
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
By unchecking the <interface>sounds</interface> checkbox, the &blinken; sound effects will be suppressed.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
By unchecking the <interface>font</interface> checkbox, a standard font will be used for status text instead of the default handwriting font.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&blinken;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2005 Albert Astals Cid <email>tsdgeos@terra.es</email> and &Danny.Allen; &Danny.Allen.mail;
|
||||
</para>
|
||||
<para>
|
||||
Contributors:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>"Steve" font: Steve Jordi
|
||||
<email>steve@sjordi.com</email>
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2005 &Danny.Allen; &Danny.Allen.mail;
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-blinken">
|
||||
<title>How to obtain &blinken;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
|
||||
// vim:ts=2:sw=2:tw=78:noet:noai
|
||||
-->
|
||||
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 33 KiB |
File diff suppressed because it is too large
Load Diff
|
After Width: | Height: | Size: 26 KiB |
|
After Width: | Height: | Size: 85 KiB |
|
After Width: | Height: | Size: 48 KiB |
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 159 KiB |
|
After Width: | Height: | Size: 34 KiB |
@ -0,0 +1,71 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<author><personname><firstname>Ben</firstname><surname>Burton</surname></personname></author>
|
||||
<date>April 8, 2003</date>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>kalzium</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>kalzium</command></refname>
|
||||
<refpurpose>A &kde; based chemistry teaching tool</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>kalzium</command>
|
||||
|
||||
<group><option>KDE Generic Options</option></group>
|
||||
<group><option>Qt Generic Options</option></group>
|
||||
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
|
||||
<para>&kalzium; is a program which shows you the Periodic System of
|
||||
the Elements (PSE). You can use &kalzium; to search for information
|
||||
about the elements or to learn facts about the PSE.</para>
|
||||
|
||||
<para>&kalzium; provides you with all kinds of information about the
|
||||
PSE. You can look up lots of information about the elements and also
|
||||
use visualisations to show them.</para>
|
||||
|
||||
<para>This package is part of the official KDE edutainment module. </para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kalzium">help:/kalzium</ulink> (either enter this
|
||||
<acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kalzium</parameter></userinput>).</para>
|
||||
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
|
||||
<para>&kalzium; was written by &Carsten.Niehaus;
|
||||
&Carsten.Niehaus.mail; and
|
||||
<personname><firstname>Tomisalve</firstname><surname>Gountchev</surname></personname>
|
||||
<email>tomi@idiom.com</email>.</para>
|
||||
|
||||
<para>This manual page was prepared by <personname><firstname>Ben</firstname><surname>Burton</surname></personname></para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 36 KiB |
|
After Width: | Height: | Size: 61 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 290 KiB |
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 5.3 KiB |
|
After Width: | Height: | Size: 9.8 KiB |
|
After Width: | Height: | Size: 14 KiB |
|
After Width: | Height: | Size: 76 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 4.1 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 20 KiB |
@ -0,0 +1,497 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kanagram "<application>Kanagram</application>">
|
||||
<!ENTITY kappname "&kanagram;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kanagram; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Danny</firstname>
|
||||
<surname>Allen</surname>
|
||||
<affiliation>
|
||||
<address>&Danny.Allen.mail;</address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2005</year>
|
||||
<holder>&Danny.Allen;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-09-04</date>
|
||||
<releaseinfo>1.0</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kanagram; brings fun anagram puzzles to &kde;.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>Kanagram</keyword>
|
||||
<keyword>game</keyword>
|
||||
<keyword>child</keyword>
|
||||
<keyword>anagram</keyword>
|
||||
<keyword>words</keyword>
|
||||
<keyword>jumble</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&kanagram; is a game based on anagrams of words: the puzzle is solved when the letters of the scrambled word are put back in the correct order. There is no limit on either time taken, or the amount of attempts to solve the word. Included with &kanagram; are several vocabularies ready to play, with many more available from the Internet.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="using-kanagram">
|
||||
<title>Using &kanagram;</title>
|
||||
|
||||
<para>
|
||||
Here is the screen that is presented on startup of &kanagram;, showing the main interface to the application. Much of the window is taken up by the <interface>blackboard</interface>, where the puzzles are written onto, with the <interface>filing cabinet</interface> on the right containing application controls:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here is the screen that is presented on startup of &kanagram;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="kanagram.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
The <interface>Vocabulary Switcher</interface> allows the user to quickly <action>change the active vocabulary</action> by clicking on it: the &LMB; <action>advances to the next vocabulary</action>, with the &RMB; allowing you to <action>return to the previously-played vocabulary</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
In the center of the <interface>blackboard</interface> is the anagram puzzle to be solved.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
When the <quote><guibutton>Hint</guibutton></quote> button is clicked, a short sentence will appear, <action>describing the current word puzzle</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Reveal Word</guibutton></quote> button <action>solves the current word puzzle</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <interface>Entry Box</interface> allows you to <action>input your attempts</action> to solve the current word puzzle.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <interface>Enter</interface> button lets you <action>check if your answer is correct</action>. This function is also provided by the <keycap>Enter</keycap> key.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
This is the <guiicon>Next Word</guiicon> button, and allows you to <action>advance to the next anagram puzzle</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
This is the <guiicon>Configure</guiicon> button, which <action>opens the <guilabel>Configure</guilabel> &kanagram; dialog</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guiicon>Help</guiicon> button is special, in that it <action>reveals 3 sub-buttons</action>. These buttons are shown when the <guiicon>Help</guiicon> button is hovered over, and provide access to the <guilabel>&kanagram; handbook</guilabel> (this document), the <guilabel>About &kanagram;</guilabel> and the <guilabel>About &kde;</guilabel> dialogs:
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The 3 different states of the <guiicon>Help</guiicon> button</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="helpstates.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guiicon>Quit</guiicon> button <action>closes the application</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<sect1 id="playing-game">
|
||||
<title>Playing a game</title>
|
||||
|
||||
<para>
|
||||
Now that you are familiar with the interface of &kanagram;, lets play a game!
|
||||
</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>
|
||||
Using the <interface>Vocabulary Switcher</interface>, <action>select the vocabulary theme</action> that you would like to attempt. A word from this vocabulary will then be presented in the middle of the <interface>blackboard</interface>. Now, try and guess what word the jumble of letters represents.
|
||||
<tip>
|
||||
<para>
|
||||
If you cannot guess what the word is, press the <quote><guibutton>Hint</guibutton></quote> button to get some friendly advice from your friend in the <interface>filing cabinet</interface>:
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; hint</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="kanagram-hint.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; hint</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</tip>
|
||||
</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>
|
||||
Once you think you know the correct answer, type it into the <interface>Entry Box</interface> below the <interface>blackboard</interface>. Either press the <keycap>Enter</keycap> key, or click on the <interface>Enter</interface> button to the right of the <interface>Entry Box</interface> to check your answer: it will <action>change green on a correct answer</action>, and <action>red on an incorrect attempt</action>:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>answer highlighted</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="answer-highlight.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>answer highlighted</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>
|
||||
If you were correct, try and guess the next word! Alternatively, you can attempt one of the many other vocabularies bundled with &kanagram;.
|
||||
</para>
|
||||
</step>
|
||||
</procedure>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="configuring">
|
||||
<title>Configuring &kanagram;</title>
|
||||
|
||||
<para>
|
||||
The <guilabel>Configure</guilabel> dialog is opened by clicking on the <guiicon>Configure</guiicon> button:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; general settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="general-settings.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; general settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<itemizedlist>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guilabel>Auto-hide hints after:</guilabel></quote> <interface>drop-down box</interface> allows you to specify how hints are presented to you. Here, you can set the hint box to disappear after a certain amount of seconds (⪚ 5 seconds), or you can leave it as default (<quote>Do not auto-hide hints</quote>).
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guilabel>Play Using:</guilabel></quote> <interface>drop-down box</interface> allows you to play &kanagram; using vocabularies of a different language. For this feature to work, you must have vocabularies of a separate language installed.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Get Chalk Font</guibutton></quote> button will be visible if you do not have the chalk-styled font installed on your system. Pressing this button will download the font from the Internet, which &kanagram; will then use after the application has been restarted.
|
||||
</para>
|
||||
<para>
|
||||
Once you have the chalk-styled font installed, the <quote><guilabel>Use standard fonts</guilabel></quote> <interface>checkbox</interface> becomes active. If checked, &kanagram; will display the <interface>blackboard</interface> text in a standard, rather than chalk-styled font. This should aid readability of the text:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; standard font</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="standard-fonts.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; standard font</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guilabel>Use sounds</guilabel></quote> <interface>checkbox</interface> allows you to either allow or suppress the &kanagram; sound effects.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
You need to have &arts; support in kdelibs to hear the sounds.
|
||||
</para>
|
||||
</note>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<sect1 id="vocabularies-config">
|
||||
<title>Vocabularies</title>
|
||||
|
||||
<para>
|
||||
The <guilabel>Vocabularies</guilabel> configuration page allows you to manage your installed vocabularies. Using this dialog, you can <action>edit</action> and <action>remove</action> downloaded vocabularies, as well as <action>create</action> your very own:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; vocabulary settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="vocab-settings.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; vocabulary settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Create New</guibutton></quote> button <action>opens the <link
|
||||
linkend="vocab-editor"><guilabel>Vocabulary Editor</guilabel></link> dialog</action> so that you can author your own vocabularies which you can then play.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Edit</guibutton></quote> button allows you to <action>make changes to vocabularies that you have either created or downloaded off the Internet</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Delete</guibutton></quote> button allows you to <action>delete vocabularies that you have created or downloaded</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
You can select which vocabulary you would like to apply these actions to by using the <interface>list of vocabularies</interface>.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<sect2 id="vocab-editor">
|
||||
<title><guilabel>Vocabulary Editor</guilabel></title>
|
||||
|
||||
<para>
|
||||
The Vocabulary Editor allows you to create your own vocabularies, which &kanagram; can then test you with:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; <guilabel>Vocabulary Editor</guilabel></screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="vocab-editor.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; <guilabel>Vocabulary Editor</guilabel></phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guilabel>Vocabulary Name</guilabel> field lets you <action>name your vocabulary</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guilabel>Description</guilabel> field enables you to <action>expand on your vocabulary name</action>, providing your user with more details of the content of your vocabulary.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
Try to keep both the name and description fields as short as possible. Effective vocabularies cover a narrow, focussed set of words for a single subject. Try to write at least 20 words for your vocabulary, so that it will not be quickly finished by the user.
|
||||
</para>
|
||||
</note>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Delete Word</guibutton></quote> button lets you <action>remove words from your vocabulary</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>New Word</guibutton></quote> button <action>creates a new word entry in your vocabulary</action>, ready for you to expand.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guilabel>Word</guilabel> field lets you <action>write word values into your vocabulary</action>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <guilabel>Hint</guilabel> field allows you to <action>write hints to accompany your words</action>.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
Good hints clearly, yet subtly describe the word, whilst increasing the knowledge of the vocabulary subject for your user. Also ensure that your hints are fairly short (under 40 characters in length).
|
||||
</para>
|
||||
</note>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Save</guibutton></quote> button <action>saves your vocabulary content</action>, and enables its use directly in &kanagram; (it will immediately become available within the application, selectable via. the <interface>Vocabulary Selector</interface>).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
The <quote><guibutton>Close</guibutton></quote> button <action>closes the <guilabel>Vocabulary Editor</guilabel> dialog</action> without saving the content of your vocabulary.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="newstuff-config">
|
||||
<title>New Stuff</title>
|
||||
|
||||
<para>
|
||||
The <guilabel>New Stuff</guilabel> configuration page allows you to obtain new vocabulary files from the Internet:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; new stuff settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="newstuff-settings.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; newstuff settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Click the <quote><guibutton>Download New Vocabularies</guibutton></quote> button to browse the available online content:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kanagram; new stuff dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="newstuff-dialog.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kanagram; new stuff dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
To install a vocabulary from the Internet, click on the vocabulary item in the list, then press the <quote><guibutton>Install</guibutton></quote> button to install to your system. The downloaded vocabulary will then be available to play immediately.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kanagram;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2005 Joshua Keel <email>joshuakeel@gmail.com</email> and &Danny.Allen; &Danny.Allen.mail;
|
||||
</para>
|
||||
<para>
|
||||
Contributors:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Sound effects: Artemio
|
||||
<email>fillme</email>
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2005 &Danny.Allen; &Danny.Allen.mail;
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kanagram">
|
||||
<title>How to obtain &kanagram;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
|
||||
// vim:ts=2:sw=2:tw=78:noet:noai
|
||||
-->
|
||||
|
After Width: | Height: | Size: 8.3 KiB |
|
After Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 33 KiB |
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 39 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 30 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 28 KiB |
@ -0,0 +1,553 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kbruch "<application>KBruch</application>">
|
||||
<!ENTITY kappname "&kbruch;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kbruch; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Sebastian</firstname>
|
||||
<surname>Stein</surname>
|
||||
<affiliation>
|
||||
<address><email>seb.kde@hpfsc.de</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001-2005</year>
|
||||
<holder>Sebastian Stein</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2004-07-09</date>
|
||||
<releaseinfo>3.4</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>&kbruch; is a small program to practice calculating with fractions.
|
||||
Different exercises are provided for this purpose. The program checks user's
|
||||
input and gives feedback.
|
||||
</para>
|
||||
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>education</keyword>
|
||||
<keyword>fraction</keyword>
|
||||
<keyword>mathematics</keyword>
|
||||
<keyword>denominator</keyword>
|
||||
<keyword>kbruch</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&kbruch; is a small program to practice calculating with fractions. Therefore
|
||||
4 different exercises are offered.
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
Fraction Task - in this exercise you have to solve a given fraction task.
|
||||
You have to enter numerator and denominator. This is the main exercise.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Comparison - in this exercise you have to compare the size of 2 given
|
||||
fractions.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Conversion - in this exercise you have to convert a given number into a
|
||||
fraction.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Factorization - in this exercise you have to factorize a given number into its prime factors.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
In all different exercises &kbruch; will generate a task and the user has to
|
||||
solve it. The program checks the input and gives a feedback about it.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
&kbruch; counts how many tasks were solved at all and how many tasks were
|
||||
solved correctly. The statistics are shown to the user, but this part of the
|
||||
main window can be hidden. The user can reset the statistics at any point.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
&kbruch; is very compact and focuses on the core idea of a task generator. An
|
||||
online help system provides context-sensitive help for the different
|
||||
situations.
|
||||
</para>
|
||||
<para>
|
||||
&kbruch; is free and licensed under the &GNU; Public License.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="using-kbruch">
|
||||
<title>Using &kbruch;</title>
|
||||
|
||||
<sect1 id="overview">
|
||||
<title>Main screen</title>
|
||||
|
||||
<para>Here is a screenshot of &kbruch;'s main screen:</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kbruch; main screen, directly after the start</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="gui_main.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kbruch; main screen</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
All action takes place in this screen. This ensures that &kbruch; is
|
||||
easy to use even for young users! The main screen is separated into 5
|
||||
parts:
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
the menubar with the 3 menus <guimenu>Task</guimenu>,
|
||||
<guimenu>Settings</guimenu> and <guimenu>Help</guimenu>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
the toolbar, where you can set the difficulty for the tasks given in the
|
||||
<guimenu>Fraction Task</guimenu> exercise
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
the exercise chooser, where you can switch between the different exercises
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
the task part, where you have to enter the result of the given task
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
the statistical part, where you can see how many tasks have been solved
|
||||
correctly or attempted
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
First you have to choose an exercise in the exercise chooser on the left side
|
||||
of the window. The task part will change according to the chosen task. The
|
||||
settings in the toolbar will be enabled, if you have chosen the exercise
|
||||
<guimenu>Fraction Task</guimenu>.
|
||||
</para>
|
||||
<para>
|
||||
You will find an icon to generate a new task in the toolbar as well. This
|
||||
action is also available in the menu
|
||||
<menuchoice><guimenu>Task</guimenu><guimenuitem>New
|
||||
Task</guimenuitem></menuchoice>. This action is always enabled. If you have not
|
||||
solved the currently given task, a new task is generated and the given task is
|
||||
counted as not correctly solved.
|
||||
</para>
|
||||
<para>
|
||||
You can hide the statistic part by dragging the vertical separator to the
|
||||
right.
|
||||
</para>
|
||||
<para>
|
||||
If you terminate &kbruch; the currently chosen exercise will be saved and
|
||||
restored on next startup.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="statistics">
|
||||
<title>Statistical Part</title>
|
||||
<para>
|
||||
In this part of the main screen you can see:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
how many tasks have been solved
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
how many tasks have been solved correctly
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
how many tasks have been solved incorrectly
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
You can reset the statistics by clicking on the <guimenu>Reset</guimenu> button
|
||||
under the figures.
|
||||
</para>
|
||||
<para>
|
||||
The statistics will be saved on &kbruch;'s termination and restored on next
|
||||
startup.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="settings">
|
||||
<title>Settings Window</title>
|
||||
<para>
|
||||
In this part of the main screen you can adjust some general settings for
|
||||
task display. To open this dialog use
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
&kbruch;</guimenuitem></menuchoice>.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&kbruch; settings dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kbruch; settings dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
In the top part of the dialog you can choose a font for displaying. In the
|
||||
lower part you can choose colors for the different parts of a mathematical
|
||||
expression. You can set wether to show the mixed number notation in the result.
|
||||
This notation is not known everywhere and can be disabled therefore.
|
||||
</para>
|
||||
<para>
|
||||
The settings will be saved on &kbruch;'s termination and restored on the next
|
||||
startup.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="exercises">
|
||||
<title>Exercises</title>
|
||||
|
||||
<sect1 id="exer_fraction">
|
||||
<title>Exercise Fraction Task</title>
|
||||
|
||||
<para>In this exercise you have to solve a given task. Therefor you have to
|
||||
enter numerator and denominator. The difficulty of the generated task can be
|
||||
adjusted by the task parameters described below.
|
||||
</para>
|
||||
|
||||
<sect2 id="task_paras">
|
||||
<title>Task Parameters</title>
|
||||
<para>
|
||||
There are 3 parameters which influence the difficulty of the generated
|
||||
tasks:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><guilabel>Terms</guilabel></term>
|
||||
<listitem><para>The number of terms (separate fractions) given in each
|
||||
task. From 2 to 5, inclusive.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Max. main denominator</guilabel></term>
|
||||
<listitem><para>The highest number &kbruch; will use as the main denominator in the
|
||||
tasks it sets. From a minimum of 10 to a maximum of 50.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Operations</guilabel></term>
|
||||
<listitem><para>Operations which should be used in the
|
||||
task: <guilabel>Addition/Subtraction</guilabel>,
|
||||
<guilabel>Multiplication/Division</guilabel> or <guilabel>All Operations Mixed</guilabel>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>
|
||||
After you have changed the parameters you have to click on the <guimenu>New
|
||||
Task</guimenu> button in the toolbar to generate a task which uses the new
|
||||
parameters. You can also call this action from the menubar with
|
||||
<menuchoice><guimenu>Task</guimenu><guimenuitem>New
|
||||
Task</guimenuitem></menuchoice>.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
Your selection of the maximum main denominator will be reset to a default
|
||||
value every time you change the number of terms. So you should change the
|
||||
number of terms first and then select the maximum main denominator.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
If you have not solved the current task and call the <guimenu>New
|
||||
Task</guimenu> action, the task will be counted as not solved correctly. To
|
||||
prevent this you have to change the parameters after you solved the task but
|
||||
before generating a new one.
|
||||
</para>
|
||||
<para>
|
||||
The chosen parameters will be saved on &kbruch;'s termination and restored
|
||||
on next startup.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="exer_fraction_solve_task">
|
||||
<title>Solving Tasks</title>
|
||||
<para>
|
||||
After you have solved a given task, you need to enter the result into the two
|
||||
input boxes. In the upper box you enter the numerator and in the lower
|
||||
box the denominator.
|
||||
</para>
|
||||
<para>
|
||||
If the result is negative, you can enter a minus sign in front of the numerator
|
||||
or denominator. If the result is 0, just type a 0 in the numerator input field.
|
||||
If the result has a denominator of 1, you can leave the lower box empty.
|
||||
</para>
|
||||
<para>
|
||||
After you have entered the result you should click the <guibutton>Check
|
||||
Task</guibutton> button below the input boxes. &kbruch; will check your input
|
||||
and present the correct result. Therefore the screen changes a little, as
|
||||
you can see in the screenshot:
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Checked Task</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="checked.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Checked Task</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
This task was solved correctly. The correct value is shown in 2 different
|
||||
forms. The second form just in front of the word <guilabel>CORRECT</guilabel>
|
||||
is only used in some countries and must be read as 2 + 1/5 in the given case.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
You always have to enter the result reduced, because most teachers only
|
||||
give all points to reduced results. &kbruch; will show you a short message
|
||||
like the one in the screenshot below, if you enter the correct result
|
||||
unreduced.
|
||||
</para>
|
||||
</note>
|
||||
<screenshot>
|
||||
<screeninfo>Unreduced Result</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="reduced.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Unreduced Result</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
To continue with the next task, click on the <guimenu>Next Task</guimenu>
|
||||
button. If you want to change the parameters for the next task please do this
|
||||
before clicking on the <guimenu>Next Task</guimenu> button.
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="exer_compare">
|
||||
<title>Exercise Comparison</title>
|
||||
|
||||
<para>In this exercise you have to compare 2 given fractions. You have to choose
|
||||
the bigger fraction of both by selecting the correct comparison sign.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Exercise Comparison</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="compare.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Exercise Comparison</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>First choose the correct comparison sign. To toggle the comparison sign,
|
||||
you have to click on the button showing the comparison sign. After you have
|
||||
chosen the comparison sign click on the <guimenu>Check Task</guimenu> button.
|
||||
&kbruch; will check your input and present the correct result. After this step
|
||||
you will get to the next task by clicking on the <guimenu>Next Task</guimenu>
|
||||
button.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="exer_convert">
|
||||
<title>Exercise Conversion</title>
|
||||
|
||||
<para>In this exercise you have to convert a given number into a fraction. You
|
||||
have to enter numerator and denominator.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Exercise Conversion</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="convert.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Exercise Conversion</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>On the left side of the equal sign in the screenshot above you can see a
|
||||
recurring decimal. This means, that the fraction shown as a decimal has a
|
||||
repeating part. The repeating part is marked with the small bar above the
|
||||
numbers. Those numbers repeat ad infinitum.
|
||||
</para>
|
||||
|
||||
<para>After you have entered the numerator and denominator click on the
|
||||
<guimenu>Check Task</guimenu> button. &kbruch; will check your input and
|
||||
present the correct result. After this step you will get to the next task by
|
||||
clicking on the <guimenu>Next Task</guimenu> button.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
Do not forget to enter the result reduced. Unreduced results will be counted as
|
||||
solved not correctly.
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="exer_factorize">
|
||||
<title>Exercise Factorization</title>
|
||||
|
||||
<para>In this exercise you have to factorize a given number into its prime
|
||||
factors. You have to enter all prime factors of the number.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Exercise Factorization</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="factorize.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Exercise Factorization</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>You can enter a factor by clicking on the prime <guimenu>factor
|
||||
buttons</guimenu>. The currently entered prime factors will be shown in the
|
||||
field next to the number to be factorized. You can remove the last entered
|
||||
prime factor by clicking on the <guimenu>Remove Last Factor</guimenu> button.
|
||||
</para>
|
||||
<para>
|
||||
After you have entered all prime factors click on the
|
||||
<guimenu>Check Task</guimenu> button. &kbruch; will check your input and
|
||||
present the correct result. After this step you will get to the next task by
|
||||
clicking on the <guimenu>Next Task</guimenu> button.
|
||||
</para>
|
||||
|
||||
<para>In the screenshot at the top of this page you can see a <quote>*</quote>
|
||||
between the prime factors. This is the multiplication sign. The product of all
|
||||
prime factors must be the number you try to factorize.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
You have to enter all prime factors even when a prime factor repeats several
|
||||
times. Example: As prime factors of number 18 you have to enter 2, 3 and 3.
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
<para>&kbruch;</para>
|
||||
<para>
|
||||
Program and documentation Copyright, 2001-2004 Sebastian Stein
|
||||
<email>seb.kde@hpfsc.de</email>
|
||||
</para>
|
||||
|
||||
<para>Thank you goes to:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>&Anne-Marie.Mahfouf; for managing the &kde;-edu project</para></listitem>
|
||||
<listitem><para>Klas Kalass for helping design the interface</para></listitem>
|
||||
<listitem><para>Eva Brucherseifer for writing <application>KMath</application> (&kbruch;'s &GUI; is based on this work)</para></listitem>
|
||||
<listitem><para>Dominique Devriese for bug fixing</para></listitem>
|
||||
<listitem><para><ulink url="http://www.net-tex.de/">Stefan Schumacher</ulink> for testing a very early version</para></listitem>
|
||||
<listitem><para><ulink url="http://www.guckes.net/">Sven Guckes</ulink> for testing the text interface (which has been removed)</para></listitem>
|
||||
<listitem><para>&David.Faure; for helping with &kde; <acronym>CVS</acronym> and &kde; Bugzilla</para></listitem>
|
||||
<listitem><para>&Robert.Gogolok; for helping with &kde; <acronym>CVS</acronym></para></listitem>
|
||||
<listitem><para>John Kesson for proof reading the handbook</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kbruch">
|
||||
<title>How to obtain &kbruch;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="requirements">
|
||||
<title>Requirements</title>
|
||||
|
||||
<para>
|
||||
In order to successfully use &kbruch;, you need &kde; > 3.1 .
|
||||
</para>
|
||||
|
||||
<para>
|
||||
&kbruch; itself can be found
|
||||
on <ulink url="http://edu.kde.org/kbruch/">the &kbruch; home page</ulink>
|
||||
and it is part of the &kde;-edu project</para>
|
||||
|
||||
<para>You can find a list of changes in the <acronym>CVS</acronym> commit
|
||||
messages.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
|
||||
// vim:ts=2:sw=2:tw=78:noet
|
||||
-->
|
||||
@ -0,0 +1,56 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author>&Lauri.Watts;&Lauri.Watts.mail;</author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>kbruch</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>kbruch</command></refname>
|
||||
<refpurpose>Learn calculating with fractions</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>kbruch</command>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kbruch; is a small program to practice calculating with fractions.
|
||||
Different exercises are provided for this purpose. The program checks user's
|
||||
input and gives feedback.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kbruch">help:/kbruch</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kbruch</parameter></userinput>).</para>
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kbruch/">the kde-edu website</ulink></para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&kbruch; was written by
|
||||
<personname><firstname>Sebastian</firstname><surname>Stein</surname></personname> <email>seb.kde@hpfsc.de</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 50 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
@ -0,0 +1,334 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&keduca;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &keduca; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Javier</firstname>
|
||||
<othername>J.</othername>
|
||||
<surname>Campos</surname>
|
||||
<affiliation>
|
||||
<address><email>&Javier.J.Campos.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>1999</year>
|
||||
<holder>&Javier.J.Campos;</holder>
|
||||
</copyright>
|
||||
|
||||
<date>2002-10-08</date>
|
||||
<releaseinfo>1.1</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>&keduca; is flash card application, which allows you to make
|
||||
interactive form based tests.</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>KEduca</keyword>
|
||||
<keyword>test</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>&keduca; is flash card application, which allows you to make
|
||||
interactive form based tests.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&keduca; screenshot</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="screenshot.png" format="PNG" />
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&keduca; screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</chapter>
|
||||
<!--
|
||||
<chapter id="create-modify-test">
|
||||
<title>Creating a New Test</title>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="configuration">
|
||||
<title>Configuring &keduca;</title>
|
||||
|
||||
</chapter>
|
||||
-->
|
||||
<chapter id="command-reference">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="file-menu">
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<sect2 id="main-window-file-menu">
|
||||
<title>The <guilabel>Main Window</guilabel> <guimenu>File</guimenu>
|
||||
Menu</title>
|
||||
|
||||
<para>The <guilabel>Main Window</guilabel> has the following
|
||||
entries:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><!-- <shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>
|
||||
</shortcut> -->
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Open an existing test file.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guisubmenu>Open Recent</guisubmenu>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Open a recently used test file.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Close</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>
|
||||
Close the currently open test file.
|
||||
</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quit</action> &keduca;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="edit-test-window-file-menu">
|
||||
<title>The Editing Window <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Create a new test</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Open an existing test file.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guisubmenu>Open Recent</guisubmenu>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Open a recently used test file.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Save the currently open
|
||||
test.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save As...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Save the currently open game with a new
|
||||
name.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Close</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>
|
||||
Close the currently open test file.
|
||||
</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Print...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Print the currently open
|
||||
test.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quit</action> &keduca;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="build-menu">
|
||||
<title>The <guimenu>Build</guimenu> Menu</title>
|
||||
|
||||
<para>The <guimenu>Build</guimenu> menu exists only in the
|
||||
<guilabel>Main Window</guilabel> of &keduca;.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Build</guimenu>
|
||||
<guimenuitem>Create/Modify...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Create or modify a test</action> in the Create or Modify a test
|
||||
window.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="settings-menu">
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<para>The first entries are available in both of the main &keduca;
|
||||
windows.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show Toolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Toggle on and off the display of the toolbar.</action>
|
||||
The default is on.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Personalize the keybindings</action> for &keduca;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Personalize the toolbars</action> for &keduca;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>The following entry is only available in the <guilabel>Main
|
||||
Window</guilabel>.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &keduca;</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Customize</action> &keduca;. The options available to
|
||||
you are described in the Configuration chapter.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="help-menu">
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
|
||||
&help.menu.documentation;
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits-and-licenses">
|
||||
<title>Credits and Licenses</title>
|
||||
|
||||
<para>&keduca; is copyright 2001, Javier Campos.</para>
|
||||
|
||||
<para>Documentation partly by &Lauri.Watts; &Lauri.Watts.mail;</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
<!--
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
&install.compile.documentation;
|
||||
</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,67 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author>&Lauri.Watts;&Lauri.Watts.mail;</author>
|
||||
<date>March 16, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
<refmeta>
|
||||
<refentrytitle><command>keduca</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>keduca</command></refname>
|
||||
<refpurpose>Interactive form-based tests and exams.</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>keduca</command>
|
||||
<group><option>file</option></group>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&keduca; is flash card application, which allows you to make
|
||||
interactive form based tests.</para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry><term><option><replaceable>file</replaceable></option></term>
|
||||
<listitem><para>File to load</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/keduca">help:/keduca</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/keduca</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at the <ulink
|
||||
url="http://edu.kde.org/keduca/">KDE Educatainment project website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&keduca; was written by <personname><firstname>Javier</firstname><surname>Campos</surname></personname></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,74 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>2005-05-27</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>keducabuilder</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>keducabuilder</command></refname>
|
||||
<refpurpose>test/exam editor for keduca</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>keducabuilder</command>
|
||||
<group><option>file</option></group>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para><application>KEducaBuilder</application> is the test editor for
|
||||
&keduca;, a flash-card application for working with interactive form-based
|
||||
tests. KEducaBuilder is used to create and edit these tests, whereas
|
||||
&keduca; itself can be used to view and take these tests. </para>
|
||||
<para>This application is part of the &kde; edutainment module. </para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><option><replaceable>file</replaceable></option></term>
|
||||
<listitem><para>Filename to load in the editor</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>keduca(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/keduca">help:/&keduca;</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/keduca</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at the <ulink url="http://edu.kde.org/keduca/">&kde; Edutainment website:</ulink></para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&keduca; was written by <personname><firstname>Javier</firstname><surname>Campos</surname></personname></para><para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email>.</para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 25 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 9.8 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 33 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 2.6 KiB |
|
After Width: | Height: | Size: 6.4 KiB |
|
After Width: | Height: | Size: 4.4 KiB |
|
After Width: | Height: | Size: 711 B |
|
After Width: | Height: | Size: 8.1 KiB |
|
After Width: | Height: | Size: 2.3 KiB |
@ -0,0 +1,655 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kgeography "<application>KGeography</application>">
|
||||
<!ENTITY kappname "&kgeography;">
|
||||
<!ENTITY package "playground/edu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kgeography; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<personname>
|
||||
<firstname>Anne-Marie</firstname>
|
||||
<surname>Mahfouf</surname>
|
||||
</personname>
|
||||
<email>&Anne-Marie.Mahfouf.mail;</email>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
|
||||
<copyright>
|
||||
<year>2005</year>
|
||||
<holder>&Anne-Marie.Mahfouf;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-08-02</date>
|
||||
<releaseinfo>0.4</releaseinfo>
|
||||
|
||||
<!-- Abstract about this handbook -->
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kgeography; is a geography learning tool for &kde;. Right now it has six usage modes:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Browse the maps clicking in a map division to see its name, capital and flag</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The game tells you a map division name and you have to click on it</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>The game tells you a capital and you have to guess the division it belongs to</para>
|
||||
</listitem><listitem>
|
||||
<para>The game tells you a division and you have to guess its capital</para>
|
||||
</listitem><listitem>
|
||||
<para>The game shows you a map division flag and you have to guess its name</para>
|
||||
</listitem><listitem>
|
||||
<para>The game tells you a map division name and you have to guess its flag</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
</abstract>
|
||||
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>KGeography</keyword>
|
||||
<keyword>geography</keyword>
|
||||
<keyword>maps</keyword>
|
||||
<keyword>countries</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<!-- The introduction chapter contains a brief introduction for the
|
||||
application that explains what it does and where to report
|
||||
problems. Basically a long version of the abstract. Don't include a
|
||||
revision history. (see installation appendix comment) -->
|
||||
|
||||
<para>
|
||||
&kgeography; is a geography learning tool for &kde;. It allows you to learn about the political divisions of some countries (divisions, capitals of those divisions and their associated flags if there are some).
|
||||
</para>
|
||||
<para>
|
||||
Maps available in current release are: Africa, Asia, Austria, Brazil, Canada, China, Europe, France, Germany, Italy, Italy by provinces, North and Central America, Norway, Poland, South America, Spain, USA and the world.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="quick-start">
|
||||
<title>Quick Start to &kgeography;</title>
|
||||
<para>
|
||||
When you run &kgeography; for the first time, it first asks you to choose a map to start with.
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kgeography; at first start</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here's a screenshot of &kgeography; at first start</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Here we choose Canada
|
||||
<screenshot>
|
||||
<screeninfo>Canada is choosen</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Canada is choosen</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
And &kgeography; main window appears with the map of Canada:
|
||||
<screenshot>
|
||||
<screeninfo>&kgeography; main window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start3.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kgeography; main window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
You can then choose what type of learning or testing you want to do by looking at the menu on the left:
|
||||
<screenshot>
|
||||
<screeninfo>&kgeography; menu</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start4.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kgeography; menu</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Browse the map: a &LMB; click on an area of the map will display informations about that area:
|
||||
<screenshot>
|
||||
<screeninfo>Browse the map</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start5.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Browse the map</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Click division in the map: you are first asked how many questions you want
|
||||
<screenshot>
|
||||
<screeninfo>How many questions</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start6.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>How many questions</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Then you are asked to click on a specific province:
|
||||
<screenshot>
|
||||
<screeninfo>Click on a province</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start7.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Click on a province</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
When you finish all the questions, a result dialog is shown with your correct and uncorrect answers:
|
||||
<screenshot>
|
||||
<screeninfo>Your results</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start8.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Your results</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Guess a division from its capital: you are asked to find the name of a province among a choice of 4 given its capital:
|
||||
<screenshot>
|
||||
<screeninfo>Guess a division from its capital</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start9.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Guess a division from its capital</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
And the results are displayed when the test is finished:
|
||||
<screenshot>
|
||||
<screeninfo>Your results</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start10.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Your results</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Guess the capital from a division: you have a capital and four province names and you must choose the correct one. As before, at the end a result dialog is shown.
|
||||
</para>
|
||||
<para>
|
||||
Guess division from its flag: a flag is shown and you must find the province it belongs to.
|
||||
<screenshot>
|
||||
<screeninfo>the flag question</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start11.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>the flag question</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Guess the flag of a division: a province name is given and you must find the correct flag among four.
|
||||
<screenshot>
|
||||
<screeninfo>match the flag with the province</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="first-start12.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>match the flag with the province</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="using-kapp">
|
||||
<title>Using &kgeography;</title>
|
||||
|
||||
<para>
|
||||
&kgeography; displays informations about some countries and tests you about those informations.
|
||||
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kgeography;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="kgeography.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
|
||||
<sect1 id="kapp-features">
|
||||
<title>More &kgeography; features</title>
|
||||
|
||||
<para>Another feature of &kgeography; is the possibility of zoom on a map.
|
||||
<screenshot>
|
||||
<screeninfo>Zoom</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="zoom.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Zoom</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
While in zoom mode, you can press &RMB; to go back to the original map size (the <guimenuitem>Original Size</guimenuitem> action has the same effect). Use the scroll bars to move around the zoomed map or use the <guimenuitem>Move</guimenuitem> action that will allow you to drag the map using &LMB;.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<!--<chapter id="teachers-parents">
|
||||
<title>Teachers/Parents guide to &kgeography; </title>
|
||||
This chapter should emphasize the educational aims of your app and
|
||||
guide the parent/teacher on how to help the child using it.
|
||||
</chapter>-->
|
||||
|
||||
<chapter id="how-to-maps">
|
||||
<title>How to make maps</title>
|
||||
<para>A map in &kgeography; is made by two files, one is the image of the map and the other one is its description. </para>
|
||||
<sect1 id="helper-tool">
|
||||
<title>Helper tool</title>
|
||||
<para>
|
||||
You can find <ulink url="http://kgeography.berlios.de/gen_map.pl">here</ulink> a tool (made by Yann Verley) which helped him with the map of France. To find out its usage, simply execute it and read the help message. It basically creates the <literal role="extension">.kgm</literal> file from a plain text file and creates a file with the colors it has assigned to each division, so you can fill the map according to them.</para>
|
||||
</sect1>
|
||||
<sect1 id="description-file">
|
||||
<title>Description file</title>
|
||||
<para>
|
||||
The description file is needed and its file extension is <literal role="extension">.kgm</literal>. It should begin with <sgmltag class="starttag">map</sgmltag> and end with <sgmltag class="endtag">map</sgmltag>.
|
||||
</para>
|
||||
<para>
|
||||
Inside of those tags there should be:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">mapFile</sgmltag> and <sgmltag class="endtag">mapFile</sgmltag>: the name of the file (without any path) containing the map image, ⪚ <quote>europe.png</quote>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">name</sgmltag> and <sgmltag class="endtag">name</sgmltag>: the name of map, ⪚ <quote>Europe</quote>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>A <sgmltag class="starttag">division</sgmltag> and <sgmltag class="endtag">division</sgmltag> for each division in the map.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
Each division has these tags:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">name</sgmltag> and <sgmltag class="endtag">name</sgmltag>: the name of the division, ⪚ <quote>Albania</quote>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">capital</sgmltag> and <sgmltag class="endtag">capital</sgmltag>: the name of the capital of the division, ⪚ <quote>Tirana</quote>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">ignore</sgmltag> and <sgmltag class="endtag">ignore</sgmltag>: can be set to <userinput>yes</userinput>, <userinput>allowClickMode</userinput> and <userinput>no</userinput>. If this tag is set to <userinput>yes</userinput> then the division will be ignored when asking for divisions in that map. It is then as if this division does not exist in &kgeography; quiz modes. If this tag is set to <userinput>allowClickMode</userinput> then &kgeography; will ask for the division in the <guibutton>Click Division in Map...</guibutton> mode but not in other quiz modes. Setting this tag to <userinput>no</userinput> means the division will appear in all modes (browse and quizzes). This tag is optional and when there is no <sgmltag class="starttag">ignore</sgmltag> tag that means as it is set to <userinput>no</userinput>. For example <quote>Algeria</quote> has this tag set to <userinput>yes</userinput> in the <quote>Europe</quote> map which means that <quote>Algeria</quote> will not be part of any quiz in the <quote>Europe</quote> map.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">flag</sgmltag> and <sgmltag class="endtag">flag</sgmltag>: the file (without any path) containing the flag of the division, ⪚ <quote>albania.png</quote>. This tag is optional. Not needed for the divisions whose <sgmltag class="starttag">ignore</sgmltag> tag is set to <userinput>yes</userinput>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">color</sgmltag> and <sgmltag class="endtag">color</sgmltag>: the color the division has in the map.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
The color is defined using three tags:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">red</sgmltag> and <sgmltag class="endtag">red</sgmltag>: red component of the color. Valid values are between 0 and 255.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">green</sgmltag> and <sgmltag class="endtag">green</sgmltag>: green component of the color. Valid values are between 0 and 255.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><sgmltag class="starttag">blue</sgmltag> and <sgmltag class="endtag">blue</sgmltag>: blue component of the color. Valid values are between 0 and 255.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<tip>
|
||||
<para>
|
||||
It is convenient to create 2 or 3 false divisions like <quote>Water</quote>, <quote>Frontier</quote> and <quote>Coast</quote> and set them with the <sgmltag class="starttag">ignore</sgmltag> tag set to <userinput>yes</userinput>.
|
||||
</para>
|
||||
</tip>
|
||||
<important>
|
||||
<para>All names (capitals and divisions) must be in English.</para>
|
||||
</important>
|
||||
</sect1>
|
||||
<sect1 id="map-file">
|
||||
<title>Map file</title>
|
||||
<para>
|
||||
The map file is quite simple but laborious to create. It has to be in <acronym>PNG</acronym> format.
|
||||
You can find some maps to transform at <ulink url="https://www.cia.gov/cia/publications/factbook/docs/refmaps.html">Cia Reference Maps</ulink>. If no map fits your needs you can download the <ulink url="https://www.cia.gov/cia/publications/factbook/reference_maps/pdf/political_world.pdf">political world map</ulink>, take a screenshot of it and work from it.
|
||||
Each division in the map should have one and only one color. To achieve this you can use image processing programs like <application>The Gimp</application> and <application>Kolourpaint</application>.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="flags">
|
||||
<title>Flags</title>
|
||||
<para>
|
||||
If you have used the <sgmltag class="starttag">flag</sgmltag> tag you should provide the flag files. They have to be in <acronym>PNG</acronym> format and better if they are 300x200 pixels and you provide a <acronym>SVG</acronym> file for it. To obtain <acronym>SVG</acronym> flags of almost all countries in the world and some other divisions, you can consult the <ulink url="http://www.sodipodi.com/index.php3?section=clipart/flags">Sodipodi flags collection</ulink>.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="how-to-test">
|
||||
<title>How to test</title>
|
||||
<para>
|
||||
Before sending your map to Albert <email>tsdgeos@terra.es</email>, you should test it to see it has no errors. To achieve that, you have to do the following:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Put the map description and map image file in <filename class="directory">$<envar>KDEDIR</envar>/share/apps/kgeography/</filename></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Put the flag <acronym>PNG</acronym> files (if any) in <filename class="directory">$<envar>KDEDIR</envar>/share/apps/kgeography/flags/</filename></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
Once that has been done you should be able of opening your map from inside &kgeography;.
|
||||
</para>
|
||||
<para>
|
||||
If you don't know which is your <filename class="directory">$<envar>KDEDIR</envar></filename>, type <userinput><command>kde-config</command> <option>--prefix</option></userinput> in a shell.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="non-political-maps">
|
||||
<title>Non political maps</title>
|
||||
<para> Is it possible to do non-political maps? Yes, it is!
|
||||
<screenshot>
|
||||
<screeninfo>Example of how to create a non political map</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="river.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Example of how to create a non political map</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
Of course, the division concept can be extended to a river or a mountain. During the creation of the map, you should keep in mind that most times the river or mountain will be too small that you should provide an additional clicking area.
|
||||
In this example the river would have the maroon area and color <20,76,34> as its identifier.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<!-- (OPTIONAL, BUT RECOMMENDED) This chapter should list all of the
|
||||
application windows and their menubar and toolbar commands for easy reference.
|
||||
Also include any keys that have a special function but have no equivalent in the
|
||||
menus or toolbars. This may not be necessary for small apps or apps with no tool
|
||||
or menu bars. -->
|
||||
|
||||
<sect1 id="kapp-mainwindow">
|
||||
<title>The main &kgeography; window</title>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
<para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Map...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Open the choose map dialog</action></para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quits</action> &kgeography;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>View</guimenu> Menu</title>
|
||||
<para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>View</guimenu>
|
||||
<guimenuitem>Zoom</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Goes in zoom mode</action></para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>View</guimenu>
|
||||
<guimenuitem>Original Size</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Sets</action> the map back to its original size</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>View</guimenu>
|
||||
<guimenuitem>Move</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Moves</action> the current map</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
<para>
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show/Hide Toolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Show/Hide the &kgeography; toolbar.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure key shortcuts for &kgeography;.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure the &kgeography; toolbar.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
|
||||
<!-- Assuming you have a standard help menu (help, what's this, about -->
|
||||
<!-- &kgeography;, about KDE) then the documentation is already written. -->
|
||||
<!-- The following entity is valid anywhere that a variablelist is -->
|
||||
<!-- valid. -->
|
||||
|
||||
&help.menu.documentation;
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<!--<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<qandaset id="faqlist">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>My Mouse doesn't work. How do I quit &kgeography;?</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 am I not able to 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>
|
||||
|
||||
<para>
|
||||
&kgeography;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2004-2005 Albert Astals Cid <email>tsdgeos@terra.es</email>
|
||||
</para>
|
||||
|
||||
|
||||
<para>
|
||||
Documentation Copyright © 2005 &Anne-Marie.Mahfouf; <email>&Anne-Marie.Mahfouf.mail;</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kapp">
|
||||
<title>How to obtain &kgeography;</title>
|
||||
|
||||
<!-- This first entity contains boiler plate for applications that are
|
||||
part of KDE CVS. You should remove it if you are releasing your
|
||||
application -->
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
<!-- This entity contains the boilerplate text for standard -->
|
||||
<!-- compilation instructions. If your application requires any -->
|
||||
<!-- special handling, remove it, and replace with your own text. -->
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
</appendix>
|
||||
|
||||
&documentation.index;
|
||||
</book>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: xml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
End:
|
||||
|
||||
vim:tabstop=2:shiftwidth=2:expandtab
|
||||
-->
|
||||
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 594 B |
|
After Width: | Height: | Size: 32 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 15 KiB |
@ -0,0 +1,929 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&khangman;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &khangman; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Anne-Marie</firstname>
|
||||
<surname>Mahfouf</surname>
|
||||
<affiliation>
|
||||
<address>&Anne-Marie.Mahfouf.mail;</address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
|
||||
<copyright>
|
||||
<year>2001</year><year>2005</year>
|
||||
<holder>&Anne-Marie.Mahfouf;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
|
||||
<date>2006-02-01</date>
|
||||
<releaseinfo>1.6</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&khangman; is the classic hangman game for children, adapted for &kde;.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>KHangMan</keyword>
|
||||
<keyword>hangman</keyword>
|
||||
<keyword>game</keyword>
|
||||
<keyword>child</keyword>
|
||||
<keyword>words</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&khangman; is a game based on the well-known hangman game. It is aimed at
|
||||
children aged six and over. The game has four levels of difficulty: Animals (animals
|
||||
words), Easy, Medium and Hard. A word is picked at random, the letters are
|
||||
hidden, and you must guess the word by trying one letter after another. Each
|
||||
time you guess a wrong letter, part of a picture of a hangman is drawn. You
|
||||
must guess the word before being hanged! You have 10 tries.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="using-khangman">
|
||||
<title>Using &khangman;</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &khangman; when you start it for the first time</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="khangman1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&khangman; screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Here you can see &khangman; as it is the first time you run it. Level is Animals,
|
||||
language is default (English here, the default is your current &kde; language if
|
||||
the data exists), the theme is "Sea". Any changes in level, language or theme
|
||||
(background) are written in the configuration file and restored in your next
|
||||
game.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Please note how easy it is to change the level and the theme, just
|
||||
click on the combo boxes on the toolbar. Getting a new word and quitting the
|
||||
game are also easily done by clicking on the corresponding buttons on the
|
||||
toolbar.
|
||||
</para>
|
||||
|
||||
<sect1 id="general-usage">
|
||||
<title>General usage</title>
|
||||
|
||||
<!-- FIXME: A word cannot really be displayed and hidden at the same time, -->
|
||||
<!-- although I cannot think of a better way to phrase this -->
|
||||
<para>A word is chosen and its letters are displayed as an underscore (_) symbol. You know how many letters there are in the
|
||||
word. You have to guess the word by trying one letter after another. You enter the letter in the text box and you either press the Enter key or click on the Guess button to see if the letter belongs or not to the word. </para>
|
||||
|
||||
<para>The word is picked at random and it is not the same as the previous word.
|
||||
</para>
|
||||
|
||||
<important><para>All the words are nouns (there are no verbs or adjectives, &etc;).</para></important>
|
||||
|
||||
<para>
|
||||
Usually, it is not important whether you type in lowercase or uppercase. The program
|
||||
converts all input into lowercase (except for German words beginning with an uppercase letter). The program does that automatically.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The current level and current language are displayed in the statusbar.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Each time you guess a letter that is not in the word, another part of the
|
||||
hangman is drawn. You have 10 tries to guess the word. After that, the correct
|
||||
answer is displayed.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There are 4 levels: easy, medium, hard and animals, plus levels for other
|
||||
topics in some languages. The program scans for all data files in all
|
||||
languages.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In the easy level, the words are quite simple and related to everyday life. It
|
||||
is suitable for children from 6 to 9. The animals level contains only names of
|
||||
animals so they are easier to find. Some of them are easy, others are more
|
||||
difficult. In the medium level, the words are longer and more difficult. It is
|
||||
suitable for ages 9+. The hard level is just that, hard, &ie; the words are
|
||||
difficult to spell and not very well known. This level is challenging, even for
|
||||
adults.
|
||||
</para>
|
||||
|
||||
<para>After a word is guessed (or the hangman is completed), you are
|
||||
prompted for another word and you can either use the
|
||||
<keycap>Y</keycap> or <keycap>N</keycap> keys or the mouse to answer
|
||||
yes or no. If you say <guilabel>No</guilabel>, the game quits. If you
|
||||
say <guilabel>Yes</guilabel>, another word is ready to be guessed.
|
||||
</para>
|
||||
|
||||
<para>You type the letter you want to try in the text box (the mouse cursor is
|
||||
ready in the text box) and you hit the &Enter; key. If the letter belongs to the
|
||||
word, it takes its place, as many times as it appears in the word. If the
|
||||
letter does not belong to the word, it goes in the Misses field and a further
|
||||
part of the hangman is drawn on the right. You have ten tries and after that
|
||||
you lose and the correct word is displayed.
|
||||
</para>
|
||||
|
||||
<para>During the game, you can choose to start a new game by going in the
|
||||
<guimenu>Game</guimenu> menu and choosing <guimenuitem>New</guimenuitem> or
|
||||
clicking on the <guiicon>New</guiicon> icon on the toolbar. You can also change
|
||||
the level with the level button on the toolbar (this will bring you a new word
|
||||
for the new level).</para>
|
||||
|
||||
<para>
|
||||
Future improvement (in &kde; 4) will allow you to create your own words file.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="languages">
|
||||
<title>Playing in different languages</title>
|
||||
<para>
|
||||
You can play &khangman; in twenty-four languages: Brazilian Portuguese, Bulgarian, Catalan, Czech, Danish, Dutch, English,
|
||||
Finnish, French, German, Hungarian, Irish (Gaelic), Italian, Norwegian (Bokmål), Norwegian (Nynorsk), Portuguese, Spanish, Serbian (Latin and Cyrillic), Slovenian, Tajik, Swedish, Russian and Turkish.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
By default, after the first installation of &khangman;, only English and your &kde; language if it is one of the above and if you have the corresponding kde-i18n package will be installed. For example if you are a Danish user and if you have &kde; in Danish, in <guimenu>Languages</guimenu> you will see two items: English and Danish and Danish will be the default.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You can still play &khangman; in other languages. It is very easy to add new data in &khangman;. All you need is a working Internet connection.
|
||||
You click on the <guimenu>File</guimenu> menu and then on <guimenu>Get Words in New Language...</guimenu>. A dialog appears, similar to this one:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The Get New Words dialog for &khangman;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="getnewstuff.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The Get New Words dialog for &khangman;</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Click on the language name you want to install and then on the <guibutton>Install</guibutton> button. If the language is successfully installed, a green tick is displayed in front of the language name. You click on the <guibutton>Close</guibutton> button to close the Get New Words dialog (if you want another language, you get repeat these steps).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You can then easily change the language by going in the <guimenu>Languages</guimenu> and choose the new language.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Please note that you can now type the special characters in a language by displaying the <interface>Special Characters Toolbar</interface>.
|
||||
This toolbar holds buttons with an icon of each special character per language like é in French for example. Clicking on such a
|
||||
button will write the corresponding letter in the input line and you validate your choice with Enter. You can of course also use the keyboard layout corresponding to the language. This toolbar can be shown or hidden. The setting is restored next time you play &khangman;.
|
||||
</para>
|
||||
|
||||
<important><para>
|
||||
Please note that you need Arial and URW Bookman fonts in order to display the special characters correctly in some languages. Provided you have those fonts installed, &khangman; will automatically use them. If you see small squares instead of letters, then you may not have one of these fonts installed. Type <command>fonts:/</command> into the &konqueror; address bar to check which fonts you have installed.
|
||||
</para></important>
|
||||
|
||||
</sect1>
|
||||
<sect1 id="few-tips">
|
||||
<title>A few tips</title>
|
||||
<para>
|
||||
Try to guess the vowels first. Then have a go with the most common consonants:
|
||||
l, t, r, n, s
|
||||
</para>
|
||||
<para>corresponding:
|
||||
when you see <quote>io</quote>, try n after that, in French and English.
|
||||
</para>
|
||||
<para>
|
||||
In Brazilian Portuguese, Catalan, Spanish and Portuguese, the accented
|
||||
vowels can be discovered when you type the non accented corresponding
|
||||
vowel. For example, all the accented <quote>a</quote> are displayed in
|
||||
the word when you type <quote>a</quote>. This is when <guilabel>Type accented
|
||||
letters</guilabel> on the <guilabel>Languages</guilabel> page of &khangman;'s
|
||||
configuration dialog is not checked. When <guilabel>Type accented
|
||||
letters</guilabel> is checked, then you have to type
|
||||
the accented letters yourself. When you type <quote>a</quote>, only
|
||||
<quote>a</quote> is displayed and you have to type for example
|
||||
ã for this letter to be displayed.
|
||||
</para>
|
||||
<para>
|
||||
Did you know? In English, the most common letter is e (12.7%), followed by t
|
||||
(9.1%) then a (8.2%), i (7.0%) and n (6.7%).
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="menus">
|
||||
<title>Menubar and toolbars</title>
|
||||
|
||||
<sect1 id="mainwindow">
|
||||
<title>The Main &khangman; Window</title>
|
||||
|
||||
<para>The <guimenu>Game</guimenu> menu has 3 items:
|
||||
<guimenuitem>New</guimenuitem>, <guimenuitem>Get Words in New Language...</guimenuitem> and
|
||||
<guimenuitem>Quit</guimenuitem>.</para>
|
||||
|
||||
<para><guimenuitem>New</guimenuitem> brings you a new game, &ie; a new
|
||||
word to guess, in the same level you already
|
||||
are. <guimenuitem>Get Words in New Language...</guimenuitem> will display the Get New Stuff dialog to allow you to download data in a new language. <guimenuitem>Quit</guimenuitem> quits the game by closing the
|
||||
main window and writing the actual settings in the configuration
|
||||
file.</para>
|
||||
|
||||
<para>
|
||||
The <guimenu>Level</guimenu> menu allows you to choose the level, &ie; the difficulty of the word to guess.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <guimenu>Languages</guimenu> menu allows you to change the language the words are displayed in.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <guimenu>Look</guimenu> menu proposes two themes: the <guimenuitem>Sea Theme</guimenuitem> and the <guimenuitem>Desert Theme</guimenuitem>. The background and the font colors changes for each theme.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <guimenuitem>Settings</guimenuitem> menu allows you to configure
|
||||
&khangman; easily. First, <guimenuitem>Toolbars</guimenuitem> and
|
||||
<guimenuitem>Show Statusbar</guimenuitem> give you the possibility to
|
||||
hide/show the toolbars and statusbar.
|
||||
</para>
|
||||
|
||||
<para>There are two toolbars: the main one which is the one on top
|
||||
with the buttons and combo boxes and the
|
||||
<guilabel>Special Characters</guilabel> toolbar which, when it is shown, is
|
||||
on the bottom. This toolbar has buttons with the special characters
|
||||
for each language: accented letters and other special characters. This
|
||||
allows users to easily play in another language without having to configure
|
||||
a new keyboard layout. You click on a special letter and it is
|
||||
displayed as the letter to try. Pressing &Enter; will make the program
|
||||
see if the letter is present in the word or not. The toolbar can be
|
||||
hidden if you don't want it. This is saved in the configuration file
|
||||
so if the toolbar is hidden, it will be hidden next time you run
|
||||
&khangman;.
|
||||
</para>
|
||||
<tip>
|
||||
<para>
|
||||
It is of course possible to move the toolbars around. Put the mouse
|
||||
cursor on the small handle on the left of the toolbar, press the &LMB;
|
||||
and drag the toolbar to position it on the screen where you want
|
||||
it. If you point the mouse on one of the toolbars and press the right
|
||||
mouse button, a context menu appears to let you choose different
|
||||
options for the toolbar.
|
||||
</para>
|
||||
</tip>
|
||||
<para>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem> is a standard &kde; setting dialog that allows you to
|
||||
choose different shortcut keys for different actions. For example,
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo> is the
|
||||
standard shortcut for <guimenuitem>Quit</guimenuitem>.</para>
|
||||
<para><guimenuitem>Configure Toolbars...</guimenuitem> is also a
|
||||
standard &kde; menu item that allows you to add or suppress items from
|
||||
the toolbar.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&khangman; Desert theme</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="khangman2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&khangman; Desert theme</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para> Here you have &khangman; with the Desert theme, Catalan language and level Easy. The
|
||||
<interface>Characters</interface> toolbar is shown here.</para>
|
||||
|
||||
<para>The level is chosen with a combo box in the toolbar or via the <guimenu>Level</guimenu> menu in the menubar. The available levels are <guimenuitem>Easy</guimenuitem>, <guimenuitem>Medium</guimenuitem>, <guimenuitem>Animals</guimenuitem> and <guimenuitem>Hard</guimenuitem>. Easy is related to common objects a child aged six
|
||||
or seven knows. Medium regards nouns a bit more challenging, hard is
|
||||
quite difficult and animals is only animals nouns. </para>
|
||||
|
||||
<para> All words are nouns. No verbs, no adjectives. The chosen level
|
||||
is then displayed on the statusbar.</para>
|
||||
<para>Only letters are allowed to be typed in the text box.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="settings">
|
||||
<title>Available Settings</title>
|
||||
<para>
|
||||
A toolbar is provided for quick access to some settings. You can click on a button to have a new game (i.e. a new word), or to quit the game. The level and the theme are easily changed via 2 combo boxes on the toolbar.
|
||||
</para>
|
||||
<para>
|
||||
In <guimenu>Settings</guimenu>, <guimenu>Configure &khangman;...</guimenu> you will find tree pages. The first one is for <guilabel>General</guilabel> settings.
|
||||
</para>
|
||||
|
||||
<sect2 id="general-settings">
|
||||
<title>General Settings</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&khangman; General settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&khangman; General settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para><guilabel>Require more guesses for duplicate letters</guilabel>: this is unchecked as default. When unchecked, if you try the letter "a" and the word has several as, they will be all displayed. For example if the word is "potato" and you try "o", both os will be diaplayed. If you check this option however, only the first "o" will be displayed and you will have to try it one more time to display the second "o" in "potato". This increases the difficulty.
|
||||
</para>
|
||||
|
||||
<para><guilabel>Do not display the 'Congratulations! You won!' dialog</guilabel>: the default is unchecked, that means that when you win a game, a message box will be displayed to tell you that you won and ask you if you want to play again. If you check this option, this dialog is not displayed anymore, instead a new game starts directly after 3 seconds.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In the Sounds section, if you check <guilabel>Enable sounds</guilabel> then a sound will be played on new game and another sound will be played when you win a game.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="languages-settings">
|
||||
<title>Languages Settings</title>
|
||||
<para>The <guilabel>Languages</guilabel> Settings tab allows you to set some settings specific to some languages. If the settings are not available for the language you are playing in then those settings will be grayed and disabled so you cannot choose them.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&khangman; Languages Settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&khangman; Languages Settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Some languages also have hints to help you guess the word. The hint is shown by a right-click and gives a short definition of the word to guess. If this setting is enabled and if you check the option <guilabel>Show hints</guilabel>, you can &RMB; click anywhere on the game and get a hint shown for four seconds. This hint should help you to guess the word more easily.
|
||||
</para>
|
||||
|
||||
<para><guilabel>Type accented letters</guilabel> is available for Brazilian Portuguese, Catalan, Portuguese and Spanish in &khangman;'s configuration dialog. If you check <guilabel>Type accented letters</guilabel> then you will have to type all accented vowels (like ã). If this remains unchecked, when you type any vowel, all accented vowels will be displayed as well.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="timers-settings">
|
||||
<title>Timers Settings</title>
|
||||
<para>The <guilabel>Timers</guilabel> Settings tab allows you to <guilabel>Set the time for displaying the hint</guilabel> and to <guilabel>Set the time for Already Guessed Letter</guilabel> tooltip.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&khangman; Timers Settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings3.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&khangman; Timers Settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
<guilabel>Set the time for displaying the hint:</guilabel> allows you to set a greater time for showing the hint label. It is necessary to increase the time for younger children for example as they read more slowly than adults.
|
||||
</para>
|
||||
|
||||
<para><guilabel>Set the time for displaying the Already Guessed Letter</guilabel> allows you to increase or decrease the time for displaying the Already Guessed Letter tooltip. This tooltip is a label which appears when you tried a letter that was already tried. Some people will want not to see it for long while children will need time to understand it and thus will need to set the display for a longer duration.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="khangman-mainwindow">
|
||||
<title>Menus and Shortcut Keys</title>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Game</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Game</guimenu>
|
||||
<guimenuitem>New</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>New</action> game (&ie; new word)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>G</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Game</guimenu>
|
||||
<guimenuitem>Get Words in New Language...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Display</action> the KNewStuff dialog which lists all the data available in the different languages. </para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Game</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quits</action> &khangman;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Level</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Animals</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the list of animals words to guess</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Easy</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the list of easy words to guess</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Medium</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the list of medium difficulty words to guess</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Hard</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the list of difficult words to guess</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Language</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Language</guimenu>
|
||||
<guimenuitem>English</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the English language for the words to guess.</para>
|
||||
<para>All other installed languages are displayed as items in this menu as well.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Look</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Look</guimenu>
|
||||
<guimenuitem>Sea Theme</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the Sea background picture and associated font colors</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Look</guimenu>
|
||||
<guimenuitem>Desert Theme</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the Desert background picture and associated font colors</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Toolbars</guisubmenu>
|
||||
<guimenuitem>Main (&khangman;)</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the Main Toolbar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Toolbars</guisubmenu>
|
||||
<guimenuitem>Special Characters (&khangman;)</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the Characters Toolbar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show Statusbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the statusbar</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Open</action> standard &kde; setting dialog that allows you to
|
||||
choose different shortcut keys for different actions.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> the items you want to put in the toolbar
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &khangman;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Display</action> the &khangman; settings dialog
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
&help.menu.documentation;
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="developers">
|
||||
<title>Developer's Guide to &khangman;</title>
|
||||
|
||||
<sect1 id="changing-words">
|
||||
<title>How to add words in a new language for the game</title>
|
||||
|
||||
<para>Thanks to Stefan Asserhäll, it is very easy to add a new language
|
||||
directly to the game. The procedure described here can also be
|
||||
found in the <filename class="directory">khangman</filename> source folder
|
||||
in the file <filename>README.languages</filename>. Please follow the procedure and then send me the files tarred and gzipped to annemarie.mahfouf@free.fr.
|
||||
</para>
|
||||
<para>
|
||||
The twenty four available languages so far by code are: bg ca cs da de en es fr fi ga hu it nb nl nn pt pt_BR ru sl sr sr@Ltn sv tg and tr. If your language code is not among those, you can proceed further.
|
||||
</para>
|
||||
<para>Most of this data should be completed to include <emphasis>hints</emphasis>, please see below. Complete data: bg de fr en it only have hints so the other above languages must be updated as soon as possible.
|
||||
</para>
|
||||
<para>Be sure you are working with the latest svn trunk sources of &khangman; by
|
||||
issuing a
|
||||
<screen><userinput><command>
|
||||
svn up khangman
|
||||
</command></userinput></screen>
|
||||
in the kdeedu module. Then
|
||||
<screen><userinput><command>
|
||||
cd kdeedu/khangman
|
||||
</command></userinput></screen>
|
||||
</para>
|
||||
<para>The words are stored in 4 separate files, one for each level. The files are in
|
||||
<filename class="directory">/khangman/data/en</filename>. The file
|
||||
<filename>easy.txt</filename> is for level easy, the file
|
||||
<filename>medium.txt</filename> is for level medium, the file
|
||||
<filename>animals.txt</filename> is for level animals and the file
|
||||
<filename>hard.txt</filename> is for level hard.</para>
|
||||
<para>English is the default and thus the only language to be shipped with &khangman;. All other languages data are put in the correct kde-l10n.
|
||||
</para>
|
||||
<procedure>
|
||||
<step><para>Enter the following commands in a &konsole; to create the folder
|
||||
and files for the new language:</para>
|
||||
<!-- Do not wrap or indent the next line, it's white space sensitive -->
|
||||
<screen><userinput><command>./add_language <replaceable>language_code</replaceable></command></userinput></screen>
|
||||
<para>Here you must replace <replaceable>language_code</replaceable>
|
||||
with your language code.</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>The files now use the kvtml format. The tag <sgmltag class="starttag">o</sgmltag> is for the word and the tag <sgmltag class="starttag">t</sgmltag> is for the hint. Try to match the hint with the level of difficulty. The level 'Easy' will require an easy hint but the level 'Hard' will require the definition in the dictionary. Try not to use words of the same family in the hint, that would give the word away too easily! </para>
|
||||
<para>An example of a kvtml file is as follow:</para>
|
||||
<programlisting><markup>
|
||||
<?xml version="1.0"?>
|
||||
<!DOCTYPE kvtml SYSTEM "kvoctrain.dtd">
|
||||
<kvtml>
|
||||
<e>
|
||||
<o>cane</o>
|
||||
<t>è il tuo animale domestico preferito</t>
|
||||
</e>
|
||||
...
|
||||
...
|
||||
</kvtml>
|
||||
</markup></programlisting>
|
||||
</step>
|
||||
<step>
|
||||
<para>Edit all indicated text files in the new folder with a text editor,
|
||||
and replace each word inside the <sgmltag class="starttag">o</sgmltag> tag with a translated word and each hint inside a <sgmltag class="starttag">t</sgmltag> with a translated hint. It is not really important
|
||||
that the exact meaning is preserved, but try to keep the length and
|
||||
level of difficulty roughly the same.
|
||||
You can include words with white space or - in them, in that case the white space or the -
|
||||
will be shown instead of the _.
|
||||
Please contact &Anne-Marie.Mahfouf; <email>annemarie.mahfouf@free.fr</email> if there is anything special related to your language so I can adapt the code to it (especially the special and accented characters).</para>
|
||||
|
||||
<para>You can just translate the words but you can also adapt them
|
||||
following the level and add new words if you want. For example,
|
||||
<quote>table</quote> is in level easy in English but in your language,
|
||||
it can be level medium. Feel free to adapt the files to your language
|
||||
needs. The number of words in a file is not important, you can add
|
||||
some if you want.</para>
|
||||
|
||||
<para>Remember that all words are nouns.</para>
|
||||
|
||||
<para> Note that you must use <emphasis role="bold">UTF-8 encoding</emphasis> when editing the
|
||||
files. If your editor cannot do this, try using &kwrite; or &kate;. When
|
||||
opening a file in &kwrite; or &kate; you can select utf8 encoding with
|
||||
the combo box at the top of the file open dialog.</para>
|
||||
|
||||
<para>Please keep the actual English filenames in your
|
||||
<replaceable>language_code</replaceable> dir.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Enter the following command to install the new data files:</para>
|
||||
<screen><userinput><command>make</command></userinput>
|
||||
<userinput><command>make install</command></userinput></screen>
|
||||
|
||||
<para>You may have to become <systemitem
|
||||
class="username">root</systemitem> to run <command>make
|
||||
install</command>, depending on your installation.</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>Run the game and check that your language has been added:</para>
|
||||
<screen><userinput><command>khangman</command></userinput></screen>
|
||||
</step>
|
||||
<step><para>Instead of committing your files, please sent them to
|
||||
&Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail; tarred and gzipped. As there are
|
||||
now twenty three languages, a wizard (KNewStuff) is now included in &khangman;
|
||||
to easily download and install new languages that are placed on the website.
|
||||
This is done to reduce the size of the kdeedu module and it will also be done in
|
||||
&klettres;, &kstars; and maybe &ktouch;.
|
||||
Please contact Anne-Marie by email if you need further information.</para>
|
||||
<para>When you send me the files, please don't forget to mention any <emphasis role="bold">special characters</emphasis> used in your language (put them in a text file, one per line and add this file in the tarball) and please mention any other specificity.</para>
|
||||
<para><emphasis>Please never commit files in a BRANCH as it might break the game.</emphasis></para>
|
||||
</step>
|
||||
</procedure>
|
||||
<para>Many thanks for your contribution!</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="internal">
|
||||
<title>What is stored by &khangman; and where</title>
|
||||
<para>
|
||||
When you get a new language via <menuchoice><guimenu>Game</guimenu> <guimenuitem>Get Words in New Language...</guimenuitem></menuchoice>, the new language data is stored in <filename class="directory">$~/.kde/share/apps/khangman/data</filename> in the language code folder. The available language dir names are also stored in the &khangman; config file in <filename>~/.kde/share/config/khangmanrc</filename>.
|
||||
</para>
|
||||
<para>
|
||||
The provider name (i.e. the address of the website where to download the new languages) is stored in <filename>$KDEDIR/share/apps/khangman/khangmanrc</filename>.
|
||||
</para>
|
||||
<para>
|
||||
The English language (default) and the user language from his i18n package(s) (if available) are stored in <filename class="directory">$KDEDIR/share/apps/khangman</filename>.
|
||||
</para>
|
||||
<para>
|
||||
In the configuration file, stored for each user in his <filename>~/.kde/share/config/khangmanrc</filename> are saved all the game settings such as the background, last level played, ... plus the files that were downloaded from the KNewStuff dialog.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="planned-features">
|
||||
<title>Planned Features for &khangman;</title>
|
||||
<para>
|
||||
A planned feature is of course to have more language data and also hints in every language. You can help for this in your own language if it is not done yet. Please contact me if you want to help with this, it's just a matter of translating the English words to your language (see <link linkend="changing-words">How to add words in a new language for the game</link>).
|
||||
</para>
|
||||
<para>
|
||||
What can also be done is to use other kvtml files like the ones that are on the
|
||||
&kde;-Edu website to play &khangman;. For example, imagine you can play the
|
||||
capitals of the world, the hint will tell you the country and you have to guess
|
||||
the capital. Or learn words in another language, the hint is the word in your
|
||||
language, the word to guess is the translation in the new language.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<qandaset id="faqlist">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I have an error message telling me the pictures cannot be found.</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>The game installs by default in <filename
|
||||
class="directory">/usr/local/kde</filename> so add <filename
|
||||
class="directory">/usr/local/kde/bin</filename> to your path and set
|
||||
the <envar>KDEDIR</envar> variable to <filename
|
||||
class="directory">/usr/local/kde</filename> before running the
|
||||
game. An easy way is to configure &khangman; with the option
|
||||
<option>--prefix</option>=$<envar>KDEDIR</envar> where
|
||||
$<envar>KDEDIR</envar> is where the rest of &kde; is installed. This
|
||||
could vary widely, depending on the distribution and operating system
|
||||
you.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>&khangman; does not start correctly after I upgraded from an earlier version to the &kde; 3.5 version</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
There might be a problem due to the change of the configuration file. Please remove the <filename>khangmanrc</filename> file in your <filename class="directory">$HOME/.kde/share/config</filename> folder.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&khangman;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2001-2006 &Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail;
|
||||
</para>
|
||||
<para>
|
||||
Contributors:
|
||||
<itemizedlist>
|
||||
<listitem><para>Hangman graphics: Renaud Blanchard
|
||||
<email>kisukuma@chez.com</email></para> </listitem>
|
||||
<listitem><para>Sounds: Ludovic Grossard
|
||||
<email>ludovic.grossard@libertysurf.fr</email></para> </listitem>
|
||||
<listitem><para>Blue theme, icons and code: &Primoz.Anzur;
|
||||
&Primoz.Anzur.mail;</para> </listitem>
|
||||
<listitem><para>Swedish data files, coding help, transparent pictures and i18n fixes: Stefan Asserhäll
|
||||
<email>stefan.asserhall@telia.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Nature theme: Joe Bolin
|
||||
<email>jbolin@users.sourceforge.net</email></para> </listitem>
|
||||
<listitem><para>Softer Hangman Pictures: Matt Howe
|
||||
<email>mdhowe@bigfoot.com</email></para> </listitem>
|
||||
<listitem><para>Spanish data files: eXParTaKus
|
||||
<email>expartakus@expartakus.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Spanish data hints: Rafael Beccar
|
||||
<email>rafael.beccar@kdemail.net
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Danish data files: Erik Kjaer Pedersen
|
||||
<email>erik@mpim-bonn.mpg.de
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Finnish data files: Niko Lewman
|
||||
<email>niko.lewman@edu.hel.fi
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Brazilian Portuguese data files: João Sebastião de Oliveira Bueno
|
||||
<email>gwidion@mpc.com.br
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Catalan data files: Antoni Bella
|
||||
<email>bella5@teleline.es
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Italian data files: Giovanni Venturi
|
||||
<email>jumpyj@tiscali.it
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Dutch data files: Rinse
|
||||
<email>rinse@kde.nl
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Portuguese data files: Pedro Morais
|
||||
<email>morais@kde.org
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Serbian (Cyrillic and Latin) data files: Chusslove Illich
|
||||
<email>chaslav@sezampro.yu
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Slovenian data files: Jure Repinc
|
||||
<email>jlp@holodeck1.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Czech data files: Lukáš Tinkl
|
||||
<email>lukas@kde.org
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Tajik data files: Roger Kovacs
|
||||
<email>rkovacs@khujand.org
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Norwegian (Bokmål) data files: Torger Åge Sinnes
|
||||
<email>torg-a-s@online.no
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Hungarian data files: Tamas Szanto
|
||||
<email>tszanto@mol.hu
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Norwegian (Nynorsk) data files: Gaute Hvoslef Kvalnes
|
||||
<email>gaute@verdsveven.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Turkish data files: Mehmet Özel
|
||||
<email>mehmet_ozel2003@hotmail.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Bulgarian data files: Radostin Radnev
|
||||
<email>radnev@yahoo.com
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Irish (Gaelic) data files: Kevin Patrick Scannell
|
||||
<email>scannell@slu.edu
|
||||
</email></para> </listitem>
|
||||
<listitem><para>Coding help: &Robert.Gogolok;
|
||||
&Robert.Gogolok.mail;</para> </listitem>
|
||||
<listitem><para>Coding help: Benjamin Meyer
|
||||
<email>ben@meyerhome.net</email></para> </listitem>
|
||||
<listitem><para>Code fixes: Lubos Lunàk
|
||||
<email>l.lunak@kde.org</email></para> </listitem>
|
||||
<listitem><para>Code fixes: Albert Astals Cid
|
||||
<email>tsdgeos@terra.es</email></para> </listitem>
|
||||
<listitem><para>Usability study: Celeste Paul
|
||||
<email>seele@obso1337.org</email></para> </listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2001-2005 &Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail;
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-khangman">
|
||||
<title>How to obtain &khangman;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 80 KiB |
|
After Width: | Height: | Size: 226 KiB |
@ -0,0 +1,63 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>khangman</command></refentrytitle>
|
||||
<manvolnum>6</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>khangman</command></refname>
|
||||
<refpurpose>The classical hangman game for KDE</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>khangman</command>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&khangman; is a game based on the well known hangman game. It is
|
||||
aimed for children 6 and above. It has four levels of difficulty: Animals
|
||||
(animals words), Easy, Medium and Hard.</para><para>A word is picked at
|
||||
random and the letters are hidden. You must guess the word by trying one
|
||||
letter after another. Each time you guess a wrong letter, part of a picture
|
||||
of a hangman is drawn. You must guess the word before getting hanged! You
|
||||
have 10 tries.</para><para>This application is part of the &kde; Edutainment
|
||||
module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/khangman">help:/khangman</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/khangman</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at the <ulink url="http://edu.kde.org/khangman/">&kde; Edutainment web site</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&khangman; was written by <personname><firstname>Primoz</firstname><surname>Anzur</surname></personname> and &Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail;</para>
|
||||
<para>This manual page based on the one prepared by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> for the Debian project.</para>
|
||||
|
||||
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 15 KiB |
@ -0,0 +1,5 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 18 KiB |
@ -0,0 +1,998 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kseg "<application>KSeg</application>">
|
||||
<!ENTITY cabri "<application>Cabri</application>">
|
||||
<!ENTITY drgeo "<application>Dr.Geo</application>">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY kappname "&kig;">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
<!-- change language only here -->
|
||||
]
|
||||
>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kig; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Dominique</firstname> <surname>Devriese</surname>
|
||||
<affiliation>
|
||||
<address><email>devriese@kde.org</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
|
||||
<copyright>
|
||||
<year>2002</year><year>2003</year><year>2004</year> <holder>Dominique
|
||||
Devriese</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-08-20</date> <releaseinfo>0.10.5</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kig; is a &kde; application for Interactive Geometry.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>KDE-Edu</keyword>
|
||||
<keyword>Kig</keyword>
|
||||
<keyword>Interactive Geometry</keyword>
|
||||
<keyword>KGeo</keyword>
|
||||
<keyword>Cabri</keyword>
|
||||
<keyword>Dr.Geo</keyword>
|
||||
<keyword>KSeg</keyword>
|
||||
</keywordset>
|
||||
</bookinfo>
|
||||
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&kig; is an application for Interactive Geometry. It's intended
|
||||
to serve two purposes:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para> Allow students to interactively explore
|
||||
mathematical figures and concepts using the computer.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para> Serve as a <acronym>WYSIWYG</acronym> tool for
|
||||
drawing mathematical figures and including them in other
|
||||
documents.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>
|
||||
You can report problems in &kig; using the internal bug
|
||||
reporting tool
|
||||
(<menuchoice><guimenu>Help</guimenu><guimenuitem>Report
|
||||
Bug...</guimenuitem></menuchoice>), or just contact me at
|
||||
<email>toscano.pino@tiscali.it</email>.
|
||||
</para>
|
||||
<para>
|
||||
Since &kig; supports macros and the construction of locuses, it allows for
|
||||
some
|
||||
rather advanced macros to be defined. If you have created an
|
||||
interesting macro, which you think might be useful for other
|
||||
people, please mail it to me at
|
||||
<email>toscano.pino@tiscali.it</email>, so I can include it in the
|
||||
distribution (if you do this, it will be licensed under the
|
||||
terms of &kig;'s license, the <ulink
|
||||
url="http://www.gnu.org/licenses/licenses.html#GPL">GPL</ulink>,
|
||||
so that other people can freely use and adapt it).
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="using-kig-basic">
|
||||
<title>Basic usage</title>
|
||||
<section id="constructing-objects">
|
||||
<title>Constructing Objects</title>
|
||||
<section id="constructing-points">
|
||||
<title>Constructing points</title>
|
||||
<para>
|
||||
You can construct points in several ways:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Select <menuchoice><guimenu>Objects</guimenu>
|
||||
<guisubmenu>Points</guisubmenu>
|
||||
<guimenuitem>Point</guimenuitem></menuchoice> from the
|
||||
menubar or
|
||||
press the appropriate button in the toolbar. You can
|
||||
then construct a point by clicking at the desired
|
||||
position in the window.</para> <note><para>Actually, this
|
||||
works the same way for constructing other objects as
|
||||
well: click on the desired menubar entry or toolbar
|
||||
button and select the necessary items to construct
|
||||
the object.</para></note>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Since you often need to construct points, simply
|
||||
clicking somewhere in the screen with the &MMB; will
|
||||
construct a point for you, without going to a menu or
|
||||
button.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
You can construct points while you are building other
|
||||
objects in the background, optionally selecting them
|
||||
for the object you are building. For more on this,
|
||||
see <xref linkend="constructing-other-objects" />.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>A point has been constructed</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="constructed_a_point.png"
|
||||
format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>A point has been constructed</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<section id="constructing-other-objects">
|
||||
<title>Constructing Other Objects</title>
|
||||
<para>
|
||||
Constructing objects other than points is usually done by
|
||||
selecting the appropriate entry in the
|
||||
<guimenu>Objects</guimenu> menu, or by clicking on one of
|
||||
the toolbar buttons.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Constructing a circle</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="constructing_a_circle.png"
|
||||
format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Constructing a circle</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
This will start the construction of the chosen object type.
|
||||
All of these types require arguments. For example, if you
|
||||
selected to construct a circle by center and point, you will need to
|
||||
give two points: one for the center, and one for the point on
|
||||
the circle.
|
||||
</para>
|
||||
<para>
|
||||
These arguments are objects too, which can also be selected, simply by
|
||||
clicking on them. When you move the cursor over an argument you want to use to
|
||||
construct an object, a preliminary image will be shown of the object, so you will
|
||||
know what it will look like. For objects that require points as arguments, you
|
||||
can place a new point at the
|
||||
current cursor position and select it by clicking the &LMB;.
|
||||
</para>
|
||||
<para>
|
||||
You can always cancel the construction of the new object by
|
||||
pressing the &Esc; button or by clicking
|
||||
on the <guiicon>Stop</guiicon> button (red octagon with an
|
||||
<quote>X</quote>) on the toolbar.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Constructing a circle.</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="constructing_a_circle_2.png"
|
||||
format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Constructing a circle</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section id="selecting-objects">
|
||||
<title>Selecting Objects</title>
|
||||
<para>
|
||||
Selecting objects can be done in two ways:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Simply clicking on an object causes that object to be selected, clearing the
|
||||
current selection. If you
|
||||
want to select multiple objects simultaneously, hold down the &Ctrl; key while
|
||||
clicking on an object.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
By clicking and dragging on an empty spot on the screen,
|
||||
you can select all objects within the rectangle that is
|
||||
created. This action will clear the current selection. As
|
||||
in the previous case, holding down the &Ctrl; key allows you
|
||||
to keep the current selection.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>
|
||||
When you have more than one object under the mouse, you can easily
|
||||
choose which object select or add to the current selection. Click
|
||||
with the &LMB;, while holding the &Shift; key, to have a popup with
|
||||
all the objects under the mouse. Then, you can select the object
|
||||
you need. As said before, the behaviour of the &Ctrl; key will
|
||||
affect the selection.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Selecting objects</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="selecting_objects.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Selecting objects</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<section id="moving-objects">
|
||||
<title>Moving Objects</title>
|
||||
<para>
|
||||
To move objects, you must first <link
|
||||
linkend="selecting-objects">select</link> them.
|
||||
</para>
|
||||
<para>
|
||||
When the objects you want to move are selected, you can start
|
||||
moving them by &LMB; clicking and dragging any one of them. When you are done,
|
||||
simply release the &LMB;.
|
||||
</para>
|
||||
<note><para>For some types of objects (especially when defined by
|
||||
complicated locuses), moving them can be slow on old hardware. This
|
||||
is unfortunate, but inevitable, given the calculations involved.
|
||||
</para></note> <note><para>If you &RMB; click one of the selected objects, and
|
||||
choose
|
||||
<guimenuitem>Move</guimenuitem>, moving the mouse will move the object. When the
|
||||
object is moved to the desired position, another &LMB; click will stop the
|
||||
moving of the object.</para></note>
|
||||
</section>
|
||||
<section id="deleting-objects">
|
||||
<title>Deleting objects</title>
|
||||
<para>
|
||||
Deleting objects is done by first <link
|
||||
linkend="selecting-objects">selecting</link> them, and next doing either of
|
||||
these:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Press the <keycap>Delete</keycap> key.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Press the <guiicon>delete</guiicon> button on the toolbar.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<mousebutton>Right</mousebutton>-click on one of the
|
||||
objects, and select
|
||||
<guimenuitem>Delete</guimenuitem>
|
||||
in the <link linkend="objects-context-menus">context
|
||||
menu</link> that appears.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="showing-hiding-objects">
|
||||
<title>Showing and hiding objects</title>
|
||||
<para>
|
||||
In &kig;, objects can be hidden. This is done by selecting
|
||||
the objects, &RMB; clicking one of
|
||||
them, and selecting
|
||||
<guimenuitem>Hide</guimenuitem> in
|
||||
the <link linkend="objects-context-menus">context menu</link>
|
||||
that appears.
|
||||
</para>
|
||||
<para>
|
||||
To unhide the objects, use the
|
||||
<menuchoice><guimenu>Edit</guimenu><guimenuitem>Unhide
|
||||
all</guimenuitem></menuchoice>. This will unhide all
|
||||
currently hidden objects.
|
||||
</para>
|
||||
|
||||
<section id="night-vision">
|
||||
<title>Night Vision</title>
|
||||
<para>
|
||||
Night Vision is a particular way of working with hidden
|
||||
objects. When you have to move or change something in one or
|
||||
more object but without unhiding all the hidden objects you
|
||||
have, then the night vision mode will be of benefit to you.
|
||||
</para>
|
||||
<para>
|
||||
Basically, it allows you to see the hidden objects as if they
|
||||
were visible, so that you can manipulate them as you would normally.
|
||||
In Night Vision mode, the hidden objects will be visible with
|
||||
a grey colour.
|
||||
</para>
|
||||
<para>
|
||||
To toggle the night vision mode, use
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Wear
|
||||
Infrared Glasses</guimenuitem></menuchoice>.
|
||||
</para>
|
||||
</section>
|
||||
</section>
|
||||
|
||||
<section id="undo-redo">
|
||||
<title>Undo/Redo</title>
|
||||
<para>
|
||||
In &kig;, you can undo almost any change you make in the
|
||||
document. Just use the
|
||||
<guiicon>undo</guiicon>/<guiicon>redo</guiicon> buttons on the
|
||||
toolbar, or the appropriate shortcuts.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="full-screen-mode">
|
||||
<title>Full Screen Mode</title>
|
||||
<para>
|
||||
&kig; also has a Full Screen mode. To use it, click the
|
||||
appropriate button on the toolbar, or select
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Full
|
||||
Screen Mode</guimenuitem></menuchoice>.
|
||||
</para>
|
||||
<para>
|
||||
To leave Full Screen mode,
|
||||
&RMB; click the screen at a place
|
||||
where there is no object present, and select
|
||||
<guimenuitem>Exit Full Screen Mode</guimenuitem>, or press the
|
||||
&Esc; key.
|
||||
</para>
|
||||
</section>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="kig-object-types">
|
||||
<title>&kig; Object Types</title>
|
||||
<para>
|
||||
&kig; supports a rather large number of object types. Please
|
||||
note that not all of the available object types are shown in the
|
||||
toolbars: there are some objects that you can only
|
||||
construct via the <guimenu>Objects</guimenu> menu in the menu
|
||||
bar. Of course, as with all &kde; applications, the contents of the toolbars are
|
||||
configurable. Try out the
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Toolbars...</guimenuitem></menuchoice> option if you want to do this.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="using-advanced">
|
||||
<title>Advanced Usage</title>
|
||||
<section id="objects-context-menus">
|
||||
<title>Context Menus</title>
|
||||
<para>
|
||||
&kig; has context menus for its objects. Try
|
||||
&RMB; clicking on an object in order to see
|
||||
a context menu appear. There are many options: for
|
||||
constructing other objects, setting colours, and even hiding,
|
||||
moving or deleting objects. Some objects have options of
|
||||
their own (⪚ you can redefine certain points to be
|
||||
constrained to a line if they previously weren't, &etc;).
|
||||
These options should be very straightforward to understand.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="document-context-menus">
|
||||
<title>Document context menus</title>
|
||||
<para>
|
||||
<mousebutton>Right</mousebutton>-clicking on the document (&ie; not on an
|
||||
object) will
|
||||
present a popup that you can use to start constructing a new object, change the
|
||||
coordinate system used, show hidden
|
||||
objects, and even zoom in and zoom out of the document.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="defining-macros">
|
||||
<title>Defining Macros</title>
|
||||
<para>
|
||||
One of the more advanced features in &kig; is its support for
|
||||
macros. This allows you to define new types of objects from
|
||||
other ones which are defined already.
|
||||
</para>
|
||||
<para>
|
||||
For example: Suppose you want to make a macro for constructing
|
||||
a circle from three points on it. You would input three points,
|
||||
then construct some perpendiculars and midpoints
|
||||
until you find the center. Now you can use the existing
|
||||
<quote>Construct a circle by center and point</quote> command
|
||||
(using one of the three points as the point for this command). The
|
||||
following image should make this a bit more clear:
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Test running macros</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="test_run_macro.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Test running macros</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Next comes defining the macro. Select <guimenuitem>New
|
||||
macro</guimenuitem> from the <guimenu>Type</guimenu> menu, or
|
||||
click on the button on the toolbar. A wizard will appear and
|
||||
ask you to select the given objects. In our example, these
|
||||
are the three points. Select the three points (click on them
|
||||
to select, click again to unselect) and click the
|
||||
<guibutton>Next</guibutton> button to continue. Finally,
|
||||
select the last objects (only the circle in our example).
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The macro wizard</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="macro_wizard.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The macro wizard</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para> After the previous steps are completed, click the
|
||||
<guibutton>Next</guibutton> button to continue. Enter a name
|
||||
and optionally a description for your new type, and click the
|
||||
<guibutton>Finish</guibutton> button. Your macro type is now
|
||||
finished.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To use the new macro type, click its button on the toolbar or
|
||||
use the <guimenu>Objects</guimenu> menu. Constructing a macro
|
||||
object is just like constructing any other object.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Using your new type</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="macros_at_work.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Using your new type</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<section id="working-with-types">
|
||||
<title>Working with types</title>
|
||||
<para>
|
||||
As you saw in the previous chapter, &kig; allows you to create
|
||||
your own objects. &kig; also makes sure that once you have
|
||||
created an object, it is saved on exit and loaded on startup.
|
||||
You do not have to manually save or load macro definitions.
|
||||
However, &kig; does allow you to do more with the macros. If
|
||||
you select <menuchoice><guimenu>Types</guimenu><guimenuitem>Manage
|
||||
Types...</guimenuitem></menuchoice> from the menu, you will see
|
||||
a dialog where you can edit your types. It allows you to modify
|
||||
the existant types, delete types that are no longer used, export
|
||||
them to a file, or even load them from another file.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Edit Types Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="edit_types_dialog.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The Edit Types Dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<section id="text-labels">
|
||||
<title>Text labels</title>
|
||||
<para>
|
||||
&kig; allows you to add text labels to a construction. This
|
||||
is very useful for adding names, explanations or other text
|
||||
to constructions. &kig; can also display variable information
|
||||
about objects (also known as <quote>properties</quote>).
|
||||
</para>
|
||||
<para>
|
||||
To start constructing a text label, simply press the
|
||||
<guibutton>Text Label</guibutton> button in the &kig; toolbar or
|
||||
select <menuchoice><guimenu>Objects</guimenu><guisubmenu>Other
|
||||
</guisubmenu><guimenuitem>Text label</guimenuitem>
|
||||
</menuchoice> in the menubar.
|
||||
</para>
|
||||
<para>
|
||||
Next, you have to choose a location for the text label. You
|
||||
can either just select a random location on the screen, or
|
||||
choose to <quote>attach</quote> the label to an object.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Attaching a label to a circle...</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="text_label_attaching.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Attaching a label to a circle...</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
After you have selected where to put the label, the text label dialog appears.
|
||||
Here, you can type in
|
||||
the text that you want in the new label, and click
|
||||
<guibutton>Finish</guibutton>. You should now see the label in your document.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>The Text Label Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="text_label_wizard.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The Text Label Dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
The previous example was a simple one, and limited to just
|
||||
text. However, there is also support for showing variable
|
||||
information about objects in a label (⪚ you can construct a
|
||||
label with the text <quote>This segment is %1 units
|
||||
long.</quote> where <token>%1</token> would be dynamically
|
||||
replaced with the length of a specific segment).
|
||||
</para>
|
||||
<para>
|
||||
To do this, enter a text with a number of placeholders (
|
||||
<token>%1</token>, <token>%2</token> &etc;) in it.
|
||||
Then, press the <guibutton>Next</guibutton> button to
|
||||
continue. If you want to change the text or variables later,
|
||||
you can go back using the <guibutton>Back</guibutton> button.
|
||||
</para>
|
||||
<para>
|
||||
The wizard now shows the text you entered with all
|
||||
placeholders replaced by something like <guilabel>argument
|
||||
1</guilabel>. Selecting the property connected to a certain argument is
|
||||
done by first clicking on the argument in question. Then click
|
||||
on the object that you need and that has this property, and
|
||||
then select the property itself in the popup
|
||||
menu that appears. For instance, in the example above, you
|
||||
would click <guilabel>argument 1</guilabel>, click on the
|
||||
correct segment in the main &kig; window, and select the
|
||||
property <guilabel>Length</guilabel>. Afterwards, you can
|
||||
fill in the rest of the variable parts, or select another
|
||||
property for one of the variable parts if you wish to change
|
||||
it. When you are ready, click the
|
||||
<guibutton>Finish</guibutton> button to complete the
|
||||
construction of the text label.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Selecting a property for a variable
|
||||
part</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="text_label_wizard__select_property.png"
|
||||
format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Selecting a property for a variable part</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</section>
|
||||
|
||||
<section id="locuses">
|
||||
<title>Locuses</title>
|
||||
<para>
|
||||
&kig; supports the use of locuses. A locus is mathematically defined as
|
||||
the set of all points or lines that satisfy or are determined by specific
|
||||
conditions; as in <quote>the locus of points
|
||||
equidistant from a given point is a circle</quote>.
|
||||
Let's look at an example of how to use locuses in &kig;:
|
||||
</para>
|
||||
<para>
|
||||
Consider the following geometrical construction: We draw a
|
||||
circle, and a point that can move only along its circumference
|
||||
(construct this point by positioning the cursor on a circle, and clicking
|
||||
the &MMB;. If you then try to move the resulting point,
|
||||
you'll see that you cannot move it off the circle). Then, we
|
||||
draw a segment from that point to the center of the circle,
|
||||
and the midpoint of that segment.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>A simple construction using a locus</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata
|
||||
fileref="simple_locus_construction.png"
|
||||
format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>A simple construction using a locus</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
Now if you move the point that is constrained to the circle,
|
||||
you'll see that the second point moves along with it. If you
|
||||
were to hold a pen at the second point, and move the
|
||||
first point around the entire circle, a new circle, half the
|
||||
size of the other would be drawn. The path that the second point
|
||||
travels while the first one moves around the circle is its locus.
|
||||
</para>
|
||||
<para>
|
||||
Actually constructing the locus of a point is very easy. Click
|
||||
the <guiicon>locus</guiicon> button in the toolbar, or select
|
||||
<menuchoice><guimenu>Objects</guimenu>
|
||||
<guisubmenu>Other</guisubmenu>
|
||||
<guimenuitem>Locus</guimenuitem>
|
||||
</menuchoice>
|
||||
from the menubar. Then select the constrained point as the
|
||||
moving point (the text <guilabel>Moving Point</guilabel> will
|
||||
appear as you move the mouse over it), and the other as the
|
||||
dependent point. The locus of the dependent point will then be drawn.
|
||||
</para>
|
||||
</section>
|
||||
</chapter>
|
||||
|
||||
<chapter id="scripting">
|
||||
<title>Scripting</title>
|
||||
<para>
|
||||
&kig; allows you to create custom types in the Python
|
||||
scripting language. This is a very advanced feature, and I know
|
||||
of only one other Interactive Geometry program that has a similar
|
||||
functionality (the <acronym>GNOME</acronym> program &drgeo;).
|
||||
</para>
|
||||
<para>
|
||||
Python Scripting in &kig; basically allows you to create your
|
||||
own objects from certain parent objects. For example, if you are a math
|
||||
teacher, and you have some fancy way
|
||||
of calculating an interesting point on a conic, then instead of
|
||||
messing with complex constructions and macros, you could just
|
||||
write down in Python code how the point is to be calculated and
|
||||
then &kig; will show it for you.
|
||||
</para>
|
||||
<para>
|
||||
Suppose you were not aware of the &kig; built-in type <quote>Mid Point</quote>,
|
||||
and you wanted to show the midpoint of two given points. You
|
||||
would then click on the <guibutton>Python Script</guibutton>
|
||||
button in the toolbar, or select
|
||||
<menuchoice><guimenu>Objects</guimenu><guisubmenu>Other</guisubmenu>
|
||||
<guimenuitem>Python Script</guimenuitem></menuchoice> from the
|
||||
menubar. You are then presented with a wizard that allows you
|
||||
to proceed.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>The Script Object Wizard</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="script_wizard.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The Script Object Wizard</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
The first thing you have to do is select the arguments for the
|
||||
script object. In our example, this means the two points of
|
||||
which we want to show the midpoint. Select them in the &kig;
|
||||
main window, and click <guibutton>Next</guibutton> to proceed.
|
||||
</para>
|
||||
<para>
|
||||
Now you are presented with a text edit box where you can enter
|
||||
the code for you script object. Template code and some comments
|
||||
are already in place. It is important to make sure that your
|
||||
code is valid Python code. People familiar with Python will
|
||||
notice that we are actually defining a Python function called
|
||||
<function>calc</function>. It is therefore necessary to adhere
|
||||
to the Python rules for defining functions. For example, every
|
||||
line of the function should start with a <keysym>Tab</keysym>.
|
||||
The first line not starting with a <keysym>tab</keysym> ends the
|
||||
definition of the function.
|
||||
</para>
|
||||
<para>
|
||||
The Python function that we want to define is called
|
||||
<function>calc</function>, and in our case it accepts two arguments.
|
||||
These are the objects you have selected as arguments in the
|
||||
previous screen. You need as many arguments as you have
|
||||
selected there. They are called <parameter>arg1</parameter> and
|
||||
<parameter>arg2</parameter>, but you can change their names to
|
||||
something more meaningful if you want.
|
||||
</para>
|
||||
<para>
|
||||
In the function, you can do all sorts of calculations that you
|
||||
deem necessary, using the two arguments if needed. You should
|
||||
return the object you want to define. In our case, this is a
|
||||
<classname>Point</classname> object. The two arguments are also
|
||||
<classname>Point</classname> objects, and we
|
||||
can use the <function>Point.coordinate()</function> function to
|
||||
define the coordinates of the two given points.
|
||||
</para>
|
||||
<para>
|
||||
The calculation necessary in our example is very simple, we
|
||||
simply add the two sets of coordinates, and divide the new set
|
||||
by two. We then construct a new point using the result.
|
||||
The Python code needed is:</para>
|
||||
|
||||
<programlisting>
|
||||
def calc( a, b ):
|
||||
m = ( a.coordinate() + b.coordinate() ) / 2;
|
||||
return Point( m )
|
||||
</programlisting>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Entering the code</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="script_wizard_entering_code.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Entering the code for the midpoint in the Script Object
|
||||
wizard.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
If you now click the <guibutton>Finish</guibutton> button,
|
||||
the new object will appear in the &kig; document. If you move
|
||||
one of the points, the newly created point will move along
|
||||
with it. Much more powerful objects can be built in this way:
|
||||
you are encouraged to try it out.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Constructed a Script Object</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="constructed_script_object.png" format="PNG" />
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>
|
||||
The newly constructed Script Object.
|
||||
</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
All objects in &kig; can be used in the Python code. As we have
|
||||
seen above, points are of the <classname>Point</classname> class, and you
|
||||
can use ⪚ the <function>Point.coordinate()</function> method. You can
|
||||
also return all kinds of objects, not just a <classname>Point</classname>.
|
||||
Many more classes and methods are available in the &kig; Python code,
|
||||
and a more complete reference is provided <ulink
|
||||
url="http://edu.kde.org/kig/manual/scripting-api/index.html">on
|
||||
the &kig; website</ulink>.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="kig-features">
|
||||
<title>&kig; Features</title>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; is an open source application. This means that you
|
||||
are free to use and modify it any way you like it.
|
||||
Distributing &kig; is subject to some restrictions,
|
||||
basically that everyone should have the same rights to use
|
||||
&kig;, including your modifications, as you and me.
|
||||
</para>
|
||||
<para>
|
||||
Free software programs are developed in a very open
|
||||
spirit, and its developers are usually very responsive to
|
||||
user feedback. Therefore, if you have any questions,
|
||||
complaints, or whatever about &kig;, please let the author
|
||||
know at <email>toscano.pino@tiscali.it</email>.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; is a KPart application, which means that you can
|
||||
embed it into other &kde; software. If you open a <literal
|
||||
role="extension">.kig</literal> file in &konqueror;, it
|
||||
can be opened directly in the &konqueror; screen without
|
||||
the need to start an external application.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Working with &kig; should be very straightforward.
|
||||
Constructing objects is easy and interactive, with
|
||||
preliminary results being shown, &etc;. Moving, selecting
|
||||
and building all work as one would expect them to. Undo
|
||||
support should also be very intuitive.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; supports macros to be defined in a straightforward
|
||||
manner. These objects are presented to the user like
|
||||
normal objects. They are saved on exit and loaded on
|
||||
startup, so that they aren't lost on exit. You can
|
||||
manage these objects in the <guilabel>Manage Types</guilabel>
|
||||
dialog (see <xref linkend="working-with-types" />). You can export
|
||||
them
|
||||
to files, import them from files, edit and delete them.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; saves its data in a clear &XML; format.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; supports the construction of locuses.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; allows you to export a &kig; file to some interesting
|
||||
formats, like images, <application>XFig</application> and
|
||||
<application>LaTeX</application> files, and <acronym>SVG</acronym>
|
||||
vectorial images. This is rather useful, because not all programs
|
||||
support the &kig; file format yet.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; has a very flexible transformation system.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
&kig; aims to be compatible with its competitors. This is
|
||||
why it supports the &kgeo; file format, the &kseg; file
|
||||
format and partially the &drgeo; and &cabri; formats; morover,
|
||||
support for other formats is planned.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs; &updating.documentation;
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kig;
|
||||
</para>
|
||||
<para>
|
||||
&kig; copyright 2002-2004 Dominique Devriese
|
||||
<email>devriese@kde.org</email>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2002-2004 Dominique
|
||||
Devriese <email>devriese@kde.org</email>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2004-2005 Pino Toscano
|
||||
<email>toscano.pino@tiscali.it</email>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Reviewed by &Philip.Rodrigues; &Philip.Rodrigues.mail;.
|
||||
</para>
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL; &underGPL;
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kig">
|
||||
<title>How to obtain &kig;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
&install.compile.documentation;
|
||||
</sect1>
|
||||
|
||||
</appendix>
|
||||
|
||||
<appendix id="contributing">
|
||||
<title>Contribute</title>
|
||||
<section id="kig-is-free">
|
||||
<title>Free Software</title>
|
||||
<para>
|
||||
&kig; is <ulink
|
||||
url="http://www.gnu.org/philosophy/philosophy.html#AboutFreeSoftware">
|
||||
Free Software</ulink>. This means that its source code is
|
||||
freely available on the Internet, and everyone can use it,
|
||||
read it, modify it, and distribute it. I work on it as a
|
||||
hobby project, and I have already learned a lot about
|
||||
programming, C++, &kde;/&Qt;, math, software collaboration and open
|
||||
source projects in the process.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="contribute-to-kig">
|
||||
<title>Contribute</title>
|
||||
<para>
|
||||
In this chapter I want to point out to you (the user) the
|
||||
rights that &kig;'s license gives you. As with all free
|
||||
software, you are allowed (and encouraged) to fix problems
|
||||
you encounter while using it, to add features you miss, to
|
||||
distribute your modified program, and to send these
|
||||
modifications to me at <email>toscano.pino@tiscali.it</email>, so
|
||||
that I can include them in the next version for others to
|
||||
enjoy. Please note I personally have no financial interest in this
|
||||
project whatsoever.
|
||||
</para>
|
||||
<para>
|
||||
If you are uncertain of your rights to use this software, or
|
||||
other people's right to use any modifications you make to this
|
||||
program &etc;, please read the license. You can find it in the
|
||||
<filename>COPYING</filename> file in the &kig; source tree or
|
||||
the <guilabel>license</guilabel> tab in the <guilabel>About
|
||||
Kig</guilabel> dialog.
|
||||
</para>
|
||||
</section>
|
||||
|
||||
<section id="howto-contribute">
|
||||
<title>How to contribute ?</title>
|
||||
<para>
|
||||
Any contributions are welcome. If you don't like the icons,
|
||||
or think that the manual needs updating, or if you have this really
|
||||
cool macro that you want to share with the world, do not
|
||||
hesitate to send it to me. Please note that your
|
||||
contributions will be distributed under the terms of the &GNU;
|
||||
<acronym>GPL</acronym>; you can find the terms of this license in the
|
||||
<filename>COPYING</filename> file in the &kig; source tree,
|
||||
and in the <link linkend="credits">Credits and
|
||||
Licenses</link> chapter in this manual.
|
||||
</para>
|
||||
</section>
|
||||
</appendix>
|
||||
|
||||
&documentation.index;
|
||||
</book>
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: xml
|
||||
End:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 42 KiB |
|
After Width: | Height: | Size: 81 KiB |
@ -0,0 +1,109 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname><email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>kig</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>kig</command></refname>
|
||||
<refpurpose>an interactive geometry program for &kde;</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>kig</command>
|
||||
<group choice="opt"><option>-c, --convert-to-native</option>
|
||||
<group choice="opt"><option>-o, --outfile <replaceable>filename</replaceable></option>
|
||||
</group>
|
||||
</group>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kig; is an application for interactive geometry. It is intended to
|
||||
serve two purposes:</para>
|
||||
<itemizedlist><listitem><para>To allow students to interactively explore
|
||||
mathematical figures and concepts using the computer;</para></listitem>
|
||||
<listitem><para>To serve as a WYSIWYG tool for drawing mathematical figures and
|
||||
including them in other documents.</para></listitem></itemizedlist>
|
||||
<para>With this program you can do geometry on a computer just like you
|
||||
would on a blackboard in a classroom. However the program allows you to
|
||||
move and change parts of a geometrical drawing so that you can see how other
|
||||
parts change as a result.</para>
|
||||
<para>&kig; supports loci and user-defined macros. It also imports and
|
||||
exports both to and from foreign file formats including
|
||||
<application>Cabri</application>, <application>Dr. Geo</application>,
|
||||
&kgeo;, <application>KSeg</application> and <application>XFig</application>.</para>
|
||||
<para>This application is part of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<para>App options, in a variablelist</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><option>-c, --convert-to-native</option></term>
|
||||
<listitem><para>Do not show a &GUI;. Instead convert the specified file to
|
||||
native &kig; format. The native &kig; file will be written to standard
|
||||
output unless <option>--outfile</option> is passed.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><option>-o, --outfile <replaceable>filename</replaceable></option></term>
|
||||
<listitem><para>Used with <option>--convert-to-native</option> to specify
|
||||
where to save the newly created &kig; file. Not specifying this option, or
|
||||
providing a filename of <filename>-</filename> will output the file to
|
||||
standard output.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kig">help:/kig</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kig</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at the <ulink
|
||||
url="http://edu.kde.org/kig/">&kde; Edutainment website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&kig; was written by
|
||||
<personname><firstname>Dominique</firstname><surname>Devriese</surname></personname>
|
||||
<email>devriese@kde.org</email>,
|
||||
<personname><firstname>Maurizio</firstname><surname>Paolini</surname></personname>
|
||||
<email>paolini@dmf.bs.unicatt.it</email>,
|
||||
<personname><firstname>Franco</firstname><surname>Pasquarelli</surname></personname>
|
||||
<email>pasqui@dmf.bs.unicatt.it</email>,
|
||||
<personname><firstname>Pino</firstname><surname>Toscano</surname></personname>
|
||||
<email>toscano.pino@tiscali.it</email>, and others.</para>
|
||||
<para>This man page based on the one prepared for Debian by
|
||||
<personname><firstname>Ben</firstname><surname>Burton</surname></personname>
|
||||
<email>bab@debian.org</email>.</para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 46 KiB |
|
After Width: | Height: | Size: 17 KiB |
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,7 @@
|
||||
# generate the Kig Python Scriptin APIdocs from the Kig source code
|
||||
|
||||
all-local: build-kig-python-scripting-apidocs
|
||||
build-kig-python-scripting-apidocs:
|
||||
# cat $(srcdir)/Doxyfile.scripting-api.in | sed -e 's#KIGVERSION#@KIGVERSION@#g' | sed -e 's#TOPSRCDIR#$(top_srcdir)#g' | sed -e 's#SRCDIR#$(srcdir)#g' > Doxyfile.scripting-api
|
||||
doxygen Doxyfile.scripting-api
|
||||
cp bottom1.png bottom2.png docheadergears.png grad.png headerbg.png build/html
|
||||
@ -0,0 +1,14 @@
|
||||
This directory contains mostly the things necessary for generating the
|
||||
Kig Python Scripting API documentation from the Kig source code. This
|
||||
file serves to answer two questions:
|
||||
|
||||
1 Why is this in its own directory ? Because, when I tried putting it
|
||||
in the directory above, the KDE_DOCS am_edit feature installed the
|
||||
Doxyfile and stuff in the documentation dir, which is bogus.
|
||||
|
||||
2 You copied doxygen.css, footer.html, header.html, headerbg.png,
|
||||
docheadergears.png, grad.png, bottom1.png and bottom2.png from
|
||||
kdelibs/doc/common, why didn't you use the already installed version
|
||||
in kde_htmldir/common ? -> because Kig is supposed to run on
|
||||
various KDE installations ( ranging from 3.1 to HEAD ), and I don't
|
||||
think the images in there are guaranteed not to change..
|
||||
|
After Width: | Height: | Size: 168 B |
|
After Width: | Height: | Size: 6.8 KiB |
@ -0,0 +1 @@
|
||||
dnl AC_OUTPUT( doc/kig/scripting-api/Doxyfile.scripting-api )
|
||||
|
After Width: | Height: | Size: 9.1 KiB |
@ -0,0 +1,156 @@
|
||||
/*******************************************************************************
|
||||
Adapted from the doxygen.css in kdelibs/doc/common by domi
|
||||
********************************************************************************/
|
||||
|
||||
/*******************************************************************************
|
||||
|
||||
Style sheet for kdelibs doxygen documentation.
|
||||
Copyright (c) Anders Lund <anders@alweb.dk> 2002
|
||||
|
||||
This script is made available under the terms of the General Public License.
|
||||
You should have received a copy of the GNU General Public License
|
||||
along with this software; see the file COPYING. If not, write to
|
||||
the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
|
||||
Boston, MA 02110-1301, USA.
|
||||
|
||||
********************************************************************************/
|
||||
|
||||
body {
|
||||
margin: 0px;
|
||||
color: black;
|
||||
background-color: white;
|
||||
}
|
||||
|
||||
a {
|
||||
color: #0000C0;
|
||||
}
|
||||
|
||||
/* decorative header */
|
||||
div.header {
|
||||
background-color: #0855C5;
|
||||
background-image: url("headerbg.png");
|
||||
}
|
||||
div.header table {
|
||||
padding: 0px;
|
||||
margin: 0px
|
||||
}
|
||||
div.header table tr td h1 {
|
||||
color: white;
|
||||
font: bold 20pt monospace;
|
||||
padding-top: 0.5em;
|
||||
}
|
||||
|
||||
/* global lind buttons at bottom of decorative header */
|
||||
table.links {
|
||||
float: right;
|
||||
border:0;
|
||||
padding-left:1px
|
||||
}
|
||||
table.links td a {
|
||||
color: white
|
||||
}
|
||||
table.links td:hover {
|
||||
background-color:#0C4293;
|
||||
}
|
||||
table.links td a:hover {
|
||||
color: white;
|
||||
background-color:#0C4293
|
||||
}
|
||||
table.links td {
|
||||
border-left: 1px solid #4A81D5;
|
||||
padding: 0px 12px 0px 12px;
|
||||
background-color:#0E4EAF;
|
||||
font-size:9pt;
|
||||
/*font-weight: bold;*/
|
||||
}
|
||||
|
||||
/* little gradient below decorative/navigation header */
|
||||
div#hgrad {
|
||||
height: 12px;
|
||||
background-image: url("grad.png");
|
||||
}
|
||||
|
||||
/* contents part of page */
|
||||
div.text {
|
||||
margin: 12px
|
||||
}
|
||||
|
||||
/* contents, mostly equivalent to the default doxugen style sheet */
|
||||
H1 { text-align: center; }
|
||||
CAPTION { font-weight: bold }
|
||||
A.qindex {}
|
||||
A.qindexRef {}
|
||||
A.el { text-decoration: none; font-weight: bold }
|
||||
A.elRef { font-weight: bold }
|
||||
A.code { text-decoration: none; font-weight: normal; color: #4444ee }
|
||||
A.codeRef { font-weight: normal; color: #4444ee }
|
||||
A:hover { text-decoration: none; background-color: #ececec }
|
||||
DL.el { margin-left: -1cm }
|
||||
DIV.fragment { width: 100%; border: none; background-color: #ffffee; padding: 12px }
|
||||
DIV.ah { background-color: navy; font-weight: bold; color: #ffffff; margin-bottom: 3px; margin-top: 3px }
|
||||
TD.md { background-color: #ececec; font-weight: bold; }
|
||||
TD.mdname1 { background-color: #ececec; font-weight: bold; color: #602020; }
|
||||
TD.mdname { background-color: #ececec; font-weight: bold; color: #602020; width: 600px; }
|
||||
DIV.groupHeader { margin-left: 16px; margin-top: 12px; margin-bottom: 6px; font-weight: bold }
|
||||
DIV.groupText { margin-left: 16px; font-style: italic; font-size: smaller }
|
||||
BODY { background: white }
|
||||
TD.indexkey {
|
||||
background-color: #e0eef8;
|
||||
font-weight: bold;
|
||||
padding-right : 10px;
|
||||
padding-top : 2px;
|
||||
padding-left : 10px;
|
||||
padding-bottom : 2px;
|
||||
margin-left : 0px;
|
||||
margin-right : 0px;
|
||||
margin-top : 2px;
|
||||
margin-bottom : 2px
|
||||
}
|
||||
TD.indexvalue {
|
||||
background-color: #e0eef8;
|
||||
font-style: normal;
|
||||
padding-right : 10px;
|
||||
padding-top : 2px;
|
||||
padding-left : 10px;
|
||||
padding-bottom : 2px;
|
||||
margin-left : 0px;
|
||||
margin-right : 0px;
|
||||
margin-top : 2px;
|
||||
margin-bottom : 2px
|
||||
}
|
||||
FONT.keyword { color: #008000 }
|
||||
FONT.keywordtype { color: #604020 }
|
||||
FONT.keywordflow { color: #e08000 }
|
||||
FONT.comment { color: #800000 }
|
||||
FONT.preprocessor { color: #806020 }
|
||||
FONT.stringliteral { color: #002080 }
|
||||
FONT.charliteral { color: #008080 }
|
||||
|
||||
|
||||
|
||||
/* kde decoration at bottom */
|
||||
div#bottom-nav {
|
||||
position : relative;
|
||||
background-color: transparent;
|
||||
/*width : 100%;*/
|
||||
/*top: 0px;
|
||||
left: 0px;
|
||||
right: 0px;
|
||||
margin-left: 0px;
|
||||
margin-right:0px;*/
|
||||
margin-top: 12px;
|
||||
height: 50px;
|
||||
background-image : url('bottom1.png');
|
||||
background-repeat : repeat-x;
|
||||
}
|
||||
|
||||
/* copyright etc at bottom */
|
||||
div.bottom {
|
||||
margin: 12px;
|
||||
font-size: 9pt;
|
||||
text-align: right;
|
||||
}
|
||||
div.bottom a {
|
||||
color: #aaaaaa
|
||||
}
|
||||
|
||||
@ -0,0 +1,15 @@
|
||||
<!-- Adapted from the footer.html in kdelibs/doc/common by domi -->
|
||||
</div>
|
||||
<div id="bottom-nav">
|
||||
<img src="bottom2.png" align="right" height="59" width="227" alt="KDE Logo">
|
||||
</div>
|
||||
<div class="bottom">
|
||||
This file is part of the documentation for kdelibs $projectnumber.
|
||||
</div>
|
||||
<div class="bottom" style="color:#cccccc">
|
||||
Documentation copyright © 1996-2002 the KDE developers.<br>
|
||||
Generated on $datetime by
|
||||
<a href="http://www.doxygen.org/index.html">doxygen</a> $doxygenversion written by <a href="mailto:dimitri@stack.nl">Dimitri van Heesch</a>, © 1997-2001
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
After Width: | Height: | Size: 248 B |
@ -0,0 +1,34 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<!-- Adapted from the header.html in kdelibs/doc/common by domi -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
|
||||
<title>$title ($projectname)</title>
|
||||
<link href="doxygen.css" rel="stylesheet" type="text/css">
|
||||
</head>
|
||||
<body>
|
||||
<div class="header">
|
||||
<table border="0" cellspacing="0" cellpadding="0">
|
||||
<tr>
|
||||
<td rowspan="2" width="92">
|
||||
<a href="index.html" title="The Kig Python Scripting API documentation main page"><img src="docheadergears.png" style="border:0px;" alt=""></a>
|
||||
</td>
|
||||
<td width="95%">
|
||||
<h1>$projectname Documentation</h1>
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="bottom">
|
||||
<table class="links" border=0 cellspacing=0>
|
||||
<tr>
|
||||
<td><a href="index.html">Overview</a></td>
|
||||
<td><a href="hierarchy.html" title="Inheritance list, sorted roughly alphabetically">Class Hierarchy</a></td>
|
||||
<td><a href="classes.html" title="Alphabetical list of classes">Classes</a></td>
|
||||
<td><a href="annotated.html" title="Classes, structs, unions and interfaces with brief descriptions">Classes (annotated)</a></td>
|
||||
<td><a href="functions.html" title="Documented class members with links to the classes they belong to">Members</a></td>
|
||||
</tr>
|
||||
</table>
|
||||
</td></tr></table>
|
||||
</div>
|
||||
<div id="hgrad"></div>
|
||||
<div class="text">
|
||||
|
After Width: | Height: | Size: 493 B |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 42 KiB |
|
After Width: | Height: | Size: 43 KiB |
|
After Width: | Height: | Size: 36 KiB |
|
After Width: | Height: | Size: 59 KiB |
|
After Width: | Height: | Size: 60 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
@ -0,0 +1,521 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&kiten;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kiten; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Katz-Brown</surname>
|
||||
<affiliation>
|
||||
<address><email>&Jason.Katz-Brown.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2002-10-08</date>
|
||||
<releaseinfo>1.1</releaseinfo>
|
||||
|
||||
<!-- Abstract about this handbook -->
|
||||
|
||||
<abstract>
|
||||
<para>&kiten; is a Japanese reference/study tool for &kde;. </para>
|
||||
</abstract>
|
||||
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>Japanese</keyword>
|
||||
<keyword>Language</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>&kiten; is an application with multiple functions. Firstly, it
|
||||
is a convenient English to Japanese and Japanese to English
|
||||
dictionary; secondly, it is a Kanji dictionary, with multiple ways to
|
||||
look up specific characters; thirdly, it is a tool to help you learn
|
||||
Kanji.</para>
|
||||
|
||||
<para>Each of these modes is discussed in its own chapter.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kiten;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="kiten1.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>&kiten; screenshot</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="dictionary">
|
||||
<title>Using the Dictionary</title>
|
||||
|
||||
<para>&kiten;'s most basic mode is as a dictionary for looking up both
|
||||
English and Japanese words. You can also add other dictionaries to
|
||||
&kiten;'s list.</para>
|
||||
|
||||
<para>&kiten; uses Jim Breen's Edict and Kanjidic as the default dictionaries. You can find more information at <ulink url="http://www.csse.monash.edu.au/~jwb/edict.html">the Edict web site</ulink> and <ulink url="http://www.csse.monash.edu.au/~jwb/kanjidic.html">the Kanjidic web site</ulink>.</para>
|
||||
|
||||
<sect1 id="looking-up-words">
|
||||
<title>Looking Up Words</title>
|
||||
|
||||
<para>To look up words in either language, type them in to the
|
||||
text-edit (much like &konqueror;'s location bar) and press either
|
||||
<keycap>Enter</keycap> or the <guilabel>Search</guilabel> button on
|
||||
the toolbar (again, much like &konqueror;). &kiten; will then look up
|
||||
the word.</para>
|
||||
|
||||
<para>You can enter Kanji, Kana and English and get back results from
|
||||
&kiten;. These results of your search will appear in the large
|
||||
results view which takes up the majority of the &kiten; window.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>searching for an English translation</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="kiten2.png" format="PNG"/></imageobject>
|
||||
<textobject><phrase>&kiten; search screenshot</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect2>
|
||||
<title>Filtering</title>
|
||||
|
||||
<para>Often times you will want to filter rare words from your
|
||||
search. &kiten; will do this for you if toggle
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Filter
|
||||
Rare</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<note><para>Not all dictionary files support filtering rare entries -
|
||||
most dictionaries, excluding the two provided by default in &kiten; do
|
||||
not.</para></note>
|
||||
|
||||
<para>If you have not enabled filtering rare entries, common entries
|
||||
will be labeled <guilabel>Common</guilabel> in the result view.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="advanced-searches">
|
||||
<title>Advanced Searches</title>
|
||||
|
||||
<para>&kiten; supports more advanced searches than plain normal word
|
||||
searches.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Options for Matching English</title>
|
||||
|
||||
<para>Case sensitivity and whole-word matching can be enabled or
|
||||
disabled by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Kiten...</guimenuitem></menuchoice>, and then choosing the
|
||||
<guilabel>Searching</guilabel> item on the list on the left. The
|
||||
options can be enabled by checking the check boxes and disabled by
|
||||
unchecking the check boxes on this page. These options are global and
|
||||
affect all searches.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Beginning/Anywhere Searches</title>
|
||||
|
||||
<para>To search for the beginning of a word, instead of pressing the
|
||||
<guilabel>Search</guilabel> button on the toolbar or pressing
|
||||
<keycap>Return</keycap> on the text-entry in the toolbar, choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Search with
|
||||
Beginning of Word</guimenuitem></menuchoice>. Similarly, choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Search
|
||||
Anywhere</guimenuitem></menuchoice> to search for your text anywhere
|
||||
in a word. These search modes work for searches of both
|
||||
languages.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Searching in Results</title>
|
||||
|
||||
<para>&kiten; can also help you refine your searches by allowing you
|
||||
to search for new text in the results generated by a previous
|
||||
search. To do this, just choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Search in
|
||||
Results</guimenuitem></menuchoice> to perform your search.</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="deinf">
|
||||
<title>Verb Deinflection</title>
|
||||
|
||||
<para>&kiten; can deinflect verbs you search for. To enable this, make
|
||||
sure <menuchoice><guimenu>Settings</guimenu><guimenuitem>Deinflect
|
||||
Verbs in Regular Search</guimenuitem></menuchoice> is checked. &kiten;
|
||||
will then deinflect Japanese you search for that starts with a Kanji
|
||||
and ends with a Kana.</para>
|
||||
<para>
|
||||
The "Deinflect" option tries to unconjugate Japanese verbs. Deinflect only supports the common verb conjugations. If you search a lot of Japanese text you might consider using this option until you get used to handling Japanese verb forms.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="looking-up-kanji">
|
||||
<title>Looking Up Kanji</title>
|
||||
|
||||
<para>&kiten; has features that makes finding the one kanji you want
|
||||
easy from over 14,000 in the default dictionary.</para>
|
||||
|
||||
<note> <para>Clicking on any Kanji in the main result view will show
|
||||
details on that particular Kanji. This can sometimes be the fastest
|
||||
way to look up a kanji.</para></note>
|
||||
|
||||
<tip><para>Kanji searches are also filtered according to whether
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Filter
|
||||
Rare</guimenuitem></menuchoice> is checked.</para></tip>
|
||||
|
||||
<sect1 id="regular-kanji-search">
|
||||
<title>Regular Searching</title>
|
||||
|
||||
<para>To enable regular searching on the Kanji dictionary, check
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Kanjidic</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>You can search with English and Japanese search strings the
|
||||
exact same way you can with the normal dictionary.</para>
|
||||
|
||||
<caution><para>When searching for Kana readings in the Kanji
|
||||
dictionary, you will have to put a period before the okurigana (the
|
||||
kana that are not part of the Kanji).</para></caution>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="radical-search">
|
||||
<title>Radical Searching</title>
|
||||
|
||||
<para>You can use &kiten;'s radical search dialog to search for Kanji
|
||||
with a combination of radicals and a certain stroke count. Choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Radical
|
||||
Search...</guimenuitem></menuchoice> to open the radical search
|
||||
dialog.</para>
|
||||
|
||||
<para>To choose the radicals you want to be in your Kanji, select them
|
||||
from the middle listbox. To display possible radicals to select from
|
||||
this listbox with a certain number of strokes, choose this number of
|
||||
strokes from the spinbox just above the listbox. The radicals you
|
||||
choose will appear in the listbox to the right.</para>
|
||||
|
||||
<para>To choose how many strokes your Kanji should have, first check
|
||||
the <guilabel>Search by total strokes</guilabel> checkbox. (If you do
|
||||
not want to search by total strokes, uncheck this checkbox.) Then
|
||||
select the number of strokes from the spinbox on the left, under the
|
||||
checkbox. If you want the stroke count to be fuzzy by a certain number
|
||||
of strokes, select the margin of error from the spinbox to the right
|
||||
of the <guilabel>+/-</guilabel> label.</para>
|
||||
|
||||
<para>To perform the lookup, press the <guibutton>Look Up</guibutton>
|
||||
button.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="grade-search">
|
||||
<title>Grade Search</title>
|
||||
|
||||
<para>To get a list of all Kanji in a certain grade, enter that grade
|
||||
in the main text-entry in the toolbar. Then choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Grade</guimenuitem></menuchoice>
|
||||
to perform your search.</para>
|
||||
|
||||
<tip><para>You can enter <userinput>Jouyou</userinput> and
|
||||
<userinput>Jinmeiyou</userinput> to get Kanji not in a regular grade
|
||||
but in those groups.</para></tip>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="stroke-search">
|
||||
<title>Stroke Search</title>
|
||||
|
||||
<para>To get a list of all Kanji with a certain number of strokes,
|
||||
enter that number in the text-entry in the toolbar. Then choose
|
||||
<menuchoice><guimenu>Search</guimenu><guimenuitem>Strokes</guimenuitem></menuchoice>
|
||||
to perform your search.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="misc">
|
||||
<title>Miscellaneous</title>
|
||||
|
||||
<para>This chapter describes miscellaneous features that can be used
|
||||
in both modes in &kiten;'s main window.</para>
|
||||
|
||||
<sect1 id="history">
|
||||
<title>The History</title>
|
||||
|
||||
<para>&kiten; keeps track of all of your queries in a list. You can
|
||||
see your last 20 results by looking under
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>History</guimenuitem></menuchoice>. To
|
||||
go forward one in the history, choose
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Forward</guimenuitem></menuchoice>. To
|
||||
go backward one in the history, choose
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Back</guimenuitem></menuchoice>.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="input">
|
||||
<title>Inputting Japanese</title>
|
||||
|
||||
<para>If you are unable to input Japanese normally into &kde;
|
||||
applications, you can use &kiten;'s Kana input system that is built in
|
||||
to the text-entry.</para>
|
||||
|
||||
<para>To start Kana input, press <keycombo
|
||||
action="simul">&Shift;<keycap>Space</keycap></keycombo>. Now inputted
|
||||
syllables will be transformed into Hiragana. If you type a syllable in
|
||||
capital letters, it will be transformed into Katakana instead. Press
|
||||
<keycombo action="simul">&Shift;<keycap>Space</keycap></keycombo>
|
||||
again to go back to regular input.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="global-keys">
|
||||
<title>Global Shortcuts</title>
|
||||
|
||||
<para>You can set global &kiten; shortcuts that work everywhere on
|
||||
your desktop. Go to the &kiten; configuration dialog, which can be
|
||||
opened by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Kiten...</guimenuitem></menuchoice>. Select the <guilabel>Global
|
||||
Keys</guilabel> section of the dialog. Here you can set the keys for a
|
||||
global word search and a global Kanji search like in other &kde;
|
||||
shortcut configuration panels.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="printing">
|
||||
<title>Printing</title>
|
||||
|
||||
<para>You can print the result view by choosing
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Print</guimenuitem></menuchoice>. &kiten;
|
||||
will add an informative header to the printout.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="fonts">
|
||||
<title>Fonts</title>
|
||||
|
||||
<para>You can choose the font that &kiten; uses in its result view and
|
||||
while printing. Go to the &kiten; configuration dialog, which can be
|
||||
opened by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Kiten...</guimenuitem></menuchoice>. Select the
|
||||
<guilabel>Font</guilabel> section of the dialog and select the font in
|
||||
the font-chooser.</para>
|
||||
|
||||
<note><para>&Qt; 3's new font-substitution system makes it so a
|
||||
Japanese font will always be substituted for Japanese characters, even
|
||||
if the font you specify doesn't include them. Thus, you can choose any
|
||||
font in the chooser and everything should still display
|
||||
fine.</para></note>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="learn"> <title>Learn Mode</title>
|
||||
|
||||
<para>&kiten;'s last mode is its Learn mode which is in a separate
|
||||
window. To open it, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Learn...</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>The Learn mode window in turn has two main tabs - one where
|
||||
where you maintain your <quote>Learning List</quote>, which is the
|
||||
list of Kanji that you are currently trying to learn. The other tab is
|
||||
the quiz area, where you are given a never-ending quiz on the Kanji on
|
||||
your Learning List.</para>
|
||||
|
||||
<tip><para>If you want the Learn window to open every time you start
|
||||
up &kiten;, check the <guilabel>Start Learn on Kiten
|
||||
startup</guilabel> check box in the <guilabel>Learn</guilabel> section
|
||||
of the configuration dialog, which can be opened by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Kiten...</guimenuitem></menuchoice>.</para></tip>
|
||||
|
||||
<sect1 id="browsing-learn">
|
||||
<title>The Learn Browser</title>
|
||||
|
||||
<para>The first tab of the Learn mode window, the
|
||||
<guilabel>List</guilabel> tab, provides an area to browse the Kanji in
|
||||
the 8 Kanji grades - 1st-6th grade, <guilabel>Others in
|
||||
Jouyou</guilabel>, and <guilabel>Jinmeiyou</guilabel>. Also in the top
|
||||
half of the tab is a listview which contains all of the Kanji on your
|
||||
Learning List.</para>
|
||||
|
||||
<para>To choose a grade to browse, choose it from the list in
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Grade</guimenuitem></menuchoice>. After
|
||||
selecting a grade, the first Kanji in that grade will be shown.</para>
|
||||
|
||||
<para>To go forward one Kanji in the current grade, choose
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Forward</guimenuitem></menuchoice>. To
|
||||
go back one Kanji, choose
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Back</guimenuitem></menuchoice>. To
|
||||
go to a random Kanji, choose
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Random</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<tip><para>If you click on a Kanji in the top view, the main &kiten;
|
||||
window will give detailed information on the Kanji you
|
||||
clicked.</para></tip>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="populating-learning-list">
|
||||
<title>Populating the Learning List</title>
|
||||
|
||||
<para>There are three ways to add Kanji to the Learning List. To add
|
||||
the current Kanji (the one displayed in the view on the top) to your
|
||||
list, choose
|
||||
<menuchoice><guimenu>Edit</guimenu><guimenuitem>Add</guimenuitem></menuchoice>. To
|
||||
add all Kanji in the current grade to your list, choose
|
||||
<menuchoice><guimenu>Edit</guimenu><guimenuitem>Add
|
||||
All</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>The current Kanji in the main &kiten; window can also be added
|
||||
by choosing (in the main &kiten; window)
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Add Kanji to Learning
|
||||
List</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>To delete a Kanji on your Learning List, select it and choose
|
||||
<menuchoice><guimenu>Edit</guimenu><guimenuitem>Delete</guimenuitem></menuchoice>. You
|
||||
can also select a range of Kanji to delete by clicking in the list
|
||||
while holding down the &Shift; or &Ctrl; keys.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="file-list">
|
||||
<title>Managing Learning List Files</title>
|
||||
|
||||
<para>Learning Lists can be saved to files for easy storage.</para>
|
||||
|
||||
<para>To open a list, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Open...</guimenuitem></menuchoice>
|
||||
and choose the existing list file in the file dialog.</para>
|
||||
|
||||
<para>To open a new list, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Open...</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<para>To save a list, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice>
|
||||
and choose the file to save your list to. To save the list under a
|
||||
different filename, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Save
|
||||
As...</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<note><para>When you close the Learn window the list you have opened
|
||||
will be re-opened the next time you start Learn mode.</para></note>
|
||||
|
||||
<para>To print out your Learning List, choose
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Print</guimenuitem></menuchoice>.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="quizzing">
|
||||
<title>Quizzing</title>
|
||||
|
||||
<para>The second tab of the Learn window is the
|
||||
<guilabel>Quiz</guilabel> tab. If you have at least two Kanji on your
|
||||
Learning List, this tab will be enabled. Click on the tab to switch to
|
||||
it.</para>
|
||||
|
||||
<para>To answer the question, click on the pushbutton that contains
|
||||
the answer that matches with the Kanji on the centered
|
||||
pushbutton.</para>
|
||||
|
||||
<para>If you do not know the answer, you can cheat by choosing
|
||||
<menuchoice><guimenu>Go</guimenu><guimenuitem>Cheat</guimenuitem></menuchoice>. This
|
||||
will set the correct pushbutton's focus.</para>
|
||||
|
||||
<tip><para>To see full information about the Kanji, click on the
|
||||
button it is drawn on. This will be counted as a wrong answer,
|
||||
however, in the same way as if you cheated.</para></tip>
|
||||
|
||||
<para>If you choose the wrong answer, or cheat, your score for that
|
||||
Kanji will be decremented. If you choose the correct answer, your
|
||||
score will be incremented by two. Your score on the Kanji are shown on
|
||||
the very right-hand column of your Learning List (on the
|
||||
<guilabel>List</guilabel> tab of the Learn window).</para>
|
||||
|
||||
<note><para>Your scores are stored globally for each Kanji - thus, the
|
||||
same Kanji in two different files will always have the same
|
||||
score.</para></note>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="config-quiz">
|
||||
<title>Configuring Quizzing</title>
|
||||
|
||||
<para>You can change the way quizzing works in the &kiten;
|
||||
configuration dialog, which can be opened by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
Kiten...</guimenuitem></menuchoice>. Go to the
|
||||
<guilabel>Learn</guilabel> section, and look at the
|
||||
<guilabel>Quizzing</guilabel> groupbox. Here you can change whether
|
||||
the Kanji, meaning, or reading is given for the clue, and what is
|
||||
given for you to guess on.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits-and-license">
|
||||
<title>Credits and Licenses</title>
|
||||
|
||||
<para>&kiten; copyright 2001, 2002 &Jason.Katz-Brown;</para>
|
||||
|
||||
<itemizedlist>
|
||||
<title>Developers</title>
|
||||
<listitem>
|
||||
<para>&Jason.Katz-Brown; <email>&Jason.Katz-Brown.mail;</email></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>&Neil.Stevens; <email>&Neil.Stevens.mail;</email></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Jim Breen <email>jwb@csse.monash.edu.au</email> - Wrote xjdic, of which &kiten; borrows code, and the xjdic index file generator. Also is main author of edict and kanjidic, which &kiten; essentially require.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Paul Temple <email>paul.temple@gmx.net</email> - Port to KConfig XT and bug fixing.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Documentation copyright 2002, &Jason.Katz-Brown;</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
<!-- <appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
&install.compile.documentation;
|
||||
|
||||
</appendix> -->
|
||||
|
||||
&documentation.index;
|
||||
</book>
|
||||
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 54 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
@ -0,0 +1,19 @@
|
||||
The KLatin doc comprises several files that are used as online help by the users.
|
||||
These files are part of the User HandBook.
|
||||
|
||||
These files are
|
||||
- adjectives.docbook
|
||||
- nouns.docbook
|
||||
- numbers.docbook
|
||||
- pronouns.docbook
|
||||
- verbs.docbook
|
||||
|
||||
In these files, the Latin words must not be translated. Only English words are to be translated.
|
||||
I inserted several comments in order to help the translators.
|
||||
|
||||
Please do tell me if anything is not correct or not enough explained.
|
||||
|
||||
Anne-Marie Mahfouf
|
||||
annma@kde.org
|
||||
|
||||
09 May 2002
|
||||
@ -0,0 +1,278 @@
|
||||
<!-- Please don't translate Latin words -->
|
||||
<!-- Please translate the following -->
|
||||
<sect1 id="adjectives">
|
||||
<title> KLatin Notes - Adjectives</title>
|
||||
|
||||
<para>
|
||||
Adjectives are words to describe nouns, and so they agree with the nouns. Agreeing means
|
||||
that they match the noun they refer to in three ways: gender, number, and case.
|
||||
</para>
|
||||
|
||||
<table frame="none">
|
||||
<!--Please translate title-->
|
||||
<title>1st and 2nd Declension Adjectives (212)</title>
|
||||
<tgroup cols="4" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row>
|
||||
<!-- Please translate SINGULAR and Like-->
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>Like Servus</entry>
|
||||
<entry>Like Puella</entry>
|
||||
<entry>Like Bellum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- Please translate the first entry of each row-->
|
||||
<entry>Nominative</entry>
|
||||
<entry>bon-us</entry>
|
||||
<entry>bon-a</entry>
|
||||
<entry>bon-um</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>bon-e</entry>
|
||||
<entry>bon-a</entry>
|
||||
<entry>bon-um</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>bon-um</entry>
|
||||
<entry>bon-am</entry>
|
||||
<entry>bon-um</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>bon-i</entry>
|
||||
<entry>bon-ae</entry>
|
||||
<entry>bon-i</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>bon-o</entry>
|
||||
<entry>bon-ae</entry>
|
||||
<entry>bon-o</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>bon-o</entry>
|
||||
<entry>bon-a</entry>
|
||||
<entry>bon-o</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- Please translate the first entry of each row-->
|
||||
<entry>PLURAL</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Nominative</entry>
|
||||
<entry>bon-i</entry>
|
||||
<entry>bon-ae</entry>
|
||||
<entry>bon-a</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>bon-i</entry>
|
||||
<entry>bon-ae</entry>
|
||||
<entry>bon-a</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>bon-os</entry>
|
||||
<entry>bon-as</entry>
|
||||
<entry>bon-a</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>bon-orum</entry>
|
||||
<entry>bon-arum</entry>
|
||||
<entry>bon-orum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>bon-is</entry>
|
||||
<entry>bon-is</entry>
|
||||
<entry>bon-is</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>bon-is</entry>
|
||||
<entry>bon-is</entry>
|
||||
<entry>bon-is</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table frame="none">
|
||||
<!--Please translate the title-->
|
||||
<title>3rd Declension Adjectives (333)</title>
|
||||
|
||||
<tgroup cols="4" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row>
|
||||
<!-- Please translate SINGULAR and Like-->
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>Like Rex</entry>
|
||||
<entry>Like Rex</entry>
|
||||
<entry>Like Opus</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- Please translate the first entry of each row-->
|
||||
<entry>Nominative</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-e</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-e</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>trist-em</entry>
|
||||
<entry>trist-em</entry>
|
||||
<entry>trist-e</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>trist-i</entry>
|
||||
<entry>trist-i</entry>
|
||||
<entry>trist-is</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-is</entry>
|
||||
<entry>trist-i</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>trist-i</entry>
|
||||
<entry>trist-i</entry>
|
||||
<entry>trist-i</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- Please translate the first entry of each row-->
|
||||
<entry>PLURAL</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Nominative</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-ia</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-ia</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-es</entry>
|
||||
<entry>trist-ia</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>trist-ium</entry>
|
||||
<entry>trist-ium</entry>
|
||||
<entry>trist-ium</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
<entry>trist-ibus</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table frame="none">
|
||||
<!-- Please translate the title -->
|
||||
<title>Comparison of Adjectives</title>
|
||||
<!-- Please translate -->
|
||||
<tgroup cols="4" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Positive</entry>
|
||||
<entry>Comparative</entry>
|
||||
<entry>Superlative</entry>
|
||||
<entry>Notes</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Normal form of Adjective</entry>
|
||||
<!--Please stop translating -->
|
||||
<entry>Stem + ior,-ius</entry>
|
||||
<entry>Stem + issimus,-a,-um</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry>Stem + rimus,-a,-um</entry>
|
||||
<entry>For adjectives which end with <emphasis>-er</emphasis>. For example: acer-rimus,-a,-um</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry>Stem + limus,-a,-um</entry>
|
||||
<entry>For adjectives which end with <emphasis>-ilis</emphasis>. For example: facil-limus,-a,-um</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry>Per/Prae + Adjective</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</sect1>
|
||||
|
||||
@ -0,0 +1,502 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY klatin "<application>KLatin</application>">
|
||||
<!ENTITY kappname "&klatin;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY kvtml "<acronym>KVTML</acronym>">
|
||||
<!ENTITY numbers SYSTEM "numbers.docbook">
|
||||
<!ENTITY verbs SYSTEM "verbs.docbook">
|
||||
<!ENTITY adjectives SYSTEM "adjectives.docbook">
|
||||
<!ENTITY nouns SYSTEM "nouns.docbook">
|
||||
<!ENTITY pronouns SYSTEM "pronouns.docbook">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &klatin; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>George</firstname>
|
||||
<surname>Wright</surname>
|
||||
<affiliation>
|
||||
<address><email>gwright@kde.org</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<othercredit role="developer">
|
||||
<firstname>Anne-Marie</firstname>
|
||||
<surname>Mahfouf</surname>
|
||||
<affiliation>
|
||||
<address><email>&Anne-Marie.Mahfouf.mail;</email></address>
|
||||
</affiliation>
|
||||
<contrib>Help in documentation</contrib>
|
||||
</othercredit>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001-2004</year>
|
||||
<holder>George Wright</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2006-02-24</date>
|
||||
<releaseinfo>0.9</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&klatin; is a &kde; application to help revise/teach Latin.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>KLatin</keyword>
|
||||
<keyword>Latin</keyword>
|
||||
<keyword>education</keyword>
|
||||
<keyword>language</keyword>
|
||||
<keyword>latin</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&klatin; is a program to help revise Latin. There are three
|
||||
<quote>sections</quote> in which different aspects of the language can be
|
||||
revised. These are the vocabulary, grammar, and verb testing sections. In
|
||||
addition there is a set of revision notes that can be used for self-guided
|
||||
revision.
|
||||
</para>
|
||||
<para>
|
||||
In the vocabulary section an &XML; file is loaded containing various words and
|
||||
their local language translations. &klatin; asks you what each of these words
|
||||
translate into. The questions take place in a multiple-choice environment.
|
||||
</para>
|
||||
<para>
|
||||
In the grammar and verb sections &klatin; asks for a particular part of a noun
|
||||
or a verb, such as the <quote>ablative singular</quote>, or the <quote>1st
|
||||
person indicative passive plural</quote>, and is not multiple choice.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="using-klatin">
|
||||
<title>Using &klatin;</title>
|
||||
|
||||
<para>
|
||||
When you start &klatin;, you are greeted by four options that you can choose
|
||||
from.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; main screen, directly after the first start</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klatin1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; main screen</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The first one, <guilabel>Vocabulary</guilabel>, is a
|
||||
multiple-choice vocabulary tester.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; vocabulary section</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klatin2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; vocabulary</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
After you finish your test, a results screen is displayed.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; vocabulary results</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="results.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; results</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The second, <guilabel>Grammar</guilabel> tests you on grammatical parts of
|
||||
nouns.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; grammar section</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klatin3.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; grammar</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
<guilabel>Verbs</guilabel> is almost the same as the <guilabel>Grammar</guilabel>
|
||||
section, except that it tests you on verb forms.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; verbs section</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klatin4.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; verbs</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The fourth section,
|
||||
<guilabel>Revision notes</guilabel>, loads &konqueror; into the &klatin; revision notes
|
||||
section.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In addition to the options, you can also launch these sections via the menubar,
|
||||
in the <guimenu>Section</guimenu>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The configuration dialog for &klatin; can be accessed by choosing
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
&klatin;...</guimenuitem></menuchoice> from the menu.
|
||||
<!-- In the <quote>General</quote> settings page, you can configure your name.-->
|
||||
In the <guilabel>Vocabulary</guilabel> page, you can set whether you want the test to
|
||||
take place from your language into Latin, or vice versa. You can also choose
|
||||
the default file which you want to use to test your vocabulary on, and you can
|
||||
also set how many questions you want to be tested on.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>&klatin; configuration dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klatin-configuration.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klatin; configuration dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="klatin-mainwindow">
|
||||
<title>The &klatin; Main Window</title>
|
||||
<para>The &klatin; main window consists of four option buttons to choose which
|
||||
section to enter, and a menubar.</para>
|
||||
<para>Choose from the <guilabel>Revision Sections</guilabel> list a section and
|
||||
click <guibutton>Start</guibutton> to start the chosen section.</para>
|
||||
|
||||
<para>When you are finished with that section, click <guibutton>Back</guibutton>
|
||||
to return to &klatin;'s main menu.</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
<sect1 id="menu-file">
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quits</action> &klatin;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="menu-section">
|
||||
<title>The <guimenu>Section</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Section</guimenu>
|
||||
<guimenuitem>Load Vocabulary</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Loads</action> the vocabulary section</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Section</guimenu>
|
||||
<guimenuitem>Load Grammar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Loads</action> the grammar section</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Section</guimenu>
|
||||
<guimenuitem>Load Verbs</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Loads</action> the verbs section</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Section</guimenu>
|
||||
<guimenuitem>Load Revision</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Loads</action> the revision section</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
<sect1 id="menu-settings">
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> the keyboard keys you use to access the different actions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Not implemented yet.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &klatin;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Display</action> the &klatin; settings dialog
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="menu-help">
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
&help.menu.documentation;
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="translation">
|
||||
<title>Translation Guide to &klatin;</title>
|
||||
|
||||
<para>Only the vocabulary files have to be translated in your language. The
|
||||
vocabulary files use the &kvtml; format, which is the same as other programs
|
||||
such as &kwordquiz; use. &kwordquiz; is very useful as you can create the
|
||||
vocabulary files in that and load them directly into &klatin;.
|
||||
</para>
|
||||
<para>
|
||||
Below is explained how you can translate &klatin; vocabulary files. At the
|
||||
moment, the files are only in English, German and Polish.
|
||||
</para>
|
||||
<sect1 id="translate_vocab">
|
||||
<title>How To Translate &klatin; vocabulary files</title>
|
||||
<procedure>
|
||||
<step>
|
||||
<para>
|
||||
Get the latest &klatin; code from CVS or a latest release. The words are stored in
|
||||
<filename class="directory">source_dir_of_kdeedu/klatin/klatin/data/vocab/en/</filename>
|
||||
in files like <filename>A.kvtml</filename> for Latin words beginning with A,
|
||||
<filename>BC.kvtml</filename> for Latin words beginning with B and C and so on.
|
||||
</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>
|
||||
Create a new subdirectory in <filename class="directory">data/vocab/</filename> named
|
||||
as your language code (for example, <filename
|
||||
class="directory">fr</filename> for French, <filename
|
||||
class="directory">ja</filename> for Japanese). Copy all the English vocabulary files there as well as
|
||||
the <filename>Makefile.am</filename>. Edit the <filename>Makefile.am</filename>
|
||||
and replace <quote>en</quote> with your language code.
|
||||
</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>
|
||||
In <filename class="directory">data/vocab/<replaceable>your_language_code</replaceable></filename>, edit
|
||||
all the files and translate the English words, &ie; those that are between the
|
||||
<sgmltag class="starttag">t</sgmltag> and <sgmltag class="endtag">t</sgmltag>
|
||||
tags.
|
||||
</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>
|
||||
Please send them to George
|
||||
<email>gwright@users.sourceforge.net</email>.
|
||||
</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="developers">
|
||||
<title>Developer's Guide to &klatin;</title>
|
||||
<sect1 id="add_files">
|
||||
<title>Create new vocabulary files</title>
|
||||
<para>
|
||||
The &klatin; vocabulary database system is very easy to extend. Just look at
|
||||
the files and you'll understand! It uses the &kvtml; format, which is the same
|
||||
as other programs such as &kwordquiz; use. So you can open &kwordquiz; and use
|
||||
it to create the vocabulary files.
|
||||
</para>
|
||||
<para>
|
||||
You can save your new files in the corresponding folder depending on what
|
||||
language they refer to in <filename class="directory">.kde/share/apps/klatin/data/vocab/<replaceable>language_code</replaceable>/</filename>.
|
||||
For example, English &kvtml; files are kept in a folder called
|
||||
<filename class="directory">en</filename>, German files in <filename class="directory">de</filename>, and so on. You can also
|
||||
send me your files so I can add them in the next &klatin; release.
|
||||
</para>
|
||||
</sect1>
|
||||
<!-- FIXME: They will still need specifically outlining -->
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&klatin;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2001-2004 George Wright <email>gwright@users.sourceforge.net</email>
|
||||
</para>
|
||||
<para>
|
||||
Contributors:
|
||||
<itemizedlist>
|
||||
|
||||
<listitem><para>&Neil.Stevens; <email>&Neil.Stevens.mail;</email></para>
|
||||
</listitem>
|
||||
<listitem><para>&Anne-Marie.Mahfouf; <email>&Anne-Marie.Mahfouf.mail;</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Mark Westcott <email>mark@houseoffish.org</email></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2001-2004 George Wright <email>gwright@users.sourceforge.net</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL;
|
||||
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="klatin-index">
|
||||
<title>&klatin; notes</title>
|
||||
|
||||
<para>
|
||||
Welcome to the &klatin; notes section. This is aimed to help
|
||||
you in your revision and covers the English <acronym>GCSE</acronym> syllabus (England).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Here are the different sections you can get help for:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><link
|
||||
linkend="numbers">Latin numbers</link>
|
||||
</para></listitem>
|
||||
<listitem><para><link
|
||||
linkend="verbs">Latin verbs</link>
|
||||
</para></listitem>
|
||||
<listitem><para><link
|
||||
linkend="nouns">Latin nouns</link>
|
||||
</para></listitem>
|
||||
<listitem><para><link
|
||||
linkend="adjectives">Latin adjectives</link>
|
||||
</para></listitem>
|
||||
<listitem><para><link
|
||||
linkend="pronouns">Latin pronouns</link>
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
&numbers;
|
||||
&verbs;
|
||||
&nouns;
|
||||
&adjectives;
|
||||
&pronouns;
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-klatin">
|
||||
<title>How to obtain &klatin;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
-->
|
||||
|
||||
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 22 KiB |
@ -0,0 +1,211 @@
|
||||
<!-- Please don't translate Latin words -->
|
||||
<!-- Please translate -->
|
||||
<sect1 id="nouns">
|
||||
<title> KLatin Notes - Nouns </title>
|
||||
|
||||
<para>
|
||||
Nouns, like verbs, are divided into groups, called <emphasis>declensions</emphasis>. There are five
|
||||
declensions and three genders: masculine, feminine, and neuter.
|
||||
</para>
|
||||
<para>
|
||||
The stem of a noun is the basic part of the noun that does not change. To get
|
||||
the stem of a noun, take the genitive singular of the noun, and take off its
|
||||
ending. For example: the stem of <emphasis>puella</emphasis> is
|
||||
<emphasis>puell</emphasis>; while the stem of <emphasis>rex</emphasis> is
|
||||
<emphasis>reg</emphasis>, because its genitive is <emphasis>reg-is</emphasis>.
|
||||
</para>
|
||||
|
||||
<sect2 id="listing">
|
||||
<title>Latin Nouns</title>
|
||||
|
||||
<table frame="none">
|
||||
<title>Noun listings</title>
|
||||
<tgroup cols="9" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row>
|
||||
<!-- Please translate -->
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>1st Feminine</entry>
|
||||
<entry>2nd Masculine</entry>
|
||||
<entry>2nd Neuter</entry>
|
||||
<entry>3rd Masc/Fem</entry>
|
||||
<entry>3rd Neuter</entry>
|
||||
<entry>4th Masculine</entry>
|
||||
<entry>4th Neuter</entry>
|
||||
<entry>5th Feminine</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!--From now on please just translate first entry of each row-->
|
||||
<entry>Nominative</entry>
|
||||
<entry>puell-a</entry>
|
||||
<entry>serv-us</entry>
|
||||
<entry>bell-um</entry>
|
||||
<entry><emphasis>rex</emphasis></entry>
|
||||
<entry>opus</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>genu</entry>
|
||||
<entry>res</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>puell-a</entry>
|
||||
<entry>serv-e</entry>
|
||||
<entry>bell-um</entry>
|
||||
<entry><emphasis>rex</emphasis></entry>
|
||||
<entry> opus</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>genu</entry>
|
||||
<entry>res</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>puell-am</entry>
|
||||
<entry>serv-um</entry>
|
||||
<entry>bell-um</entry>
|
||||
<entry>reg-em</entry>
|
||||
<entry>opus</entry>
|
||||
<entry>grad-um</entry>
|
||||
<entry>genu</entry>
|
||||
<entry>re-m</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>puell-ae</entry>
|
||||
<entry>serv-i</entry>
|
||||
<entry>bell-i</entry>
|
||||
<entry>reg-is</entry>
|
||||
<entry>oper-is</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>gen-u</entry>
|
||||
<entry>re-i</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>puell-ae</entry>
|
||||
<entry>serv-o</entry>
|
||||
<entry>bell-o</entry>
|
||||
<entry>reg-i</entry>
|
||||
<entry>oper-i</entry>
|
||||
<entry>grad-ui</entry>
|
||||
<entry>gen-u</entry>
|
||||
<entry>re-i</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>puell-a</entry>
|
||||
<entry>serv-o</entry>
|
||||
<entry>bell-o</entry>
|
||||
<entry>reg-e</entry>
|
||||
<entry>oper-e</entry>
|
||||
<entry>grad-u</entry>
|
||||
<entry>gen-u</entry>
|
||||
<entry>re</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<!-- Please translate only the first entry of each row -->
|
||||
<entry>PLURAL</entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Nominative</entry>
|
||||
<entry>puell-ae</entry>
|
||||
<entry>serv-i</entry>
|
||||
<entry>bell-a</entry>
|
||||
<entry>reg-es</entry>
|
||||
<entry>oper-a</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>gen-ua</entry>
|
||||
<entry>res</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Vocative</entry>
|
||||
<entry>puell-ae</entry>
|
||||
<entry>serv-i</entry>
|
||||
<entry>bell-a</entry>
|
||||
<entry>reg-es</entry>
|
||||
<entry>oper-a</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>gen-ua</entry>
|
||||
<entry>res</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Accusative</entry>
|
||||
<entry>puell-as</entry>
|
||||
<entry>serv-os</entry>
|
||||
<entry>bell-a</entry>
|
||||
<entry>reg-es</entry>
|
||||
<entry>oper-a</entry>
|
||||
<entry>grad-us</entry>
|
||||
<entry>gen-ua</entry>
|
||||
<entry>res</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Genitive</entry>
|
||||
<entry>puell-arum</entry>
|
||||
<entry>serv-orum</entry>
|
||||
<entry>bell-orum</entry>
|
||||
<entry>reg-um</entry>
|
||||
<entry>oper-um</entry>
|
||||
<entry>grad-uum</entry>
|
||||
<entry>gen-uum</entry>
|
||||
<entry>re-rum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Dative</entry>
|
||||
<entry>puell-is</entry>
|
||||
<entry>serv-is</entry>
|
||||
<entry>bell-is</entry>
|
||||
<entry>reg-ibus</entry>
|
||||
<entry>oper-ibus</entry>
|
||||
<entry>grad-ibus</entry>
|
||||
<entry>gen-ibus</entry>
|
||||
<entry>re-bus</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ablative</entry>
|
||||
<entry>puell-is</entry>
|
||||
<entry>serv-is</entry>
|
||||
<entry>bell-is</entry>
|
||||
<entry>reg-ibus</entry>
|
||||
<entry>oper-ibus</entry>
|
||||
<entry>grad-ibus</entry>
|
||||
<entry>gen-ibus</entry>
|
||||
<entry>re-bus</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -0,0 +1,221 @@
|
||||
<!-- Please don't translate Latin words -->
|
||||
<!-- Please translate -->
|
||||
<sect1 id="numbers">
|
||||
<title>KLatin Notes - Numbers </title>
|
||||
|
||||
<para>
|
||||
The Romans had a particular set of numerals and had names for each of their
|
||||
numbers. In this section are listed some numbers and their corresponding
|
||||
symbol.
|
||||
</para>
|
||||
<table frame="none">
|
||||
<title>Numbers</title>
|
||||
<!-- translators: don't translate the following -->
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>1</entry>
|
||||
<entry>I</entry>
|
||||
<entry>unus</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>2</entry>
|
||||
<entry>II</entry>
|
||||
<entry>duo</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>3</entry>
|
||||
<entry>III</entry>
|
||||
<entry>tres</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>4</entry>
|
||||
<entry>IV</entry>
|
||||
<entry>quattuor</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>5</entry>
|
||||
<entry>V</entry>
|
||||
<entry>quinque</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>6</entry>
|
||||
<entry>VI</entry>
|
||||
<entry>sex</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>7</entry>
|
||||
<entry>VII</entry>
|
||||
<entry>septem</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>8</entry>
|
||||
<entry>VIII</entry>
|
||||
<entry>octo</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>9</entry>
|
||||
<entry>IX</entry>
|
||||
<entry>novem</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>10</entry>
|
||||
<entry>X</entry>
|
||||
<entry>decem</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>11</entry>
|
||||
<entry>XI</entry>
|
||||
<entry>undecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>12</entry>
|
||||
<entry>XII</entry>
|
||||
<entry>duodecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>13</entry>
|
||||
<entry>XIII</entry>
|
||||
<entry>tredecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>14</entry>
|
||||
<entry>XIV</entry>
|
||||
<entry>quattuordecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>15</entry>
|
||||
<entry>XV</entry>
|
||||
<entry>quindecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>16</entry>
|
||||
<entry>XVI</entry>
|
||||
<entry>sedecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>17</entry>
|
||||
<entry>XVII</entry>
|
||||
<entry>septendecim</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>18</entry>
|
||||
<entry>XVIII</entry>
|
||||
<entry>duodeviginti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>19</entry>
|
||||
<entry>XIX</entry>
|
||||
<entry>undeviginti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>20</entry>
|
||||
<entry>XX</entry>
|
||||
<entry>viginti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>21</entry>
|
||||
<entry>XXI</entry>
|
||||
<entry>vigintiunus</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>22</entry>
|
||||
<entry>XXII</entry>
|
||||
<entry>vigintiduo</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>30</entry>
|
||||
<entry>XXX</entry>
|
||||
<entry>triginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>40</entry>
|
||||
<entry>XL</entry>
|
||||
<entry>quadraginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>50</entry>
|
||||
<entry>L</entry>
|
||||
<entry>quinquaginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>60</entry>
|
||||
<entry>LX</entry>
|
||||
<entry>sexaginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>70</entry>
|
||||
<entry>LXX</entry>
|
||||
<entry>septuaginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>80</entry>
|
||||
<entry>LXXX</entry>
|
||||
<entry>octoginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>90</entry>
|
||||
<entry>XC</entry>
|
||||
<entry>nonaginta</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>100</entry>
|
||||
<entry>C</entry>
|
||||
<entry>centum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>200</entry>
|
||||
<entry>CC</entry>
|
||||
<entry>ducenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>300</entry>
|
||||
<entry>CCC</entry>
|
||||
<entry>trecenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>400</entry>
|
||||
<entry>CD</entry>
|
||||
<entry>quadrigenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>500</entry>
|
||||
<entry>D</entry>
|
||||
<entry>quingenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>600</entry>
|
||||
<entry>DC</entry>
|
||||
<entry>sescenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>700</entry>
|
||||
<entry>DCC</entry>
|
||||
<entry>septigenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>800</entry>
|
||||
<entry>DCCC</entry>
|
||||
<entry>octigenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>900</entry>
|
||||
<entry>CM</entry>
|
||||
<entry>nongenti</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>1000</entry>
|
||||
<entry>M</entry>
|
||||
<entry>mille</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>2000</entry>
|
||||
<entry>MM</entry>
|
||||
<entry>duo milia</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
</sect1>
|
||||
@ -0,0 +1,331 @@
|
||||
<!-- Please translate the following -->
|
||||
<sect1 id="pronouns">
|
||||
<title> KLatin Notes - Pronouns </title>
|
||||
<para>Here are some pronouns.
|
||||
</para>
|
||||
|
||||
<table frame="none">
|
||||
<title>Personal Pronouns</title>
|
||||
<!-- Please don't translate the following until next title -->
|
||||
<tgroup cols="2" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<!-- Translate the following two entries -->
|
||||
<row>
|
||||
<entry><emphasis>Me</emphasis></entry>
|
||||
<entry><emphasis>You</emphasis></entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>ego</entry>
|
||||
<entry>tu</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>me</entry>
|
||||
<entry>te</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>mei</entry>
|
||||
<entry>tui</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>mihi</entry>
|
||||
<entry>tibi</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>me</entry>
|
||||
<entry>te</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<!-- Translate the following two entries -->
|
||||
<row>
|
||||
<entry><emphasis>We</emphasis></entry>
|
||||
<entry><emphasis>You (Pl)</emphasis></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nos</entry>
|
||||
<entry>vos</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nos</entry>
|
||||
<entry>vos</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nostri/nostrum</entry>
|
||||
<entry>vestri/vestrum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nobis</entry>
|
||||
<entry>vobis</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nobis</entry>
|
||||
<entry>vobis</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
<para>
|
||||
</para>
|
||||
<table frame="none">
|
||||
<!-- Please translate title-->
|
||||
<title>3rd Person Personal Pronouns</title>
|
||||
<!-- Please don't translate the following until next title-->
|
||||
<tgroup cols="4" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<!-- Translate the following entry -->
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry><emphasis>He,</emphasis></entry>
|
||||
<entry><emphasis>She,</emphasis></entry>
|
||||
<entry><emphasis>It</emphasis></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>is</entry>
|
||||
<entry>ea</entry>
|
||||
<entry>id</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eum</entry>
|
||||
<entry>eum</entry>
|
||||
<entry>id</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eius</entry>
|
||||
<entry>eius</entry>
|
||||
<entry>eius</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>ei</entry>
|
||||
<entry>ei</entry>
|
||||
<entry>ei</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eo</entry>
|
||||
<entry>ea</entry>
|
||||
<entry>eo</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>PLURAL</entry>
|
||||
<entry>ei</entry>
|
||||
<entry>eae</entry>
|
||||
<entry>ea</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eos</entry>
|
||||
<entry>eas</entry>
|
||||
<entry>ea</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eorum</entry>
|
||||
<entry>earum</entry>
|
||||
<entry>eorum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eis</entry>
|
||||
<entry>eis</entry>
|
||||
<entry>eis</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>eis</entry>
|
||||
<entry>eis</entry>
|
||||
<entry>eis</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
<para>
|
||||
</para>
|
||||
<table frame="none">
|
||||
<!-- Please translate the title-->
|
||||
<title>Demonstrative Pronouns</title>
|
||||
<!-- Please don't translate the following -->
|
||||
<tgroup cols="4" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<!-- Translate the following entry -->
|
||||
<row>
|
||||
<entry><emphasis>This</emphasis></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>hic</entry>
|
||||
<entry>haec</entry>
|
||||
<entry>hoc</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>hunc</entry>
|
||||
<entry>hanc</entry>
|
||||
<entry>hoc</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>huius</entry>
|
||||
<entry>huius</entry>
|
||||
<entry>huius</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>huic</entry>
|
||||
<entry>huic</entry>
|
||||
<entry>huic</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>hoc</entry>
|
||||
<entry>hac</entry>
|
||||
<entry>hoc</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>PLURAL</entry>
|
||||
<entry>hi</entry>
|
||||
<entry>hae</entry>
|
||||
<entry>haec</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>hos</entry>
|
||||
<entry>has</entry>
|
||||
<entry>heac</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>horum</entry>
|
||||
<entry>harum</entry>
|
||||
<entry>horum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>his</entry>
|
||||
<entry>his</entry>
|
||||
<entry>his</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>his</entry>
|
||||
<entry>his</entry>
|
||||
<entry>his</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
<!-- Translate the following entry -->
|
||||
<row>
|
||||
<entry><emphasis>That</emphasis></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>SINGULAR</entry>
|
||||
<entry>ille</entry>
|
||||
<entry>illa</entry>
|
||||
<entry>illud</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illum</entry>
|
||||
<entry>illam</entry>
|
||||
<entry>illud</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illius</entry>
|
||||
<entry>illius</entry>
|
||||
<entry>illius</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illi</entry>
|
||||
<entry>illi</entry>
|
||||
<entry>illi</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illo</entry>
|
||||
<entry>illa</entry>
|
||||
<entry>illo</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>PLURAL</entry>
|
||||
<entry>illi</entry>
|
||||
<entry>illae</entry>
|
||||
<entry>illa</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illos</entry>
|
||||
<entry>illas</entry>
|
||||
<entry>illa</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illorum</entry>
|
||||
<entry>illarum</entry>
|
||||
<entry>illorum</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illis</entry>
|
||||
<entry>illis</entry>
|
||||
<entry>illis</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry></entry>
|
||||
<entry>illis</entry>
|
||||
<entry>illis</entry>
|
||||
<entry>illis</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table frame="none">
|
||||
<title>Negative Pronouns</title>
|
||||
<!-- Please don't translate the following until next title -->
|
||||
<tgroup cols="2" colsep="1" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<!-- Translate the following two entries -->
|
||||
<row>
|
||||
<entry><emphasis>Noone</emphasis></entry>
|
||||
<entry><emphasis>Nothing</emphasis></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nemo</entry>
|
||||
<entry>nihil</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>neminem</entry>
|
||||
<entry>nihil/nil</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nullius/neminis</entry>
|
||||
<entry>nullius rei</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nemini/nulli</entry>
|
||||
<entry>nulli rei</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>nullo/nemine</entry>
|
||||
<entry>nulla re</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 23 KiB |
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
@ -0,0 +1,756 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&klettres;"><!-- replace klettres here -->
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &klettres; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Anne-Marie</firstname>
|
||||
<surname>Mahfouf</surname>
|
||||
<affiliation>
|
||||
<address>&Anne-Marie.Mahfouf.mail;</address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001</year><year>2006</year>
|
||||
<holder>&Anne-Marie.Mahfouf;</holder>
|
||||
</copyright>
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2006-02-08</date>
|
||||
<releaseinfo>1.5</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&klettres; is an application specially designed to do help the user
|
||||
to learn alphabet in a new language and then to learn to read simple syllables.
|
||||
The user can be a young child aged from two and a half or an adult that wants to learn
|
||||
the basics of a foreign language. </para>
|
||||
<para>
|
||||
Eleven languages are available at the moment: Czech, Danish, Dutch, English,
|
||||
French, Italian, Luganda, Romanized Hindi, Spanish, Slovak and German but only
|
||||
English, French and your language if it is among those are installed by default.
|
||||
</para>
|
||||
<para>
|
||||
&klettres; is really easy to use. The language can be changed using the
|
||||
<guimenu>Language</guimenu> menu. The user can also choose the Level from
|
||||
1 to 4 in a combo box in the toolbar or via the <guimenu>Level</guimenu>
|
||||
menu. <guimenuitem>Themes</guimenuitem> (background and font color) can be
|
||||
changed in a combo box or in the <menuchoice><guimenu>Look</guimenu>
|
||||
<guimenuitem>Themes</guimenuitem></menuchoice> menu. Three themes are
|
||||
available: <guimenuitem>Classroom</guimenuitem>,
|
||||
<guimenuitem>Arctic</guimenuitem> and <guimenuitem>Desert</guimenuitem>.
|
||||
Finally, the mode can be changed from kid to grown-up using the
|
||||
<menuchoice><guimenu>Look</guimenu> <guimenuitem>Mode</guimenuitem></menuchoice> menu.
|
||||
</para>
|
||||
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>klettres</keyword>
|
||||
<keyword>alphabet</keyword>
|
||||
<keyword>Czech</keyword>
|
||||
<keyword>Danish</keyword>
|
||||
<keyword>Dutch</keyword>
|
||||
<keyword>English</keyword>
|
||||
<keyword>French</keyword>
|
||||
<keyword>Italian</keyword>
|
||||
<keyword>Romanized Hindi</keyword>
|
||||
<keyword>Spanish</keyword>
|
||||
<keyword>Slovak</keyword>
|
||||
<keyword>Luganda</keyword>
|
||||
<keyword>language</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>&klettres; is a very simple application that helps a child or an
|
||||
adult to learn the alphabet and some simple sounds in his own language
|
||||
or in another language. The program picks up a letter or a syllable
|
||||
in random, this letter/syllable is displayed and the sound is played.
|
||||
The user should then type this letter or syllable. Training is done in
|
||||
the levels where the letter/syllable is not displayed, only the sound
|
||||
is played. The user does not need to know how to use the mouse, the
|
||||
keyboard only is needed.</para>
|
||||
|
||||
<para>There are eleven languages available at the moment: Czech, Danish, Dutch,
|
||||
English, French, Italian, Luganda, Romanized Hindi, Spanish, Slovak and German. If your
|
||||
&kde; language is Czech, Danish, Dutch, English, French, Italian, Luganda, Romanized Hindi, Spanish,
|
||||
Slovak or German, then your language is taken as default, otherwise French is the default.
|
||||
You can easily get any additional available language by using the
|
||||
<guimenu>File</guimenu> menu and <guimenuitem>Get Alphabet in New
|
||||
Language...</guimenuitem> menu item, provided that your computer is connected to
|
||||
the Internet.</para>
|
||||
|
||||
<note><para>&klettres; needs &arts; running for the sound</para></note>
|
||||
|
||||
<para>Two different modes allow you to adapt &klettres; to
|
||||
your need and have the full usual interface or a stripped interface. For a
|
||||
child, the menubar is no longer
|
||||
visible. We assume that a child will not want to set the language
|
||||
himself. A combo box allows him to choose the different levels. For an
|
||||
older user, the background is not so childish and the menubar is
|
||||
present in the Grown-Up style. Three different themes
|
||||
(<guimenuitem>Classroom</guimenuitem>,
|
||||
<guimenuitem>Arctic</guimenuitem> and
|
||||
<guimenuitem>Desert</guimenuitem>) set up a different background with
|
||||
different fonts.</para>
|
||||
|
||||
<note>
|
||||
<para>You do not need the language keyboard layout anymore as you can use the
|
||||
special <guimenuitem>Characters</guimenuitem> toolbar to type any special
|
||||
character in each language. In the <guimenu>Settings</guimenu> menu,
|
||||
<guimenuitem>Toolbars</guimenuitem>, select <guimenuitem>Characters</guimenuitem>
|
||||
and the toolbar will appear at the bottom of &klettres;. Click on the letter
|
||||
you want and it will be shown in the input field. This toolbar can be dragged
|
||||
anywhere on your screen.</para>
|
||||
<para>
|
||||
If you prefer having the language keyboard layout, please use &kcontrolcenter;, in the
|
||||
section <guimenu>Regional & Accessibility</guimenu> and submenu
|
||||
<guimenuitem>Keyboard Layout</guimenuitem> in order to set the correct keyboard layout.</para>
|
||||
</note>
|
||||
</chapter>
|
||||
|
||||
<chapter id="using-klettres">
|
||||
<title>Using &klettres;</title>
|
||||
<para>&klettres; has 4 levels. Levels 1 and 2 deal with the alphabet and
|
||||
levels 3 and 4 concern syllables. For a very young child (2 1/2 to 4), I would
|
||||
suggest that he/she is sitting on your lap in front of the computer and
|
||||
that you do the game together.</para>
|
||||
|
||||
<sect1 id="levels1-and2">
|
||||
<title>Levels 1 and 2</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Level 1</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klettres; level1</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Level is Level 1, language is French, theme is desert
|
||||
and mode is <emphasis>grown-up</emphasis>.</para>
|
||||
<note>
|
||||
<para>
|
||||
If your &kde; language is set to Czech, Danish, Dutch, English, French, Italian,
|
||||
Luganda, Romanized Hindi, Spanish, Slovak or German, then this will be the default
|
||||
language the first time you run &klettres;. For other languages, French is the default.
|
||||
&klettres; comes with French and your default language if among those listed above
|
||||
and you can get additional languages via <guimenu>File</guimenu> <guimenuitem>Get Alphabet
|
||||
in New Language...</guimenuitem> provided you have an Internet connection.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
In level 1, the user sees the letter and hears the sound. He then has to type in
|
||||
the letter in the box. If it is correct, the next letter appears (without having
|
||||
to press <keycap>Enter</keycap> or whatever). If the user types the wrong letter,
|
||||
he hears the sound again. In this level, the user memorizes the letters, associates
|
||||
them with their sound and recognizes them on the keyboard.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>The user can type in either lower or uppercase letters. The letters are
|
||||
automatically put in uppercase so that a child will match them with the keyboard.
|
||||
He can type only one letter at atime.</para>
|
||||
<para>When you type a letter in the input field, there is no need to press
|
||||
<keycap>Enter</keycap> and the program waits for a short while before testing if
|
||||
the letter is right. This short wait is to leave time to a young child to understand
|
||||
what he/she just typed, especially if this is the wrong letter. You can change this
|
||||
time by using the <guimenu>Settings</guimenu> menu, <guimenuitem>Configure &klettres;...</guimenuitem>
|
||||
and the <guilabel>Timer</guilabel> page which will bring you a dialog where you can
|
||||
set two different times: one for the <guilabel>Kid Mode</guilabel> and one for the
|
||||
<guilabel>Grown-up Mode</guilabel>.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<para>
|
||||
After the first time, the language setting is saved in a configuration file
|
||||
on closing of &klettres; and loaded the next time, with the level you were in.
|
||||
</para>
|
||||
<para>The mode (kid or grown-up) is saved in the config file and therefore
|
||||
is kept until you change.</para>
|
||||
<para>The letters appear in random order. They are not the same consecutively. </para>
|
||||
|
||||
<para>
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Level 2</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klettres; level2</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>Here is a screenshot of Level 2 with the <emphasis>kid</emphasis> mode, <emphasis>classroom</emphasis> theme and Danish language.</para>
|
||||
|
||||
<para>Clicking in the <guilabel>Level</guilabel> combo-box and choosing <guilabel>Level
|
||||
2</guilabel> or using the <guimenu>Level</guimenu> menu brings you to level 2. In that level, the user only
|
||||
hears the sound of the letter and has to type in the letter. If he
|
||||
is wrong, the letter appears to help him. </para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="levels3-and4">
|
||||
<title>Levels 3 and 4</title>
|
||||
|
||||
<para>
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Level 3</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres3.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klettres; level3</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>Here you can see &klettres; level 3, <emphasis>grown-up</emphasis> mode, <emphasis>arctic</emphasis> theme and Czech language.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In level 3, the user sees the syllable and hears the sound. He then
|
||||
has to type in the letters in the box. If the first letter of the
|
||||
sound is wrong, the user cannot type in the second one. The letter
|
||||
disappears and he has to try again. The number of letters is two or
|
||||
three, it depends of the language.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Level 4</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres4.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klettres; level4</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Here you can see &klettres; level 4, <emphasis>kid</emphasis> mode, <emphasis>desert</emphasis> theme and Slovak language.
|
||||
</para>
|
||||
|
||||
<para>The sounds appear in random order. </para> <para>Clicking in the
|
||||
<guilabel>Level</guilabel> combo-box or using the <guimenu>Level</guimenu> menu in the menubar
|
||||
and choosing <guilabel>Level 4</guilabel> brings you
|
||||
to level 4. In that level, the user only hears the sound of the
|
||||
syllable and has to type in the letters. This level is quite difficult
|
||||
for a young child. </para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id ="configuring">
|
||||
<title>Configuration dialog</title>
|
||||
<para>The configuration dialog has two pages: one for <guilabel>Font Settings</guilabel>
|
||||
and one for the <guilabel>Timer</guilabel>.</para>
|
||||
|
||||
<sect2 id="about-font">
|
||||
<title>About fonts</title>
|
||||
|
||||
<para>
|
||||
You can easily change the font that displays the letters. In some distribution, the default font used from the system is really ugly. In grown-up mode, in the <guimenu>Settings</guimenu> menu, in <guimenuitem>Configure &klettres;...</guimenuitem> you will find a <guilabel>Font Settings</guilabel> page with a font chooser dialog. The new font will be applied to both the displayed letter/syllable and the user field.
|
||||
</para>
|
||||
|
||||
<warning>
|
||||
<para>
|
||||
Changing font is also nice as some fonts (Helvetica for example) do not display correctly East-European languages as Czech and Slovak. If some letters or syllables are not displayed, please change the font and choose Arial for example.
|
||||
</para>
|
||||
</warning>
|
||||
|
||||
<para>
|
||||
You can also choose here the size you like the best. This size will be kept in configuration.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Font Chooser Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres5.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&klettres; Font Chooser Dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Here you can see &klettres; Font Chooser Dialog.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="timers">
|
||||
<title>Timers</title>
|
||||
|
||||
<para>The timers set the time between two letters &ie; the time during wich a letter is displayed. The units are tenths of seconds.
|
||||
</para>
|
||||
|
||||
<para>The <guilabel>Timer</guilabel> page in the <menuchoice><guimenu>Settings</guimenu> <guimenuitem>Configure &klettres;...</guimenuitem></menuchoice> dialog has two timers settings: one for the <guilabel>Kid Mode</guilabel> and one for the <guilabel>Grown-up Mode</guilabel>. Defaults are 4 tenths of seconds for <guilabel>Kid Mode</guilabel> and 2 tenths of seconds for <guilabel>Grown-up Mode</guilabel>. Increasing the time leaves you more time to see your errors.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Screenshot of &klettres; Timers Settings</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="klettres6.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Screenshot of &klettres; Timers Settings</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="klettres-mainwindow">
|
||||
<title>The Main &klettres; Window</title>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New Sound</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Play</action> a new sound</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>P</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Replay Sound</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Play</action> the same sound again</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Get Alphabet in New Language...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens</action> the <guilabel>Get Hot New Stuff</guilabel> dialog for &klettres; to download a new language</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quits</action> &klettres;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Level</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Level 1</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the level 1 (letter displayed and sound)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Level 2</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the level 2 (no letter displayed, sound only)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Level 3</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the level 3 (syllable displayed and sound)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Level</guimenu>
|
||||
<guimenuitem>Level 4</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the level 4 (no syllable displayed, sound only)</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>The <guimenu>Language</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Language</guimenu>
|
||||
<guimenuitem>English</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the English language</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Language</guimenu>
|
||||
<guimenuitem>French</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the French language</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Look</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Look</guimenu>
|
||||
<guisubmenu>Theme</guisubmenu>
|
||||
<guimenuitem>Classroom</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Switch</action> to the classroom theme</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Look</guimenu>
|
||||
<guisubmenu>Theme</guisubmenu>
|
||||
<guimenuitem>Arctic</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Switch</action> to the arctic theme</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Look</guimenu>
|
||||
<guisubmenu>Theme</guisubmenu>
|
||||
<guimenuitem>Desert</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Switch</action> to the desert theme</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>K</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Look</guimenu>
|
||||
<guimenuitem>Mode Kid</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the kid mode: no menubar</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>G</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Look</guimenu>
|
||||
<guimenuitem>Mode Grownup</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the grown-up mode: normal interface</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>M</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show Menubar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the menubar</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Toolbars</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the <guimenuitem>Main</guimenuitem> and the
|
||||
<guimenuitem>Characters</guimenuitem> toolbar</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> &klettres; shortcuts</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> &klettres; toolbars</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &klettres;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> &klettres;: display a dialog with the <guilabel>Font
|
||||
Settings</guilabel> page and the <guilabel>Timer</guilabel> configuration page.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="sounds">
|
||||
<title>Adding Sounds to &klettres;</title>
|
||||
|
||||
<para>
|
||||
If you would like to add sounds in your own language, it is very easy to do so. Record the alphabet sounds and place them in a folder named 'alpha'. Then record the most current syllables and put them in a folder named 'syllab'.</para>
|
||||
<para>Create a text file <filename>sounds.xml</filename>, preferably using &kate; as editor or another editor capable of different encoding. In this file, write all the alphabet sounds and syllable sounds you recorded, like this example for the czech language:</para>
|
||||
<programlisting><klettres>
|
||||
<language code="cs">
|
||||
<menuitem>
|
||||
<label>&Czech</label>
|
||||
</menuitem>
|
||||
<alphabet>
|
||||
<sound name="A" file="cs/alpha/a.ogg" />
|
||||
...
|
||||
</alphabet>
|
||||
<syllables>
|
||||
<sound name="BA" file="cs/syllab/ba.ogg" />
|
||||
...
|
||||
</syllables>
|
||||
</language>
|
||||
</klettres></programlisting>
|
||||
<para>Replace "cs" with the two letter code and "Czech" with the name of your language. Write the sound names with the special characters of your language in uppercase in utf8.</para>
|
||||
|
||||
<para>Additionally you can tell me about special letters in your language so I can easily generate the special <guimenuitem>Characters</guimenuitem> toolbar. Create a text file <filename>cs.txt</filename> (replace "cs" with the two letter code of your language) with each special character of your language in uppercase on one line.
|
||||
And save both text files with <quote>utf8</quote> encoding (upper right dropbox in &kate; allows that)</para>
|
||||
|
||||
<para>The sounds should be in wav or ogg format and long enough for KAudioPlayer to play them (between 1.5 and 2 seconds long, please add some silence if they are too short). Then make a tarball of all that and send it to me.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
See the <ulink url="http://edu.kde.org/klettres/add_language.php">&klettres; website</ulink> for more up to date instructions on how to add a new language.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<qandaset id="faqlist">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The background picture does not appear.</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>You need to configure with the <option>--prefix</option> option
|
||||
set to your &kde; folder or to add this folder to your
|
||||
path.</para> </answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I do not hear any sounds</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>You need to have &arts; support and the &arts; daemon needs to be running.
|
||||
Make sure you compiled kdelibs with &arts; if you compiled &kde;. In any doubt,
|
||||
ask your distribution. You can also check if &arts; is running in
|
||||
&kcontrolcenter; -> <guilabel>Sound & Multimedia</guilabel> in the <guilabel>Sound
|
||||
System</guilabel> tab. There you must make sure that <guilabel>Enable the sound
|
||||
system</guilabel> is checked.</para>
|
||||
<para>For &kde; 3.4 users, you must also be sure that the player used to play
|
||||
&kde; sounds is the default &kde; sound system player. See in &kcontrolcenter;
|
||||
-> <guilabel>Sound & Multimedia</guilabel>
|
||||
the <guilabel>System Notifications</guilabel> tab, click on the <guibutton>Player Settings</guibutton>
|
||||
button on the bottom right and in the dialog please check <guilabel>Use the
|
||||
&kde; sound system</guilabel>.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I do not see some letters on the icons on the special <guimenuitem>Characters</guimenuitem> toolbar. I see rectangles instead for some languages.</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>&klettres; in Czech and Slovak needs Arial and if you do not have this font installed, please ask your distribution support how to install it.</para>
|
||||
<para>If you have &Windows; on your machine, you can use the TTF fonts from
|
||||
&Windows; (Arial is in those) via &kcontrolcenter; -> <guilabel>System
|
||||
Administration</guilabel> -> <guilabel>Font Installer</guilabel> (click on
|
||||
<guibutton>Administrator Mode</guibutton> and add the &Windows; Font
|
||||
folder).</para></answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The letters on the icons on the special <guimenuitem>Characters</guimenuitem> toolbar are too small for some languages.</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>&klettres; in Czech and Slovak needs Arial and if you do not have this font installed, please ask your distribution support how to install it.</para>
|
||||
<para>If you have &Windows; on your machine, you can use the TTF fonts from
|
||||
&Windows; (Arial is in those) via &kcontrolcenter; -> <guilabel>System
|
||||
Administration</guilabel> -> <guilabel>Font Installer</guilabel> (click on
|
||||
<guilabel>Administrator mode</guilabel> and add the &Windows; Font
|
||||
folder).</para></answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why are there only ten languages?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>In order for me to add a new language, I need the sounds
|
||||
for the alphabet and some basic syllables. Someone speaking natively
|
||||
the new language must record these sounds in wav, mp3 or preferably, ogg format. For levels 3
|
||||
and 4, the syllables must be chosen by a teacher or someone who knows how children learn: these must be the
|
||||
syllables you have to learn just after the alphabet in order to learn
|
||||
well the basics of this language. Please send me a mail if you are
|
||||
able to do that. See <ulink url="http://edu.kde.org/klettres/add_language.php">the &klettres; website</ulink> for detailed instructions on how to add a new language.</para> </answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&klettres;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2001-2005 &Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail;
|
||||
</para>
|
||||
<para>
|
||||
I am very grateful to the following people whose contribution has been greatly valuable:
|
||||
<itemizedlist>
|
||||
<listitem><para>Czech sounds: Eva Mikulčíková
|
||||
<email>evmi@seznam.cz</email></para> </listitem>
|
||||
<listitem><para>Dutch sounds: Geert Stams
|
||||
<email>geert@pa3csg.myweb.nl</email></para> </listitem>
|
||||
<listitem><para>Danish sounds: Erik Kjaer Pedersen
|
||||
<email>erik@binghamton.edu</email></para> </listitem>
|
||||
<listitem><para>French sounds: Ludovic Grossard
|
||||
<email>grossard@kde.org</email></para></listitem>
|
||||
<listitem><para>Slovak sounds: Silvia Motyčková and Jozef Říha
|
||||
<email>silviamotycka@seznam.cz</email></para></listitem>
|
||||
<listitem><para>Italian sounds: Pietro Pasotti
|
||||
<email>pietro@itopen.it</email></para></listitem>
|
||||
<listitem><para>English sounds: Robert Wadley
|
||||
<email>robntina@juno.com</email></para></listitem>
|
||||
<listitem><para>Spanish sounds: Ana Belén Caballero and Juan Pedro Paredes
|
||||
<email>neneta @iquis.com</email></para></listitem>
|
||||
<listitem><para>Romanized Hindi sounds: Vikas Kharat
|
||||
<email>kharat@sancharnet.in</email></para></listitem>
|
||||
<listitem><para>Luganda sounds: John Magoye and Cormac Lynch
|
||||
<email>cormaclynch@eircom.net</email></para></listitem>
|
||||
<listitem><para>German sounds: Helmut Kriege
|
||||
<email>h.kriege@freenet.de</email></para></listitem>
|
||||
<listitem><para>Classroom background picture: Renaud Blanchard
|
||||
<email>kisukuma@chez.com</email></para> </listitem>
|
||||
<listitem><para>Original icons: &Primoz.Anzur;
|
||||
<email>zerokode@yahoo.com</email></para></listitem>
|
||||
<listitem><para>Support and coding guidance: &Robert.Gogolok;
|
||||
<email>&Robert.Gogolok.mail;</email></para></listitem>
|
||||
<listitem><para>SVG icon: Chris Luetchford
|
||||
<email>chris@os11.com</email></para></listitem>
|
||||
<listitem><para>Code for generating special characters icons: Peter Hedlund
|
||||
<email>peter@peterandlinda.com</email></para></listitem>
|
||||
<listitem><para>Port to KConfig XT, coding help: &Waldo.Bastian;
|
||||
<email>&Waldo.Bastian.mail;</email></para></listitem>
|
||||
<listitem><para>Kids and grownup SVG icons, desert theme: &Danny.Allen;
|
||||
<email>dannya40uk@yahoo.co.uk</email></para></listitem>
|
||||
<listitem><para>Timer setting widget: Michael Goettsche
|
||||
<email>michael.goettsche@kdemail.net</email></para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2001-2006
|
||||
&Anne-Marie.Mahfouf;<email>&Anne-Marie.Mahfouf.mail;</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL; <!-- FDL: do not remove. Commercial development should
|
||||
-->
|
||||
|
||||
&underGPL; <!-- GPL License -->
|
||||
</chapter>
|
||||
|
||||
<!-- <appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 164 KiB |
|
After Width: | Height: | Size: 164 KiB |
|
After Width: | Height: | Size: 64 KiB |
|
After Width: | Height: | Size: 169 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 12 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
@ -0,0 +1,471 @@
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="a-file-menu">
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem>
|
||||
<para><action>Starts a new Plot by clearing the coordinate system
|
||||
and resetting the function parser.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice><shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo></shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open...</guimenuitem></menuchoice></term>
|
||||
<listitem><para><action>Opens an existing document.</action>
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Recent</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Displays a list of recently opened files.</action>
|
||||
Selecting one from this list plots the functions in the file.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut><keycombo
|
||||
action="simul">&Ctrl;<keycap>S</keycap></keycombo></shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save</guimenuitem></menuchoice></term>
|
||||
<listitem><para><action>Saves the document.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save As...</guimenuitem></menuchoice></term>
|
||||
<listitem><para><action>Saves the document under another
|
||||
name.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>P</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Print...</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem>
|
||||
<para><action>Sends the plot to a printer or file.</action></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Export...</guimenuitem></menuchoice></term>
|
||||
<listitem><para><action>Export values to a textfile.
|
||||
</action>Every value in the parameter list will be
|
||||
written to one line in the file.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut><keycombo action="simul">
|
||||
&Ctrl;<keycap>Q</keycap>
|
||||
</keycombo></shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem></menuchoice></term>
|
||||
<listitem><para><action>Exits</action> &kmplot;.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-view-menu">
|
||||
<title>The <guimenu>Edit</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Colors...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>
|
||||
Displays the <guilabel>Colors</guilabel> Settings dialog box. See
|
||||
<xref linkend="colors-config"/>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Coordinate System...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Displays the <guilabel>Coordinate System</guilabel> dialog box. See <xref linkend="coords-config"/>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Scaling...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Displays the <guilabel>Scale</guilabel> Settings dialog box. See
|
||||
<xref linkend="scaling-config"/>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Fonts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Displays the <guilabel>Fonts</guilabel> Settings dialog box. See
|
||||
<xref linkend="font-config"/>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Coordinate System I</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Show both positive and negative x- and y-values on the grid.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Coordinate System II</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Show positive and negative y-values, but positive x-values only
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Edit</guimenu><guimenuitem>Coordinate System III</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Show only positive x- and y-values.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-functions-menu">
|
||||
<title>The <guimenu>Plot</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>Plot</guimenu>
|
||||
<guimenuitem>New Function Plot...</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Opens the dialog for creating a new function plot. See <xref
|
||||
linkend="using-kmplot"/>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>Plot</guimenu>
|
||||
<guimenuitem>New Parametric Plot...</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Opens the dialog for creating a new parametric plot. See <xref
|
||||
linkend="using-kmplot"/>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>Plot</guimenu>
|
||||
<guimenuitem>New Polar Plot...</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Opens the dialog for creating a new polar plot. See <xref
|
||||
linkend="using-kmplot"/>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>Plot</guimenu>
|
||||
<guimenuitem>Edit Plots...</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Displays the functions dialog. There you can add, edit and remove functions. See <xref
|
||||
linkend="using-kmplot"/>.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-zoom-menu">
|
||||
<title>The <guimenu>Zoom</guimenu> Menu</title>
|
||||
<para>The first five items in the menu change zoom-mode.</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>0</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>No Zoom</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Disable the zoom-mode.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>1</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>Zoom Rectangular</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>Let the user draw a rectangle. The minimum and maximum values will be set to the coordinates of the rectangle.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>2</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>Zoom In</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>The minimum and maximum values will come closer to each other and the selected point in the graph will be centered.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>3</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>Zoom Out</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>The minimum and maximum values will be more separated from each other and the selected point in the graph will be centered.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>4</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>Center Point</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>The selected point in the graph will be centered.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<menuchoice>
|
||||
<guimenu>Zoom</guimenu>
|
||||
<guimenuitem>Fit Widget to Trigonometric Functions</guimenuitem>
|
||||
</menuchoice>
|
||||
</term>
|
||||
<listitem><para>The scale will be adapted to trigonometric functions. This works both for radians and degrees.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-tools-menu">
|
||||
<title>The <guimenu>Tools</guimenu> Menu</title>
|
||||
|
||||
<para>This menu contains some tools for the functions that can be useful:</para>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Tools</guimenu>
|
||||
<guimenuitem>Get y-Value...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Let the user get the y-value from a specific x-value. At the moment, only plot functions are supported. Type a value or expression in the text box under "X:". In the list below all the available functions are shown. Press the "Calculate" button to find the function's y-value. The result will be shown in the y-value box.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Tools</guimenu>
|
||||
<guimenuitem>Search for Minimum Value...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Find the minimum value of the graph in a specified range.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Tools</guimenu>
|
||||
<guimenuitem>Search for Maximum Value...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Find the maximum value of the graph in a specified range.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Tools</guimenu>
|
||||
<guimenuitem>Calculate Integral</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Select a graph and the x-values in the new dialog that appears.
|
||||
Calulates the integral and draws the area between the graph and the x-axis in the
|
||||
range of the selected x-values in the color of the graph.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-settings-menu">
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show/Hide Toolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Toggle on and off the display of the toolbar.</action>
|
||||
The default is on.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show/Hide Statusbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Toggle on and off the display of the status bar at the bottom of
|
||||
the &kmplot; main window.</action>
|
||||
The default is on.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- Is the settings menu the right place for Full Screen Mode, same for Show Sliders ?
|
||||
perhaps better a new menu View with Full Screen, Sliders, and Coordinate System I to III
|
||||
from the menu Edit, usability bugreport against kmplot?
|
||||
-->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;&Shift;<keycap>F</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Full Screen Mode</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>With this action you toggle the full screen mode.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show Sliders</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Toogles</action> the display of sliders 1 to 4 on and off.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Personalize the keybindings</action> for &kmplot;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Personalize the toolbars</action> for &kmplot;.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &kmplot;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para><action>Customize</action> &kmplot;. The options available to
|
||||
you are described in <xref linkend="configuration"/>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="a-help-menu">
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
|
||||
<para>&kmplot; has a standard &kde; <guimenu>Help</guimenu> as described
|
||||
below, with one addition:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenu>Help</guimenu>
|
||||
<guimenuitem>Predefined Math Functions...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Opens a window with a list of the predefined function names and constants
|
||||
that &kmplot; knows.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>The standard &kde; <guimenu>Help</guimenu> entries are:</para>
|
||||
|
||||
&help.menu.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
</chapter>
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
@ -0,0 +1,237 @@
|
||||
<chapter id="configuration">
|
||||
<title>Configuring &kmplot;</title>
|
||||
<para>To access the &kmplot; configuration
|
||||
dialog, select <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure
|
||||
&kmplot;...</guimenuitem></menuchoice>. A number of settings (<guimenuitem>Colors...</guimenuitem>,
|
||||
<guimenuitem>Coordinate System...</guimenuitem>, <guimenuitem>Scaling...</guimenuitem> and
|
||||
<guimenuitem>Fonts...</guimenuitem>) can only be changed
|
||||
from the <guimenu>Edit</guimenu> menu. </para>
|
||||
|
||||
<sect1 id="general-config">
|
||||
<title><guilabel>General</guilabel> Configuration</title>
|
||||
<para>Here you can set global settings which automatic will be saved when you exit &kmplot;. In the first page you can set calculation-precision, angle-mode (radians and degrees), background color and zoom in and zoom out factors. </para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>screenshot of the &kmplot; settings dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settingsdlg.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>screenshot of the &kmplot; settings dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The second page let you define you own constants. &kmplot; saves the constants in the same file as &kcalc; does. That means you can create a constant in &kmplot;, close the program and load it in &kcalc; and vice versa. &kmplot; only supports constant names that consist of one capital character and if you in &kcalc; define a constant name that is not one character, the name will be truncated. E.g, if you already have the constants "apple" and "bananas" in &kcalc;, they will be renamed to "A" and "B" in &kmplot;.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="colors-config">
|
||||
<title><guilabel>Colors</guilabel> Configuration</title>
|
||||
<para>In the <guilabel>Coords</guilabel> tab of the <guilabel>Colors</guilabel>
|
||||
configuration dialog, you can change the colors of the axes and grid of the
|
||||
main &kmplot; area.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>screenshot of the colors configuration dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings-colors.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>screenshot of the colors configuration dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>In the <guilabel>Default Function Colors</guilabel> tab, you can change the colors used
|
||||
for the graphs of the ten functions allowed in &kmplot;.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="coords-config">
|
||||
<title><guimenuitem>Coordinate System</guimenuitem> Configuration</title>
|
||||
|
||||
<sect2 id="axes-config">
|
||||
<title>The <guilabel>Axes</guilabel> Configuration</title>
|
||||
<para>
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>X-Axis</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sets the range for the x-axis scale. You can choose one of the
|
||||
predefined ranges, or select <guilabel>Custom</guilabel> to make your
|
||||
own. Note that in the <guilabel>Custom</guilabel> boxes, you can use the
|
||||
predefined functions and constants (see <xref linkend="func-predefined"/>) as
|
||||
the extremes of the range (⪚, set <guilabel>Min:</guilabel> to
|
||||
<userinput>2*pi</userinput>). You can even use functions you have defined to
|
||||
set the extremes of the axis range. For example, if you have defined a function
|
||||
<userinput>f(x)=x^2</userinput>, you could set <guilabel>Min:</guilabel> to
|
||||
<userinput>f(3)</userinput>, which would make the lower end of the range equal
|
||||
to 9.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Y-Axis</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sets the range for the y-axis. See <quote>X-Axis</quote> above.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Axis-line width:</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sets the width of the lines representing the axes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Tic width:</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sets the width of the lines representing tics on the axes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Tic length:</guilabel></term>
|
||||
<listitem>
|
||||
<para>Sets the length of the lines representing tics on the axes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show labels</guilabel></term>
|
||||
<listitem>
|
||||
<para>If checked, the names (x, y) of the axes are shown on the plot and the axes' tics are labeled.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show extra frame</guilabel></term>
|
||||
<listitem>
|
||||
<para>If checked, the plot area is framed by an extra line.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show axes</guilabel></term>
|
||||
<listitem>
|
||||
<para>If checked, the axes are visible.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Show arrows</guilabel></term>
|
||||
<listitem>
|
||||
<para>If checked, the axes are displayed with arrows at their ends.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="grid-config">
|
||||
<title>The <guilabel>Grid</guilabel> Configuration</title>
|
||||
<para>You can set the <guilabel>Grid Style</guilabel> to one of four options:
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>None</guilabel></term>
|
||||
<listitem>
|
||||
<para>No gridlines are drawn on the plot area</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Lines</guilabel></term>
|
||||
<listitem>
|
||||
<para>Straight lines form a grid of squares on the plot area.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Crosses</guilabel></term>
|
||||
<listitem>
|
||||
<para>Crosses are drawn to indicate points where x and y have integer values
|
||||
(⪚, (1,1), (4,2) &etc;).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Polar</guilabel></term>
|
||||
<listitem>
|
||||
<para>Lines of constant radius and of constant angle are drawn on the plot
|
||||
area.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
<para>The <guilabel>Line width</guilabel> option is used to set the width of
|
||||
the lines of the grid.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="scaling-config">
|
||||
<title><guilabel>Scaling</guilabel> Configuration</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>screenshot of the scaling configuration dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings-scaling.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>screenshot of the scaling configuration dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>For each axis, you can set the <guilabel>Scaling:</guilabel> and
|
||||
<guilabel>Printing:</guilabel> of one tic. The <guilabel>Scaling:</guilabel>
|
||||
option selects how many units apart the axis tics will be (and therefore, how
|
||||
far apart grid lines will be drawn), and the <guilabel>Printing:</guilabel>
|
||||
option selects the length of one tic when displayed on the screen or
|
||||
printed. In this way, these options can be used to change the size of the graph
|
||||
on screen or on a page: For example, doubling the <guilabel>Printing:</guilabel>
|
||||
setting whilst keeping the <guilabel>Scaling:</guilabel> setting the same will
|
||||
result in the graph doubling in in height or width.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="font-config">
|
||||
<title><guilabel>Fonts</guilabel> Configuration</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>screenshot of the fonts configuration dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="settings-fonts.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>screenshot of the fonts configuration dialog</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para><guilabel>Header table:</guilabel> sets the font for the information table
|
||||
shown in &kmplot; printouts, and <guilabel>Axis font:</guilabel> and <guilabel>Axis font size:</guilabel>
|
||||
sets the font and its size used for all labels on the axes in the plot area.</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
@ -0,0 +1,47 @@
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kmplot;
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Program copyright 2000-2002 Klaus-Dieter Möller &Klaus-Dieter.Moeller.mail;
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<title>Contributors</title>
|
||||
<listitem>
|
||||
<para><acronym>CVS</acronym>: &Robert.Gogolok; <email>mail@robert-gogoloh.de</email></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Porting &GUI; to &kde; 3 and Translating: &Matthias.Messmer; &Matthias.Messmer.mail;</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Various improvements: Fredrik Edemar <email>f_edemar@linux.se</email></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Documentation copyright 2000--2002 by Klaus-Dieter Möller &Klaus-Dieter.Moeller.mail;.</para>
|
||||
<para>Documentation extended and updated for &kde; 3.2 by &Philip.Rodrigues; &Philip.Rodrigues.mail;.</para>
|
||||
<para>Documentation extended and updated for &kde; 3.3 by &Philip.Rodrigues; &Philip.Rodrigues.mail; and Fredrik Edemar <email>f_edemar@linux.se</email>.</para>
|
||||
<para>Documentation extended and updated for &kde; 3.4 by Fredrik Edemar <email>f_edemar@linux.se</email>.</para>
|
||||
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
|
||||
@ -0,0 +1,612 @@
|
||||
<chapter id="dcop">
|
||||
<title>Scripting &kmplot;</title>
|
||||
|
||||
<para>A new feature in &kde; 3.4 is that you can write scrips for &kmplot; with &DCOP;. For example, if you want to define a new function <userinput>f(x)=2sin x+3cos x</userinput>, set its line width to 20 and then draw it, you type in a console:</para>
|
||||
<para><command>dcop kmplot-PID Parser addFunction "f(x)=2sin x+3cos x"</command>
|
||||
As a result, the new function's id number will be returned, or -1 if the function could not be defined.</para>
|
||||
<para><command>>dcop kmplot-PID Parser setFunctionFLineWidth 20 ID</command>
|
||||
This command sets the function with the id number ID the line width to 20.</para>
|
||||
<para><command>>dcop kmplot-PID View drawPlot</command>
|
||||
This command repaints the window so that the function get visible.</para>
|
||||
<para>
|
||||
A list over the available functions:
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>
|
||||
KmPlotShell fileOpen &url
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Load the file <parameter>url</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg isModified
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns true if any changes are done.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg editColors
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the color edit dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg editAxes
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the coordinate system edit dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg editScaling
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the scaling edit dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg editFonts
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the fonts edit dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg editConstants
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the constants edit dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg newFunction
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the new function plot dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg newParametric
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the new parametric plot dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg newPolar
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the new polar plot dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg toggleShowSlider0
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows/hides parameter slider window number 1.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg toggleShowSlider1
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows/hides parameter slider window number 2.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg toggleShowSlider2
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows/hides parameter slider window number 3.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg toggleShowSlider3
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows/hides parameter slider window number 4.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotSave
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Saves the functions (opens the save dialog if it is a new file).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotSaveas
|
||||
</term>
|
||||
<listitem>
|
||||
<para>The same as choosing <menuchoice><guimenu>File</guimenu><guimenuitem>Save As</guimenuitem></menuchoice> in the menu.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotEditPlots
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the edit plots dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotPrint
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the print dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotExport
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the export dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotSettings
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Opens the settings dialog.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotNames
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows a list of predefined math functions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotCoord1
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Coordinate System I.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotCoord2
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Coordinate System II.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg slotCoord3
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Coordinate System III.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg getYValue
|
||||
</term>
|
||||
<listitem>
|
||||
<para>The same as choosing <menuchoice><guimenu>Tools</guimenu><guimenuitem>Get y-Value...</guimenuitem></menuchoice> in the menu.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg findMinimumValue
|
||||
</term>
|
||||
<listitem>
|
||||
<para>The same as choosing <menuchoice><guimenu>Tools</guimenu><guimenuitem>Search for Minimum Value...</guimenuitem></menuchoice> in the menu.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg findMaximumValue
|
||||
</term>
|
||||
<listitem>
|
||||
<para>The same as choosing <menuchoice><guimenu>Tools</guimenu><guimenuitem>Search for Maximum Value...</guimenuitem></menuchoice> in the menu.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
MainDlg graphArea
|
||||
</term>
|
||||
<listitem>
|
||||
<para>The same as choosing <menuchoice><guimenu>Tools</guimenu><guimenuitem>Calculate Integral</guimenuitem></menuchoice> in the menu.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser addFunction f_str
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Adds a new function with the expression <parameter>f_str</parameter>. If the expression does not contain a function name, it will be auto-generated. The id number of the new function is returned, or -1 if the function couln't be defined.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser delfkt id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Removes the function with the id number <parameter>id</parameter>. If the function could not be deleted, false is returned, otherwise true.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionExpression f_str id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the expression for the function with the id number <parameter>id</parameter> to <parameter>f_str</parameter>. Returns true if it succeed, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser countFunctions
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the number of functions (parametric functions are calculated as two).</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser listFunctionNames
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns a list with all functions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser fnameToId f_str
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the id number of <parameter>f_str</parameter> or -1 if the function name <parameter>f_str</parameter> was not found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser id x
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Calculates the value <parameter>x</parameter> for the function with the ID <parameter>id</parameter> or returns 0.0 if <parameter>id</parameter> does not exist.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionFVisible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns true if the function with the ID <parameter>id</parameter> is visible, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF1Visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns true if the first derivative of the function with the ID <parameter>id</parameter> is visible, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF2Visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns true if the second derivative of the function with the ID <parameter>id</parameter> is visible, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionIntVisible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns true if the integral of the function with the ID <parameter>id</parameter> is visible, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionFVisible visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows the function with the ID <parameter>id</parameter> if <parameter>visible</parameter> is true. If <parameter>visible</parameter> is false, the function will be hidden. True is returned if the function exists, otherwise false</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF1Visible visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows the first derivative of the function with the ID <parameter>id</parameter> if <parameter>visible</parameter> is true. If <parameter>visible</parameter> is false, the function will be hidden. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF2Visible visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows the second derivative of the function with the ID <parameter>id</parameter> if <parameter>visible</parameter> is true. If <parameter>visible</parameter> is false, the function will be hidden. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionIntVisible visible id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Shows the integral of the function with the ID <parameter>id</parameter> if <parameter>visible</parameter> is true. If <parameter>visible</parameter> is false, the function will be hidden. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionStr id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the function expression of the function with the ID <parameter>id</parameter>. If the function not exists, an empty string is returned instead.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionFColor id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the color of the function with the ID <parameter>id</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF1Color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the color of the first derivative of the function with the ID <parameter>id</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF2Color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the color of the second derivative of the function with the ID <parameter>id</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionIntColor id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the color of the integral of the function with the ID <parameter>id</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionFColor color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the color of the function with the ID <parameter>id</parameter> to <parameter>color</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF1Color color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the color of the first derivative of the function with the ID <parameter>id</parameter> to <parameter>color</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF2Color color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the color of the second derivative of the function with the ID <parameter>id</parameter> to <parameter>color</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionIntColor color id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the color of the integral of the function with the ID <parameter>id</parameter> to <parameter>color</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionFLineWidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the line width of the function with the ID <parameter>id</parameter>. If the function not exists, 0 is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF1LineWidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the line width of the first derivative of the function with the ID <parameter>id</parameter>. If the function not exists, 0 is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionF2LineWidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the line width of the first derivative of the function with the ID <parameter>id</parameter>. If the function not exists, 0 is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionIntLineWidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the line width of the integral of the function with the ID <parameter>id</parameter>. If the function not exists, 0 is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionFLineWidth linewidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the line width of the function with the ID <parameter>id</parameter> to <parameter>linewidth</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF1LineWidth linewidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the line width of the first derivative of the function with the ID <parameter>id</parameter> to <parameter>linewidth</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionF2LineWidth linewidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the line width of the second derivative of the function with the ID <parameter>id</parameter> to <parameter>linewidth</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionIntLineWidth linewidth id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the line width of the integral of the function with the ID <parameter>id</parameter> to <parameter>linewidth</parameter>. True is returned if the function exists, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionParameterList id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns a list with all the parameter values for the function with the ID <parameter>id</parameter>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionAddParameter new_parameter id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Adds the parameter value <parameter>new_parameter</parameter> to the function with the ID <parameter>id</parameter>. True is returned if the operation succeed, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionRemoveParameter remove_parameter id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Removes the parameter value <parameter>remove_parameter</parameter> from the function with the ID <parameter>id</parameter>. True is returned if the operation succeed, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionMinValue id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the minimum plot range value of the function with the ID <parameter>id</parameter>. If the function not exists or if the minimum value is not definied, an empty string is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionMaxValue id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the maximum plot range value of the function with the ID <parameter>id</parameter>. If the function not exists or if the maximum value is not definied, an empty string is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionMinValue min id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the minimum plot range value of the function with the ID <parameter>id</parameter> to <parameter>min</parameter>. True is returned if the function exists and the expression is valid, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionMaxValue max id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the maximum plot range value of the function with the ID <parameter>id</parameter> to <parameter>max</parameter>. True is returned if the function exists and the expression is valid, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionStartXValue id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the initial x point for the integral of the function with the ID <parameter>id</parameter>. If the function not exists or if the x-point-expression is not definied, an empty string is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser functionStartYValue id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Returns the initial y point for the integral of the function with the ID <parameter>id</parameter>. If the function not exists or if the y-point-expression is not definied, an empty string is returned.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionStartXValue min id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the initial x point for the integral of the function with the ID <parameter>id</parameter> to <parameter>x</parameter>. True is returned if the function exists and the expression is valid, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
Parser setFunctionStartYValue max id
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Sets the initial y point for the integral of the function with the ID <parameter>id</parameter> to <parameter>y</parameter>. True is returned if the function exists and the expression is valid, otherwise false.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
View stopDrawing
|
||||
</term>
|
||||
<listitem>
|
||||
<para>If &kmplot; currently is drawing a function, the procedure will stop.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>
|
||||
View drawPlot
|
||||
</term>
|
||||
<listitem>
|
||||
<para>Redraws all functions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
@ -0,0 +1,18 @@
|
||||
<chapter id="developers">
|
||||
<title>Developer's Guide to &kmplot;</title>
|
||||
|
||||
<para>If you want to contribute to &kmplot; feel free to send a mail to
|
||||
&Klaus-Dieter.Moeller.mail; or <email>f_edemar@linux.se</email> </para>
|
||||
</chapter>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
|
||||
|
After Width: | Height: | Size: 3.7 KiB |
@ -0,0 +1,70 @@
|
||||
<chapter id="first-steps">
|
||||
<title>First Steps With &kmplot;</title>
|
||||
|
||||
<sect1 id="simple-function-plot">
|
||||
<title>Simple Function Plot</title>
|
||||
|
||||
<para>
|
||||
In the main toolbar there is a simple text box in which you can enter
|
||||
a function expression. Simply enter:
|
||||
<screen><userinput>x^2</userinput></screen> and press &Enter;. This
|
||||
will draw the plot of y=x^2 in the coordinate system. Enter another
|
||||
expression in the text box like
|
||||
<screen><userinput>5*sin(x)</userinput></screen> and another plot will
|
||||
be added.
|
||||
</para>
|
||||
|
||||
<para>Click on one of the lines you have just plotted. Now the cross
|
||||
hair gets the color of the plot and is attached to the plot. You can
|
||||
use the mouse to move the cross hair along the plot. In the status
|
||||
bar at the bottom of the window the coordinates of the current
|
||||
position is displayed. Note that if the plot touches the x-axis the
|
||||
root will be displayed in the status bar, too.</para>
|
||||
|
||||
<para>Click the mouse again and the cross hair will be detached from
|
||||
the plot.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="edit-properties">
|
||||
<title>Edit Properties</title>
|
||||
|
||||
<para>Let us make some changes to the function and change the color of
|
||||
the plot.</para>
|
||||
|
||||
<para>You can edit all functions with the
|
||||
<menuchoice><guimenu>Plot</guimenu><guimenuitem>Edit
|
||||
Plots...</guimenuitem> </menuchoice> menu entry. A dialog appears
|
||||
which lists all the functions that you have plotted. Notice that
|
||||
&kmplot; has automatically found a unique function name for your
|
||||
expressions and completed the expression to a function
|
||||
equation.</para>
|
||||
|
||||
<para>Select <guilabel>f(x)=x^2</guilabel> in the list. A double click
|
||||
or pressing the <guibutton>Edit</guibutton> button will show you a
|
||||
dialog window. Here you have access to a lot of options. Let us rename
|
||||
the function and move the plot 5 units down. Change the function
|
||||
equation to <screen><userinput>parabola(x)=x^2-5</userinput></screen>
|
||||
</para>
|
||||
|
||||
<para>To select another color for the plot click into the
|
||||
<guilabel>Color:</guilabel> box. Finally press
|
||||
<guibutton>OK</guibutton> and your changes take effect in the
|
||||
coordinate system.</para>
|
||||
|
||||
<note><para>All changes can be undone until you press
|
||||
<guibutton>OK</guibutton> in the <guilabel>Edit Plots</guilabel>
|
||||
dialog.</para>
|
||||
</note>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
@ -0,0 +1,98 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&kmplot;"><!-- replace kmplot here -->
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY introduction SYSTEM "introduction.docbook">
|
||||
<!ENTITY firststeps SYSTEM "firststeps.docbook">
|
||||
<!ENTITY using SYSTEM "using.docbook">
|
||||
<!ENTITY commands SYSTEM "commands.docbook">
|
||||
<!ENTITY developer SYSTEM "developer.docbook">
|
||||
<!ENTITY credits SYSTEM "credits.docbook">
|
||||
<!ENTITY install SYSTEM "install.docbook">
|
||||
<!ENTITY reference SYSTEM "reference.docbook">
|
||||
<!ENTITY configuration SYSTEM "configuration.docbook">
|
||||
<!ENTITY dcop SYSTEM "dcop.docbook">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
<!-- The language must NOT be changed here. -->
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kmplot; Handbook</title>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Klaus-Dieter</firstname>
|
||||
<surname>Möller</surname>
|
||||
<affiliation>
|
||||
<address>&Klaus-Dieter.Moeller.mail;</address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<author>
|
||||
&Philip.Rodrigues; &Philip.Rodrigues.mail;
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2000</year><year>2001</year><year>2002</year>
|
||||
<holder>Klaus-Dieter Möller</holder>
|
||||
</copyright>
|
||||
|
||||
<copyright>
|
||||
<year>2003</year>
|
||||
<holder>&Philip.Rodrigues; &Philip.Rodrigues.mail;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2006-02-24</date>
|
||||
<releaseinfo>1.2.0</releaseinfo>
|
||||
|
||||
<!-- Abstract about this handbook -->
|
||||
|
||||
<abstract>
|
||||
<para>&kmplot; is a mathematical function plotter for the &kde;
|
||||
Desktop.</para>
|
||||
<para> <inlinemediaobject><imageobject><imagedata
|
||||
fileref="edu-logo.png"
|
||||
format="PNG"/></imageobject></inlinemediaobject> &kmplot; is part of
|
||||
the &kde;-EDU Project: <ulink
|
||||
url="http://edu.kde.org/">http://edu.kde.org/</ulink></para></abstract>
|
||||
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>KMPlot</keyword>
|
||||
<keyword>EDU</keyword>
|
||||
<keyword>edutainment</keyword>
|
||||
<keyword>plotting</keyword>
|
||||
<keyword>math</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
&introduction;
|
||||
&firststeps;
|
||||
&using;
|
||||
&configuration;
|
||||
&reference;
|
||||
&commands;
|
||||
&dcop;
|
||||
&developer;
|
||||
&credits;
|
||||
&install;
|
||||
|
||||
&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,34 @@
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="edu-logo.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
|
||||
<para>&kmplot; is part of the &kde; EDU Project: <ulink
|
||||
url="http://edu.kde.org/">http://edu.kde.org/</ulink></para>
|
||||
|
||||
<para>&kmplot; has its own homepage on <ulink
|
||||
url="http://kmplot.sourceforge.net">SourceForge</ulink>. You can also
|
||||
find archives of older versions of &kmplot; there, for example, for
|
||||
&kde; 2.x</para>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</appendix>
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
|
||||
|
||||
@ -0,0 +1,56 @@
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>&kmplot; is a mathematical function plotter for the &kde;
|
||||
Desktop. It has a powerful built-in parser. You can plot different
|
||||
functions simultaneously and combine them to build new
|
||||
functions.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Examples</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="threeplots.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Examples</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>&kmplot; supports parametric functions and functions in
|
||||
polar coordinates. Several grid modes are supported. Plots may be
|
||||
printed with high precision in the correct scale.</para>
|
||||
|
||||
<para>&kmplot; also provides some numerical and visual features like:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Filling and calculating
|
||||
the area between the plot and the first axis</para>
|
||||
</listitem>
|
||||
<listitem><para>Finding maximum and
|
||||
minimum values</para>
|
||||
</listitem>
|
||||
<listitem><para>Changing function parameters dynamically</para>
|
||||
</listitem>
|
||||
<listitem><para>Plotting
|
||||
derivatives and integral functions.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>These features help in learning the
|
||||
relationship between mathematical functions and their graphical
|
||||
representation in a coordinate system.</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 341 B |
|
After Width: | Height: | Size: 190 B |
|
After Width: | Height: | Size: 180 B |
|
After Width: | Height: | Size: 181 B |
|
After Width: | Height: | Size: 18 KiB |
@ -0,0 +1,66 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>&kde; User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>kmplot</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>kmplot</command></refname>
|
||||
<refpurpose>mathematical function plotter</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>kmplot</command>
|
||||
<group choice="opt"><option><replaceable>file</replaceable></option></group>
|
||||
<arg choice="opt">&kde; Generic Options</arg>
|
||||
<arg choice="opt">&Qt; Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kmplot; is a mathematical function plotter for &kde;. It has a powerful built-in parser. You can plot different functions simultaneously and combine them to build new functions.</para><para>&kmplot; supports parametric functions and functions in polar coordinates. Several grid modes are supported. Plots may be printed with high precision in the correct scale.</para><para>&kmplot; also provides some numerical and visual features, like filling and calculating the area between the plot and the first axis, finding maximum and minimum values, changing function parameters dynamically and plotting derivatives and integral functions.</para><para>&kmplot; is part of the &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option><replaceable>file</replaceable></option></term>
|
||||
<listitem><para>File to open</para></listitem></varlistentry>
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kmplot">help:/kmplot</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kmplot</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink url="http://edu.kde.org/kmplot/">the &kde; edutainment website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>&kmplot; was written by <personname><firstname>Klaus-Dieter</firstname><surname>Möller</surname></personname> <email>kdmoeller@foni.net</email>, &Matthias.Messmer; &Matthias.Messmer.mail; and <personname><firstname>Fredrik</firstname><surname>Edemar</surname></personname> <email>f_edemar@linux.se</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,339 @@
|
||||
<chapter id="reference">
|
||||
<title>&kmplot; Reference</title>
|
||||
|
||||
<!--
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="kfkt.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
|
||||
<para>This menu entry or toolbar button opens the Functions Editor. Here
|
||||
you can enter up to 10 functions or
|
||||
function groups. The parser knows <firstterm>explicit</firstterm> and
|
||||
<firstterm>parametric</firstterm> form. With specific extensions it
|
||||
is possible to add first and second derivatives and to choose values
|
||||
for the function group parameter.</para>
|
||||
-->
|
||||
|
||||
<sect1 id="func-syntax">
|
||||
<title>Function Syntax</title>
|
||||
|
||||
<para>Some syntax rules must be complied with:</para>
|
||||
|
||||
<screen>
|
||||
<userinput>name(var1[, var2])=term [;extensions]</userinput>
|
||||
</screen>
|
||||
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>name</term>
|
||||
<listitem>
|
||||
|
||||
<para>The function name. If the first character is <quote>r</quote>
|
||||
the parser assumes that you are using polar coordinates. If the first
|
||||
character is <quote>x</quote> (for instance <quote>xfunc</quote>) the
|
||||
parser expects a second function with a leading <quote>y</quote> (here
|
||||
<quote>yfunc</quote>) to define the function in parametric form.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>var1</term>
|
||||
<listitem><para>The function's variable</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>var2</term>
|
||||
<listitem><para> The function <quote>group parameter</quote>. It must be
|
||||
separated from the function's variable by a comma. You can use the group
|
||||
parameter to, for example, plot a number of graphs from one function. The parameter values can be selected manually or you can choose to have a slider bar that controls one parameter. By changing the value of the slider the value parameter will be changed. The slider can be set to an integer between 0 and 100.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>term</term>
|
||||
<listitem><para>The expression defining the function.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="func-predefined">
|
||||
<title>Predefined Function Names and Constants</title>
|
||||
|
||||
<para>
|
||||
All the predefined functions and constants that &kmplot; knows can be shown by
|
||||
selecting <menuchoice><guimenu>Help</guimenu><guimenuitem>Predefined Math Functions</guimenuitem>
|
||||
</menuchoice>. They are:
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>sqr, sqrt</term>
|
||||
<listitem>
|
||||
<para>Return the square and square root of a number, respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>exp, ln</term>
|
||||
<listitem>
|
||||
<para>Return the exponential and natural logarithm of a number, respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>log</term>
|
||||
<listitem>
|
||||
<para>Returns the logarithm to base 10 of a number.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>sin, arcsin</term>
|
||||
<listitem>
|
||||
<para>Return the sine and inverse sine of a number, respectively. Note that the
|
||||
argument to sin and the return value of arcsin are in radians.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>cos, arccos</term>
|
||||
<listitem>
|
||||
<para>Return the cosine and inverse cosine of a number, respectively. Also in radians.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>tan, arctan</term>
|
||||
<listitem>
|
||||
<para>Return the tangent and inverse tangent of a number,
|
||||
respectively. Also in radians.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>sinh, arcsinh</term>
|
||||
<listitem>
|
||||
<para>Return the hyperbolic sine and inverse hyperbolic sine of a number,
|
||||
respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>cosh, arccosh</term>
|
||||
<listitem>
|
||||
<para>Return the hyperbolic cosine and inverse hyperbolic cosine of a number, respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>tanh, arctanh</term>
|
||||
<listitem>
|
||||
<para>Return the hyperbolic tangent and inverse hyperbolic tangent of a number,
|
||||
respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>sin, arcsin</term>
|
||||
<listitem>
|
||||
<para>Return the sine and inverse sine of a number, respectively. Note that the
|
||||
argument to sin and the return value of arcsin are in radians.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>cos, arccos</term>
|
||||
<listitem>
|
||||
<para>Return the cosine and inverse cosine of a number, respectively. Also in radians.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>pi, e</term>
|
||||
<listitem>
|
||||
<para>Constants representing &pgr; (3.14159...) and e (2.71828...), respectively.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
These functions and constants and even all user defined functions can
|
||||
be used to determine the axes settings as well. See <xref linkend="axes-config"/>.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="func-extension">
|
||||
<title>Extensions</title>
|
||||
<para>An extension for a function is specified by entering a semicolon,
|
||||
followed by the extension, after the function definition. The extension can either be written in the Quick Edit box or by using the &DCOP; method Parser addFunction. None of the extensions are available for parametric functions but N and D[a,b] work for polar functions too. For example:
|
||||
<screen>
|
||||
<userinput>
|
||||
f(x)=x^2; A1
|
||||
</userinput>
|
||||
</screen>
|
||||
will show the graph y=x<superscript>2</superscript> with its first
|
||||
derivative. Supported extensions are described below:
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>N</term>
|
||||
<listitem>
|
||||
<para>
|
||||
The function will be stored but not be drawn.
|
||||
It can be used like any other user-defined or predefined function.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>A1</term>
|
||||
<listitem>
|
||||
<para>
|
||||
The graph of the derivative of the function will be drawn
|
||||
additionally with the same color but less line width.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>A2</term>
|
||||
<listitem>
|
||||
<para>
|
||||
The graph of the second derivative of the function will be
|
||||
drawn additionally with the same color but less line width.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>D[a,b]</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Sets the domain for which the function will be displayed.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>P[a{,b...}]</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Give a set of values of a group parameter for which the function should be
|
||||
displayed. For example: <userinput>f(x,k)=k*x;P[1,2,3]</userinput> will plot
|
||||
the functions f(x)=x, f(x)=2*x and f(x)=3*x. You can also use functions as the
|
||||
arguments to the P option.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
<para>
|
||||
Please note that you can do all of these operations by using the function editor dialog too.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="math-syntax">
|
||||
<title>Mathematical Syntax</title>
|
||||
<para>&kmplot; uses a common way of expressing mathematical functions, so you
|
||||
should have no trouble working it out. The operators &kmplot; understands are,
|
||||
in order of decreasing precedence:
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term>^</term>
|
||||
<listitem><para>The caret symbol performs exponentiation. ⪚,
|
||||
<userinput>2^4</userinput> returns 16.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>*, /</term>
|
||||
<listitem>
|
||||
<para>The asterisk and slash symbols perform multiplication and
|
||||
division . ⪚,
|
||||
<userinput>3*4/2</userinput> returns 6.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>+, -</term>
|
||||
<listitem><para>The plus and minus symbols perform addition and
|
||||
subtraction. ⪚, <userinput>1+3-2</userinput> returns 2.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
<para>
|
||||
Note the precedence, which means that if parentheses are not used,
|
||||
exponentiation is performed before multiplication/division, which is performed
|
||||
before addition/subtraction. So <userinput>1+2*4^2</userinput> returns 33, and
|
||||
not, say 144. To override this, use parentheses. To use the above example,
|
||||
<userinput>((1+2)*4)^2</userinput> <emphasis>will</emphasis> return 144.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<!--
|
||||
<sect1 id="coord-system">
|
||||
<title>Coordinate Systems</title>
|
||||
|
||||
<para><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="ksys1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></para>
|
||||
|
||||
<para>
|
||||
<inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="ksys2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></para>
|
||||
|
||||
<para>
|
||||
<inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="ksys3.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></para>
|
||||
-->
|
||||
<sect1 id="coord-area"><title>Plotting Area</title>
|
||||
<para>
|
||||
By default, explicitly given functions are plotted for the whole of the visible part of the
|
||||
x-axis. You can specify an other range in the edit-dialog for the function. For every pixel on the x-axis &kmplot; calculates a function value.
|
||||
If the plotting area contains the resulting point it is connected to the last
|
||||
drawn point by a line.
|
||||
</para>
|
||||
<para>
|
||||
Parametric functions are plotted for parameter values from 0 up to 2&pgr;.
|
||||
You can set the plotting range in the dialog for the function too.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="coord-cross">
|
||||
<title>Cross Hair Cursor</title>
|
||||
<para>
|
||||
While the mouse cursor is over the plotting area the cursor changes to a cross hair. The current coordinates can be seen at the intersections with the coordinate axes and also in the status bar at the bottom of the main window.
|
||||
</para>
|
||||
<para>
|
||||
You can trace a function's values more precisely by clicking onto or next to a graph. The selected function is shown in the status bar in the right column. The cross hair then will be caught and be colored in the same color as the graph. If the graph has the same color as the background color, the cross hair will have the inverted color of the background. When moving the mouse or pressing the keys Left or Right the cross hair will follow the function and you see the current x- and y-value. If the cross hair is close to y-axis, the root-value is shown in the statusbar. You can switch function with the Up and Down keys. A second click anywhere in the window or pressing any non-navigating key will leave this trace mode.
|
||||
</para>
|
||||
<para>
|
||||
Note that tracing is only possible with explicitly given functions.
|
||||
The coordinates are always displayed according to a Cartesian system of
|
||||
coordinates. Neither non-single-point parametric functions nor functions given in polar
|
||||
coordinates can be traced in this way.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 28 KiB |
@ -0,0 +1,321 @@
|
||||
<chapter id="using-kmplot">
|
||||
<title>Using &kmplot;</title>
|
||||
|
||||
<para>&kmplot; deals with named functions, which can be specified in
|
||||
terms of Cartesian coordinates (called <quote>explicit
|
||||
functions</quote>), polar coordinates or as parametric functions. To
|
||||
enter a function, choose
|
||||
<menuchoice><guimenu>Plot</guimenu><guimenuitem>Edit
|
||||
Plots...</guimenuitem> </menuchoice>. You can also enter new functions
|
||||
in the <guilabel>Function equation</guilabel> text box in the main
|
||||
&kmplot; window. The text box can handle explicit and polar
|
||||
functions. Each function you enter must have a unique name (&ie;, a
|
||||
name that is not taken by any of the existing functions displayed in
|
||||
the list box). A function name will be automatically generated if you
|
||||
do not specify one.</para>
|
||||
|
||||
<para>For more information on &kmplot; functions, see <xref
|
||||
linkend="reference"/>.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here is a screenshot of the &kmplot; welcome window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="main.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Screenshot</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect1 id="function-types">
|
||||
<title>Function Types</title>
|
||||
|
||||
<sect2 id="explicit-functions">
|
||||
<title>Explicit Functions</title>
|
||||
<para>To enter an explicit function (&ie;, a function in the form y=f(x)) into &kmplot;, just enter it in the
|
||||
following form:
|
||||
<screen>
|
||||
<userinput><replaceable>f</replaceable>(<replaceable>x</replaceable>)=<replaceable>expression</replaceable></userinput>
|
||||
</screen>
|
||||
Where:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<replaceable>f</replaceable> is the name of the function, and can be any
|
||||
string of letters and numbers you like, provided it does not start with any of
|
||||
the letters x, y or r (since these are used for parametric and polar
|
||||
functions).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem><para>
|
||||
<replaceable>x</replaceable> is the x-coordinate, to be used in the expression
|
||||
following the equals sign. It is in fact a dummy variable, so you can use any
|
||||
variable name you like, but the effect will be the same.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><replaceable>expression</replaceable> is the expression to be plotted,
|
||||
given in appropriate syntax for &kmplot;. See <xref linkend="math-syntax"/>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>As an example, to draw the graph of y=x<superscript>2</superscript>+2x,
|
||||
enter the following into the functions dialog of &kmplot;:
|
||||
<screen>
|
||||
f(x)=x^2+2x
|
||||
</screen>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="parametric-functions">
|
||||
<title>Parametric Functions</title>
|
||||
<para>Parametric functions are those in which the x and y coordinates are
|
||||
defined by separate functions of another variable, often called t. To enter a
|
||||
parametric function in &kmplot;, follow the procedure as for an explicit
|
||||
function, but prefix the name of the function describing the x-coordinate with
|
||||
the letter x, and the function describing the y-coordinate with the letter
|
||||
y. As with explicit functions, you may use any variable name you wish for the
|
||||
parameter. To draw a parametric function, you must go to <guimenu>Plot</guimenu><guimenuitem>New Parametric Plot...</guimenuitem>. A function name will be created automatic if you do not specify one.</para>
|
||||
<para>As an example, suppose you want to draw a circle, which has parametric
|
||||
equations x=sin(t), y=cos(t). In the &kmplot; functions dialog, do the
|
||||
following:
|
||||
<orderedlist>
|
||||
<listitem><para>Open the parametric plot dialog with
|
||||
<menuchoice><guimenu>Plot</guimenu><guimenuitem>New Parametric Plot...</guimenuitem>
|
||||
</menuchoice>.</para>
|
||||
</listitem>
|
||||
<listitem><para>Enter a name for the function, say,
|
||||
<userinput>circle</userinput>, in the <guilabel>Name</guilabel>
|
||||
box. The names of the x and y functions change to match this name: the
|
||||
x function becomes <guilabel>xcircle(t)</guilabel> and the y function
|
||||
becomes <guilabel>ycircle(t)</guilabel>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>In the x and y boxes, enter the appropriate equations, &ie;,
|
||||
<guilabel>xcircle(t)=</guilabel><userinput>sin(t)</userinput> and
|
||||
<guilabel>ycircle(t)=</guilabel><userinput>cos(t)</userinput>.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
Click on <guibutton>OK</guibutton> and the function will be drawn.
|
||||
</para>
|
||||
<para>You can set some further options for the plot in this dialog:
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Hide</guilabel></term>
|
||||
<listitem>
|
||||
<para>If this option is selected, the plot is not drawn, but &kmplot;
|
||||
remembers the function definition, so you can use it to define other
|
||||
functions.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Custom plot minimum-range</guilabel></term>
|
||||
<term><guilabel>Custom plot maximum-range</guilabel></term>
|
||||
<listitem>
|
||||
<para>If this options are selected, you can change the maximum and
|
||||
minimum values of the parameter t for which the function is plotted
|
||||
using the <guilabel>Min:</guilabel> and <guilabel>Max:</guilabel>
|
||||
boxes.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Line width:</guilabel></term>
|
||||
<listitem>
|
||||
<para>With this option you can set the width of the line drawn on the
|
||||
plot area, in units of 0.1mm.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><guilabel>Color:</guilabel></term>
|
||||
<listitem>
|
||||
<para>Click on the color box and pick a color in the dialog that
|
||||
appears. The line on the plot will be drawn in this color.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="polar-functions">
|
||||
<title>Entering Functions in Polar Coordinates</title>
|
||||
|
||||
<para>Polar coordinates represent a point by its distance from the origin
|
||||
(usually called r), and the angle a line from the origin to the point makes
|
||||
with the x-axis (usually represented by the Greek letter theta). To enter
|
||||
functions in polar coordinates, use the menu entry
|
||||
<menuchoice><guimenu>Plot</guimenu><guimenuitem>New Polar Plot...</guimenuitem>
|
||||
</menuchoice>. In the box labeled <guilabel>r</guilabel>, complete the
|
||||
function definition, including the name of the theta variable you want
|
||||
to use, ⪚, to draw the Archimedes' spiral r=theta, enter:
|
||||
<screen>
|
||||
<userinput>
|
||||
(theta)=theta
|
||||
</userinput>
|
||||
</screen>
|
||||
so that the whole line reads <quote>r(theta)=theta</quote>. Note that
|
||||
you can use any name for the theta variable, so
|
||||
<quote>r(foo)=foo</quote> would have produced exactly the same output.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="combining-functions">
|
||||
<title>Combining Functions</title>
|
||||
<para>Functions can be combined to produce new ones. Simply enter the functions
|
||||
after the equals sign in an expression as if the functions were variables. For
|
||||
example, if you have defined functions f(x) and g(x), you can plot the sum of f
|
||||
and g with:
|
||||
<screen>
|
||||
<userinput>
|
||||
sum(x)=f(x)+g(x)
|
||||
</userinput>
|
||||
</screen>
|
||||
</para>
|
||||
<para>Note that you can only combine functions of the same type, ⪚ an
|
||||
explicit function cannot be combined with a polar function.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="function-appearance">
|
||||
<title>Changing the appearance of functions</title>
|
||||
|
||||
<para>To change the appearance of a function's graph on the main plot
|
||||
window, select the function in the <guilabel>Edit Plots</guilabel>
|
||||
dialog, and click on the <guibutton>Edit</guibutton> button. In the
|
||||
dialog which appears, you can change the line width in the text box,
|
||||
and the color of the function's graph by clicking on the color button
|
||||
at the bottom. If you are editing an explicit function, you will see a
|
||||
dialog with three tabs. In the first one you specify the equation of
|
||||
the function. The <guilabel>Derivatives</guilabel> tab lets you draw
|
||||
the first and second derivative to the function. With the
|
||||
<guilabel>Integral</guilabel> tab you can draw the integral of the
|
||||
function which is calculated using Euler's method. </para>
|
||||
<para>Another way to edit a function is to right click on the
|
||||
graph. In the popup menu that appears, choose
|
||||
<guibutton>Edit</guibutton></para>
|
||||
|
||||
<para>For more information on the popup menu, see <xref
|
||||
linkend="popupmenu"/>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="popupmenu">
|
||||
<title>Popup menu</title>
|
||||
|
||||
<para>When right-clicking on a plot function or a single-point parametric plot function a popup menu will appear.
|
||||
In the menu there are five items available:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Hide</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Hides the selected graph. Other plots of the graph's function will still be shown.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Remove</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Removes the function. All its graphs will disappear.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Edit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Shows the editor dialog for the selected function.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Copy</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Copies the graph to another running &kmplot; instance.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Move</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Moves the graph to another running &kmplot; instance.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>For plot functions the following four items are also available:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Get y-Value</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Opens a dialog in which you can find the y-value corresponding to
|
||||
a specific x-value. The selected graph will be highlighted in the
|
||||
dialog. Enter an x value in the <guilabel>X:</guilabel> box, and click
|
||||
on <guibutton>Calculate</guibutton> (or press &Enter;). The corresponding y
|
||||
value will be shown under <guilabel>Y:</guilabel>.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Search for Minimum Value</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Find the minimum value of the graph in a specified range. The
|
||||
selected graph will be highlighted in the dialog that appears. Enter
|
||||
the lower and upper boundaries of the region in which you want to
|
||||
search for a minimum, and click <guibutton>Find</guibutton>. The x and
|
||||
y values at the minimum will be shown.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Search for Maximum Value</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>This is the same as <guimenuitem>Search for Minimum
|
||||
Value</guimenuitem> above, but finds maximum values instead of minima. </para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice><guimenuitem>Calculate Integral</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem>
|
||||
<para>Select the x-values for the graph in the new dialog that appears.
|
||||
Calulates the integral and draws the area between the graph and the x-axis in the
|
||||
selected range in the color of the graph.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
</chapter>
|
||||
<!--
|
||||
Local Variables:
|
||||
mode: sgml
|
||||
sgml-minimize-attributes:nil
|
||||
sgml-general-insert-case:lower
|
||||
sgml-indent-step:0
|
||||
sgml-indent-data:nil
|
||||
sgml-parent-document:("index.docbook" "BOOK" "CHAPTER")
|
||||
End:
|
||||
-->
|
||||
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 33 KiB |
@ -0,0 +1,53 @@
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="kpercentage-mainwindow">
|
||||
<title>The main &kpercentage; window</title>
|
||||
|
||||
<para>In the main window you can only enter one of the three input
|
||||
boxes. Here you have to type in your guess. Press
|
||||
<keycap>Enter</keycap> or click the <guibutton>Apply</guibutton>
|
||||
Button, to see if you are right. </para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the &kpercentage; main window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="main.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here's a screenshot of the &kpercentage; main window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>On the bottom, two progress bars display your effort. The upper bar shows the ratio
|
||||
of totally attempted exercises. The lower bar compares the
|
||||
right with the wrong answers. Do you notice that this is a
|
||||
percentage task too? Mistyped inputs (letters, spaces, and so on) have no influence here.
|
||||
</para>
|
||||
|
||||
<para> At any time you can leave this window with the
|
||||
<guibutton>Cancel</guibutton> button. You will be carried back to the
|
||||
welcome window. There you can select another type of task or exit
|
||||
&kpercentage;.</para>
|
||||
|
||||
<para> If you press the <guibutton>Apply</guibutton> button you are
|
||||
told whether your input was right or wrong... </para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Information about correct input</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="answer.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Information about correct input</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The funny smiley jumping up and down for every right task you made!</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
@ -0,0 +1,35 @@
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kpercentage;
|
||||
</para>
|
||||
<para>
|
||||
Program copyright 2001 Matthias Messmer <email>bmlmessmer@web.de</email>
|
||||
</para>
|
||||
<para>
|
||||
Contributors:
|
||||
<itemizedlist>
|
||||
<listitem><para><acronym>CVS</acronym>, coding and discussion partner: Robert Gogolok
|
||||
<email>mail@robert-gogoloh.de</email> and
|
||||
Carsten Niehaus <email>cniehaus@gmx.de</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Cleaning and bugfixing the code: Primoz Anzur <email>zerokode@gmx.net</email></para></listitem>
|
||||
<listitem><para>Pixmaps: Elhay Achiam
|
||||
<email>e_achiam@netvision.net.il</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Spelling and <quote>good</quote> English: Jonathan Drews
|
||||
<email>j.e.drews@att.net</email></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2001 by Matthias Messmer <email>bmlmessmer@web.de</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,9 @@
|
||||
<chapter id="developers">
|
||||
<title>Developer's Guide to &kpercentage;</title>
|
||||
|
||||
<para>If you want to contribute &kpercentage;, feel free to send me a
|
||||
mail <email>bmlmessmer@web.de</email>.</para>
|
||||
|
||||
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 3.7 KiB |
@ -0,0 +1,20 @@
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<qandaset id="faqlist">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I got no help by pressing the <guibutton>Help</guibutton> Button in
|
||||
&kpercentage;?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>If you got &kpercentage; from <acronym>CVS</acronym>, you must
|
||||
install the documentation separately.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 8.3 KiB |
@ -0,0 +1,102 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY introduction SYSTEM "introduction.docbook">
|
||||
<!ENTITY using SYSTEM "using.docbook">
|
||||
<!ENTITY commands SYSTEM "commands.docbook">
|
||||
<!ENTITY devel SYSTEM "devel.docbook">
|
||||
<!ENTITY faq SYSTEM "faq.docbook">
|
||||
<!ENTITY credits SYSTEM "credits.docbook">
|
||||
<!ENTITY install SYSTEM "install.docbook">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<!-- The language must NOT be changed here. -->
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kpercentage; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Matthias</firstname>
|
||||
<surname>Messmer</surname>
|
||||
<affiliation>
|
||||
<address><email>&Matthias.Messmer.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<author>
|
||||
<firstname>Carsten</firstname>
|
||||
<surname>Niehaus</surname>
|
||||
<affiliation>
|
||||
<address><email>cniehaus@gmx.de</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<author>
|
||||
<firstname>Robert</firstname>
|
||||
<surname>Gogolok</surname>
|
||||
<affiliation>
|
||||
<address><email>&Robert.Gogolok.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001</year>
|
||||
<year>2002</year>
|
||||
<holder>&Matthias.Messmer;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2002-10-08</date>
|
||||
<releaseinfo>1.2</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kpercentage; is a small math application that will help pupils
|
||||
to improve their skills in calculating percentages.
|
||||
|
||||
|
||||
<inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="edu-logo.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject>
|
||||
&kpercentage; is part of the &kde;-EDU Project:
|
||||
<ulink url="http://edu.kde.org/">http://edu.kde.org/</ulink></para>
|
||||
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>KPercentage</keyword>
|
||||
<keyword>EDU</keyword>
|
||||
<keyword>edutainment</keyword>
|
||||
<keyword>percentages</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
&introduction;
|
||||
&using;
|
||||
&commands;
|
||||
&devel;
|
||||
&faq;
|
||||
&credits;
|
||||
&install;
|
||||
|
||||
&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,21 @@
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<para>
|
||||
<inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="edu-logo.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject>
|
||||
&kpercentage; is part of the KDE-EDU Project:
|
||||
<ulink url="http://edu.kde.org/">http://edu.kde.org/</ulink>
|
||||
</para>
|
||||
|
||||
<para>Information about &kpercentage; can be found on <ulink
|
||||
url="http://edu.kde.org/kpercentage">The &kpercentage; home
|
||||
page</ulink>.</para>
|
||||
|
||||
&install.intro.documentation;
|
||||
&install.compile.documentation;
|
||||
|
||||
</appendix>
|
||||
@ -0,0 +1,13 @@
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&kpercentage; is a small math application that will help pupils
|
||||
to improve their skills in calculating percentages.</para>
|
||||
|
||||
<para>There is a special training section for the three basic
|
||||
tasks. Finally the pupil can select a random mode, in which all three
|
||||
tasks are mixed randomly.</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 56 KiB |
@ -0,0 +1,75 @@
|
||||
<chapter id="using-kpercentage">
|
||||
<title>Using &kpercentage;</title>
|
||||
|
||||
<para> The welcome window lets you choose the type of exercise by
|
||||
clicking on one of the buttons. The buttons are labeled with the
|
||||
value to be deduced in the exercises.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the &kpercentage; welcome window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="welcome.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here's a screenshot of the &kpercentage; welcome window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect1 id="kpercentage-features">
|
||||
<title>More &kpercentage; features</title>
|
||||
|
||||
<para>On the left hand the number of exercises can be selected. One
|
||||
can choose from 1 to 10 tasks.</para>
|
||||
|
||||
<para>On the right hand you can change the level of difficulty:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Easy</term>
|
||||
<listitem>
|
||||
<para>Only percentages with easy to calculate values are given.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Medium</term>
|
||||
<listitem>
|
||||
<para>Harder percentages are included, even some with values greater
|
||||
than 100%</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Crazy</term>
|
||||
<listitem>
|
||||
<para>Any percentage up to 200% may occur. All values are whole
|
||||
numbered however, so be honest, calculate them in your head!</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>There are some help functions integrated. As usual some tool tips arise when the mouse is over
|
||||
a control element like a button or an edit line. If you click
|
||||
on the <guibutton>Help</guibutton> button, a little menu pops up with
|
||||
further opportunities:</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The Help popup menu.</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="help.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The Help popup menu.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
&help.menu.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 72 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
After Width: | Height: | Size: 40 KiB |
@ -0,0 +1,45 @@
|
||||
<sect1 id="ai-contents">
|
||||
<title>AstroInfo: Table of Contents</title>
|
||||
|
||||
<itemizedlist><title>The Sky and Coordinate Systems</title>
|
||||
<listitem><para><link linkend="ai-skycoords">Celestial Coordinate Systems</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-cequator">Celestial Equator</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-cpoles">Celestial Poles</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-csphere">Celestial Sphere</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-ecliptic">The Ecliptic</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-equinox">The Equinoxes</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-geocoords">Geographic Coordinates</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-greatcircle">Great Circles</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-horizon">The Horizon</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-hourangle">Hour Angle</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-meridian">Local Meridian</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-precession">Precession</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-zenith">The Zenith</link></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<itemizedlist><title>Time</title>
|
||||
<listitem><para><link linkend="ai-julianday">Julian Day</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-leapyear">Leap Years</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-sidereal">Sidereal Time</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-timezones">Time Zones</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-utime">Universal Time</link></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<itemizedlist><title>Physics</title>
|
||||
<listitem><para><link linkend="ai-blackbody">Blackbody Radiation</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-darkmatter">Dark Matter</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-flux">Flux</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-luminosity">Luminosity</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-parallax">Parallax</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-retrograde">Retrograde Motion</link></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<itemizedlist><title>Astrophysics</title>
|
||||
<listitem><para><link linkend="ai-ellipgal">Elliptical Galaxies</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-spiralgal">Spiral Galaxies</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-magnitude">The Magnitude Scale</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-stars">Stars: An Introductory FAQ</link></para></listitem>
|
||||
<listitem><para><link linkend="ai-colorandtemp">Star Colors and Temperatures</link></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 1.1 KiB |
@ -0,0 +1,90 @@
|
||||
<sect1 id="tool-altvstime">
|
||||
<title>Altitude vs. Time Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Altitude vs. Time Tool</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Altitude vs. Time Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="altvstime.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Altitude vs. Time Plotter</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This tool plots the altitude of any objects as a function of time,
|
||||
for any date and location on Earth. The top section is a graphical
|
||||
plot of altitude angle on the vertical axis, and time on the horizontal
|
||||
axis. The time is shown both as standard local time along the bottom,
|
||||
and <link linkend="ai-sidereal">sidereal time</link> along the top.
|
||||
The bottom half of the graph is shaded green to indicate that points
|
||||
in this region are below the horizon.
|
||||
</para>
|
||||
<para>
|
||||
There are a few ways to add curves to the plot. The simplest way to
|
||||
add the curve of an existing object is to simply type its name in the
|
||||
<guilabel>Name</guilabel> input field, and press Enter, or the
|
||||
<guibutton>Plot</guibutton> button. If the text you enter is found in
|
||||
the object database, the object's curve is added to the graph. You
|
||||
can also press the <guibutton>Browse</guibutton> button to open the
|
||||
<link linkend="findobjects">Find Object Window</link> to select an
|
||||
object from the list of known objects. If you want to add a point
|
||||
that does not exist in the object database, simply enter a name for
|
||||
the point, and then fill in the coordinates in the
|
||||
<guilabel>RA</guilabel> and <guilabel>Dec</guilabel> input fields.
|
||||
Then press the <guibutton>Plot</guibutton> button to add the curve for
|
||||
your custom object to the plot (note that you have to pick a name that
|
||||
does not already exist in the object database for this to work).
|
||||
</para>
|
||||
<para>
|
||||
When you add an object to the plot, its altitude vs. time curve is
|
||||
plotted with a thick white line, and its name is added to the listbox
|
||||
at the lower right. Any objects that were already present are plotted
|
||||
with a thinner red curve. You can choose which object is plotted with
|
||||
the thick white curve by highlighting its name in the listbox.
|
||||
</para>
|
||||
<para>
|
||||
These curves show the objects' Altitude (angle above the <link
|
||||
linkend="ai-horizon">horizon</link>) as a function of time. When
|
||||
a curve passes from the lower half to the upper half, the object has
|
||||
risen; when it falls back to the lower half, it has set. For example,
|
||||
in the screenshot, the minor planet <firstterm>Quaoar</firstterm> is
|
||||
setting at around 15:00 local time, and is rising at about 04:00 local
|
||||
time.
|
||||
</para>
|
||||
<para>
|
||||
The Altitude of an object depends on both where you are on Earth, and
|
||||
on the Date. By default, the Tool adopts the Location and Date from the
|
||||
current KStars settings. You can change these parameters in the
|
||||
<guilabel>Date & Location</guilabel> Tab. To change the Location,
|
||||
you can press the <guibutton>Choose City...</guibutton> button to open
|
||||
the <link linkend="setgeo">Set Geographic Location</link> Window, or
|
||||
enter Longitude and Latitude values manually in the input fields, and
|
||||
press the <guibutton>Update</guibutton> button. To change the Date,
|
||||
use the <guilabel>Date</guilabel> picker widget, then press
|
||||
<guibutton>Update</guibutton>. Note that any curves you had already
|
||||
plotted will be automatically updated when you change the Date and/or
|
||||
Location.
|
||||
</para>
|
||||
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
Plot the Sun's Altitude curve. Make sure the geographic location is not
|
||||
near the equator. Change the Date to some time in June, and then again to
|
||||
sometime in January. You can see easily why we have seasons; in the
|
||||
winter, the Sun is above the horizon for less time (the days are shorter),
|
||||
and its altitude is never very high.
|
||||
</para>
|
||||
</tip>
|
||||
|
||||
|
||||
</sect1>
|
||||
|
||||
|
After Width: | Height: | Size: 46 KiB |
@ -0,0 +1,48 @@
|
||||
<chapter id="astroinfo">
|
||||
<title>The AstroInfo Project</title>
|
||||
|
||||
<para>
|
||||
Here you can find a collection of short articles that explain various
|
||||
astronomical concepts used in &kstars;. From coordinate systems to
|
||||
celestial mechanics, you can find answers to your questions here.
|
||||
</para><para>
|
||||
The articles sometimes also contain exercises that you can perform with
|
||||
&kstars; to illustrate the concept behind the article.
|
||||
</para>
|
||||
|
||||
&contents; <!--AstroInfo: Table of Contents-->
|
||||
|
||||
&skycoords; <!--AstroInfo: Celestial Coordinate Systems-->
|
||||
&cequator; <!--AstroInfo: Celestial Equator-->
|
||||
&cpoles; <!--AstroInfo: Celestial Poles-->
|
||||
&csphere; <!--AstroInfo: Celestial Sphere-->
|
||||
&ecliptic; <!--AstroInfo: The Ecliptic-->
|
||||
&equinox; <!--AstroInfo: The Equinoxes-->
|
||||
&geocoords; <!--AstroInfo: Geographic Coordinates-->
|
||||
&greatcircle; <!--AstroInfo: Great Circles-->
|
||||
&horizon; <!--AstroInfo: Horizon-->
|
||||
&hourangle; <!--AstroInfo: Hour Angle-->
|
||||
&meridian; <!--AstroInfo: Local Meridian-->
|
||||
&precession; <!--AstroInfo: Precession-->
|
||||
&zenith; <!--AstroInfo: The Zenith-->
|
||||
|
||||
&julianday; <!--AstroInfo: Julian Day-->
|
||||
&leapyear; <!--AstroInfo: Leap Year-->
|
||||
&sidereal; <!--AstroInfo: Sidereal Time-->
|
||||
&timezones; <!--AstroInfo: Time zones-->
|
||||
&utime; <!--AstroInfo: Universal Time-->
|
||||
|
||||
&blackbody; <!--AstroInfo: Blackbody Radiation-->
|
||||
&darkmatter; <!--AstroInfo: Dark Matter-->
|
||||
&flux; <!--AstroInfo: Flux-->
|
||||
&luminosity; <!--AstroInfo: Luminosity-->
|
||||
¶llax; <!--AstroInfo: Parallax-->
|
||||
&retrograde; <!--AstroInfo: Retrograde Motion-->
|
||||
|
||||
&ellipgal; <!--Elliptical Galaxies-->
|
||||
&spiralgal; <!--Spiral Galaxies-->
|
||||
&magnitude; <!--AstroInfo: The Magnitude Scale-->
|
||||
&stars; <!--AstroInfo: Stars: An Introductory FAQ-->
|
||||
&colorandtemp; <!--AstroInfo: Star Colors and Temperatures-->
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,169 @@
|
||||
<sect1 id="ai-blackbody">
|
||||
|
||||
<sect1info>
|
||||
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Blackbody Radiation</title>
|
||||
<indexterm><primary>Blackbody Radiation</primary>
|
||||
<seealso>Star Colors and Temperatures</seealso>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
A <firstterm>blackbody</firstterm> refers to an opaque object that
|
||||
emits <firstterm>thermal radiation</firstterm>. A perfect
|
||||
blackbody is one that absorbs all incoming light and does not
|
||||
reflect any. At room temperature, such an object would
|
||||
appear to be perfectly black (hence the term
|
||||
<emphasis>blackbody</emphasis>). However, if heated to a high
|
||||
temperature, a blackbody will begin to glow with
|
||||
<firstterm>thermal radiation</firstterm>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In fact, all objects emit thermal radiation (as long as their
|
||||
temperature is above Absolute Zero, or -273.15 degrees Celsius),
|
||||
but no object emits thermal radiation perfectly; rather, they are
|
||||
better at emitting/absorbing some wavelengths of light than others.
|
||||
These uneven efficiencies make it difficult to study the interaction
|
||||
of light, heat and matter using normal objects.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Fortunately, it is possible to construct a nearly-perfect blackbody.
|
||||
Construct a box made of a thermally conductive material, such as
|
||||
metal. The box should be completely closed on all sides, so that the
|
||||
inside forms a cavity that does not receive light from the
|
||||
surroundings. Then, make a small hole somewhere on the box.
|
||||
The light coming out of this hole will almost perfectly resemble the
|
||||
light from an ideal blackbody, for the temperature of the air inside
|
||||
the box.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
At the beginning of the 20th century, scientists Lord Rayleigh,
|
||||
and Max Planck (among others) studied the blackbody
|
||||
radiation using such a device. After much work, Planck was able to
|
||||
empirically describe the intensity of light emitted by a blackbody as a
|
||||
function of wavelength. Furthermore, he was able to describe how this
|
||||
spectrum would change as the temperature changed. Planck's work on
|
||||
blackbody radiation is one of the areas of physics that led to the
|
||||
foundation of the wonderful science of Quantum Mechanics, but that is
|
||||
unfortunately beyond the scope of this article.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
What Planck and the others found was that as the temperature of a
|
||||
blackbody increases, the total amount of light emitted per
|
||||
second increases, and the wavelength of the spectrum's peak shifts to
|
||||
bluer colors (see Figure 1).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="blackbody.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<caption><para><phrase>Figure 1</phrase></para></caption>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For example, an iron bar becomes orange-red when heated to high temperatures and its color
|
||||
progressively shifts toward blue and white as it is heated further.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In 1893, German physicist Wilhelm Wien quantified the relationship between blackbody
|
||||
temperature and the wavelength of the spectral peak with the
|
||||
following equation:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="lambda_max.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
where T is the temperature in Kelvin. Wien's law (also known as
|
||||
Wien's displacement law) states that the
|
||||
wavelength of maximum emission from a blackbody is inversely
|
||||
proportional to its temperature. This makes sense;
|
||||
shorter-wavelength (higher-frequency) light corresponds to
|
||||
higher-energy photons, which you would expect from a
|
||||
higher-temperature object.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For example, the sun has an average temperature of 5800 K, so
|
||||
its wavelength of maximum emission is given by:
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="lambda_ex.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This wavelengths falls in the
|
||||
green region of the visible light spectrum, but the sun's continuum
|
||||
radiates photons both longer and shorter than lambda(max) and the
|
||||
human eyes perceives the sun's color as yellow/white.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In 1879, Austrian physicist Stephan Josef Stefan showed that
|
||||
the luminosity, L, of a black body is proportional to the 4th power of its temperature T.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="luminosity.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
where A is the surface area, alpha is a constant of proportionality,
|
||||
and T is the temperature in Kelvin. That is, if we double the
|
||||
temperature (e.g. 1000 K to 2000 K) then the total energy radiated
|
||||
from a blackbody increase by a factor of 2^4 or 16.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Five years later, Austrian physicist Ludwig Boltzman derived the same
|
||||
equation and is now known as the Stefan-Boltzman law. If we assume a
|
||||
spherical star with radius R, then the luminosity of such a star is
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="luminosity_ex.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
where R is the star radius in cm, and the alpha is the
|
||||
Stefan-Boltzman constant, which has the value:
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="alpha.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 52 KiB |
@ -0,0 +1,43 @@
|
||||
<sect2 id="calc-angdist">
|
||||
<title>Angular Distance module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Angular Distance module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Angular Distance calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-angdist.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Angular Distance</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The Angular Distance tool is used to measure the angle between any
|
||||
two points on the sky. You simply specify the
|
||||
<link linkend="equatorial">Equatorial coordinates</link> of the
|
||||
desired pair of points, and then press the
|
||||
<guibutton>Compute</guibutton> button to obtain the angle between
|
||||
the two points.
|
||||
</para>
|
||||
<para>
|
||||
There is also a Batch mode for this module. In batch mode, you
|
||||
specify an input filename which contains four numbers per line:
|
||||
the RA and Dec values for pairs of points. Alternatively, you can
|
||||
specify a single value for any of these four coordinates in
|
||||
the calculator panel (the corresponding values in the input file
|
||||
should be skipped if they are specified in the calculator).
|
||||
</para>
|
||||
<para>
|
||||
Once you have specified the input filename and an output filename,
|
||||
simply press the <guibutton>Run</guibutton> button to generate the
|
||||
output file.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 38 KiB |
@ -0,0 +1,41 @@
|
||||
<sect2 id="calc-apcoords">
|
||||
<title>Apparent Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Apparent Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Apparent Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-apcoords.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Apparent Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The Apparent Coordinates module converts the <firstterm>catalog
|
||||
coordinates</firstterm> of a point in the sky to its
|
||||
<firstterm>apparent coordinates</firstterm> for any date. The
|
||||
coordinates of objects in the sky are not fixed, because of
|
||||
<link linkend="ai-precession">precession</link>, nutation and
|
||||
aberration. This module takes these effects into account.
|
||||
</para>
|
||||
<para>
|
||||
To use the module, first enter the desired target date and time
|
||||
in the <guilabel>Target Time/Date</guilabel> section. Then,
|
||||
enter the catalog coordinates in the <guilabel>Catalog
|
||||
Coordinates</guilabel> section. You can also specify the
|
||||
catalog's epoch here (usually 2000.0 for modern object
|
||||
catalogs). Finally, press the <guibutton>Compute</guibutton>
|
||||
button, and the object's coordinates for the target date
|
||||
will be displayed in the <guilabel>Apparent Coordinates</guilabel>
|
||||
section.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 48 KiB |
@ -0,0 +1,28 @@
|
||||
<sect2 id="calc-dayduration">
|
||||
<title>Day Duration module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Day Duration module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Day Duration calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-daylength.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Day Duration</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module computes the length of day as well as sunrise, sun-transit
|
||||
(noon), and sunset times for any calendar date, for any location on
|
||||
Earth. First fill in the desired geographic coordinates and date, then
|
||||
press the <guibutton>Compute</guibutton> button.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 42 KiB |
@ -0,0 +1,43 @@
|
||||
<sect2 id="calc-ecliptic">
|
||||
<title>Ecliptic Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Ecliptic Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Ecliptic Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-ecliptic.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Ecliptic Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module converts between <link linkend="equatorial">Equatorial
|
||||
coordinates</link> and <link linkend="ecliptic">Ecliptic
|
||||
coordinates</link>. First, select which coordinates
|
||||
should be taken as input values in the <guilabel>Choose Input
|
||||
Coordinates</guilabel> section. Then, fill in the corresponding
|
||||
coordinate values in either the <guilabel>Ecliptic
|
||||
coordinates</guilabel> or <guilabel>Equatorial coordinates</guilabel>
|
||||
section. Finally, press the <guibutton>Compute</guibutton> button,
|
||||
and the complementary coordinates will be filled in.
|
||||
</para>
|
||||
<para>
|
||||
The module contains a batch mode for converting several coordinate
|
||||
pairs at once. You must construct an input file in which each line
|
||||
contains two values: the input coordinate pairs (either Equatorial
|
||||
or Ecliptic). Then specify which coordinates you are using as input,
|
||||
and identify the input and output filenames. Finally, press the
|
||||
<guibutton>Run</guibutton> button to generate the output file,
|
||||
which will contain the converted coordinates (Equatorial or
|
||||
Ecliptic; the complement of what you chose as the input values).
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 40 KiB |
@ -0,0 +1,34 @@
|
||||
<sect2 id="calc-eqgal">
|
||||
<title>Equatorial/Galactic Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Equatorial/Galactic Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Equatorial/Galactic Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-eqgal.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Equatorial/Galactic Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module converts from <link linkend="equatorial">Equatorial
|
||||
coordinates</link> to <link linkend="galactic">Galactic
|
||||
coordinates</link>, and vice versa. First, select which coordinates
|
||||
should be taken as input values in the <guilabel>Input
|
||||
Selection</guilabel> section. Then, fill in the corresponding
|
||||
coordinate values in either the <guilabel>Galactic
|
||||
coordinates</guilabel> or <guilabel>Equatorial coordinates</guilabel>
|
||||
section. Finally, press the <guibutton>Compute</guibutton> button,
|
||||
and the complementary coordinates will be filled in.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
|
After Width: | Height: | Size: 42 KiB |
@ -0,0 +1,42 @@
|
||||
<sect2 id="calc-equinox">
|
||||
<title>Equinoxes and Solstices module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Equinoxes and Solstices module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Equinoxes and Solstices calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-equinox.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Equinoxes and Solstices</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The <link linkend="ai-equinox">Equinoxes</link> and
|
||||
Solstices module calculates the date and time of an
|
||||
equinox or solstice for a given year. You specify which
|
||||
event (Spring Equinox, Summer Solstice, Autumn Equinox,
|
||||
or Winter Solstice) should be investigated, and the year.
|
||||
Then press the <guibutton>Compute</guibutton> button to
|
||||
obtain the date and time of the event, and the length of
|
||||
the corresponding season, in days.
|
||||
</para>
|
||||
<para>
|
||||
There is a batch mode for this module. To use it, simply
|
||||
generate an input file whose lines each contain a year
|
||||
for which the Equinox and Solstice data will be computed.
|
||||
Then specify the input and output filenames, and press the
|
||||
<guibutton>Run</guibutton> button to generate the output
|
||||
file. Each line in the output file contains the input year,
|
||||
the date and time of each event, and the length of each
|
||||
season.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 39 KiB |
@ -0,0 +1,43 @@
|
||||
<sect2 id="calc-geodetic">
|
||||
<title>Geodetic Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Geodetic Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Geodetic Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-geodetic.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Geodetic Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The normal <link linkend="ai-geocoords">geographic coordinate
|
||||
system</link> assumes that the Earth is a perfect sphere. This is
|
||||
nearly true, so for most purposes geographic coordinates are fine.
|
||||
If very high precision is required, then we must take the true shape
|
||||
of the Earth into account. The Earth is an ellipsoid; the distance
|
||||
around the equator is about 0.3% longer than a <link
|
||||
linkend="ai-greatcircle">Great Circle</link> that passes through the
|
||||
poles. The <firstterm>Geodetic Coordinate system</firstterm> takes
|
||||
this ellipsoidal shape into account, and expresses the position
|
||||
on the Earth's surface in Cartesian coordinates (X, Y, and Z).
|
||||
</para>
|
||||
<para>
|
||||
To use the module, first select which coordinates you will use as
|
||||
input in the <guilabel>Input Selection</guilabel> section. Then, fill
|
||||
in the input coordinates in either the <guilabel>Cartesian
|
||||
Coordinates</guilabel> section or the <guilabel>Geographic
|
||||
Coordinates</guilabel> section. When you press the
|
||||
<guibutton>Compute</guibutton> button, the corresponding
|
||||
coordinates will be filled in.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 42 KiB |
@ -0,0 +1,35 @@
|
||||
<sect2 id="calc-horiz">
|
||||
<title>Horizontal Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Horizontal Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Horizontal Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-horizontal.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Horizontal Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module converts from <link linkend="equatorial">Equatorial
|
||||
coordinates</link> to <link linkend="horizontal">Horizontal
|
||||
coordinates</link>. First, select the date, time, and
|
||||
geographic coordinates for the calculation in the
|
||||
<guilabel>Input Data</guilabel> section. Then, fill in the
|
||||
equatorial coordinates to be converted and their catalog epoch
|
||||
in the <guilabel>Equatorial Coordinates</guilabel> section.
|
||||
When you press the <guibutton>Compute</guibutton> button,
|
||||
the corresponding Horizontal coordinates will be presented in
|
||||
the <guilabel>Horizontal Coordinates</guilabel> section.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
|
After Width: | Height: | Size: 51 KiB |
|
After Width: | Height: | Size: 37 KiB |
@ -0,0 +1,41 @@
|
||||
<sect2 id="calc-julian">
|
||||
<title>Julian Day module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Julian Day module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Julian Day calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-julian.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Julian Day</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module converts between the calendar date, the <link
|
||||
linkend="ai-julianday">Julian Day</link>, and the
|
||||
<firstterm>Modified Julian Day</firstterm>. The Modified Julian Day
|
||||
is simply equal to the Julian Day - 2,400,000.5.
|
||||
</para><para>
|
||||
To use the module, select which of the three dates will be the input,
|
||||
and then fill in its value. Then press the
|
||||
<guibutton>Compute</guibutton> button, and the corresponding values for
|
||||
the other two date systems will be displayed.
|
||||
</para>
|
||||
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
What calendar date does MJD = 0.0 correspond to?
|
||||
</para>
|
||||
</tip>
|
||||
|
||||
</sect2>
|
||||
@ -0,0 +1,47 @@
|
||||
<sect2 id="calc-planetcoords">
|
||||
<title>Planet Coordinates module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Planet Coordinates module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Planet Coordinates calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-planetcoords.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Planet Coordinates</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The Planet Coordinates module computes positional data for
|
||||
any major solar system body, for any time and date and any
|
||||
geographic location. Simply select the <guilabel>solar
|
||||
system body</guilabel> from the drop-down list, and specify
|
||||
the desired date, time, and geographic coordinates (these
|
||||
values are preset to the current &kstars; settings). Then
|
||||
press the <guibutton>Compute</guibutton> button to determine
|
||||
the <link linkend="equatorial">Equatorial</link>, <link
|
||||
linkend="horizontal">Horizontal</link>, and <link
|
||||
linkend="ecliptic">Ecliptic</link> coordinates of the body.
|
||||
</para>
|
||||
<para>
|
||||
There is a batch mode for this module. You must construct
|
||||
an input file in which each line specifies values for the
|
||||
input parameters (solar system body, date, time, longitude,
|
||||
and latitude). You may choose to specify a constant value
|
||||
for some of the parameters in the calculator window (these
|
||||
parameters should be skipped in the input file). You may
|
||||
also specify which of the output parameters (Equatorial,
|
||||
Horizontal, and Ecliptic coordinates) should be calculated.
|
||||
Finally, specify the input and output filenames, and press
|
||||
the <guibutton>Run</guibutton> button to generate the output
|
||||
file with the computed values.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 52 KiB |
@ -0,0 +1,37 @@
|
||||
<sect2 id="calc-precess">
|
||||
<title>Precession module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Precession module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Precession calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-precess.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Precession</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module is similar to the <link linkend="calc-apcoords">Apparent
|
||||
Coordinates module</link>, but it only applies the effect of
|
||||
<link linkend="ai-precession">precession</link>, not of nutation or
|
||||
aberration.
|
||||
</para>
|
||||
<para>
|
||||
To use the module, first enter the input coordinates and their epoch
|
||||
in the <guilabel>Original Coordinates</guilabel> section. You must
|
||||
also fill in the target epoch in the <guilabel>Precessed
|
||||
Coordinates</guilabel> section. Then, press the
|
||||
<guibutton>Compute</guibutton> button, and the object's
|
||||
coordinates, precessed to the target Epoch, are presented in the
|
||||
<guilabel>Precessed Coordinates</guilabel> section.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 47 KiB |
@ -0,0 +1,32 @@
|
||||
<sect2 id="calc-sidereal">
|
||||
<title>Sidereal Time module</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
<tertiary>Sidereal Time module</tertiary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Sidereal Time calculator module
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="calc-sidereal.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Sidereal Time</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This module converts between <link linkend="ai-utime">Universal
|
||||
Time</link> and Local <link linkend="ai-sidereal">Sidereal Time</link>.
|
||||
First, select whether you will use Universal Time or Sidereal Time
|
||||
as an input value in the <guilabel>Input Selection</guilabel> section.
|
||||
You must also specify a geographic longitude, and a date for the
|
||||
calculation, in addition to either the Universal Time or the Sidereal
|
||||
Time value. When you press the <guibutton>Compute</guibutton> button,
|
||||
the corresponding value for the other Time will be displayed.
|
||||
</para>
|
||||
</sect2>
|
||||
|
After Width: | Height: | Size: 41 KiB |
@ -0,0 +1,48 @@
|
||||
<sect1 id="tool-calculator">
|
||||
<title>The Astrocalculator</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Astrocalculator</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
The &kstars; Astrocalculator provides several modules that
|
||||
give you direct access to algorithms used by the program.
|
||||
The modules are organized by subject:
|
||||
|
||||
<itemizedlist><title>Coordinate Converters</title>
|
||||
<listitem><para><link linkend="calc-angdist">Angular Distance</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-apcoords">Apparent Coordinates</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-ecliptic">Ecliptic Coordinates</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-eqgal">Equatorial/Galactic Coordinates</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-horiz">Horizontal Coordinates</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-precess">Precession</link></para></listitem>
|
||||
</itemizedlist>
|
||||
<itemizedlist><title>Earth Coordinates</title>
|
||||
<listitem><para><link linkend="calc-geodetic">Geodetic Coordinates</link></para></listitem>
|
||||
</itemizedlist>
|
||||
<itemizedlist><title>Solar System</title>
|
||||
<listitem><para><link linkend="calc-planetcoords">Planets Coordinates</link></para></listitem>
|
||||
</itemizedlist>
|
||||
<itemizedlist><title>Time Calculators</title>
|
||||
<listitem><para><link linkend="calc-dayduration">Day Duration</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-equinox">Equinoxes and Solstices</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-julian">Julian Day</link></para></listitem>
|
||||
<listitem><para><link linkend="calc-sidereal">Sidereal Time</link></para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
&calc-angdist;
|
||||
&calc-apcoords;
|
||||
&calc-ecliptic;
|
||||
&calc-eqgal;
|
||||
&calc-horiz;
|
||||
&calc-precess;
|
||||
&calc-geodetic;
|
||||
&calc-planetcoords;
|
||||
&calc-dayduration;
|
||||
&calc-equinox;
|
||||
&calc-julian;
|
||||
&calc-sidereal;
|
||||
|
||||
</sect1>
|
||||
|
||||
@ -0,0 +1,27 @@
|
||||
<sect1 id="ai-cequator">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Celestial Equator</title>
|
||||
<indexterm><primary>Celestial Equator</primary>
|
||||
<seealso>Equatorial Coordinates</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The <firstterm>Celestial Equator</firstterm> is an imaginary <link
|
||||
linkend="ai-greatcircle">great circle</link> on the <link
|
||||
linkend="ai-csphere">celestial sphere</link>. The celestial equator
|
||||
is the fundamental plane of the <link linkend="equatorial">Equatorial
|
||||
Coordinate System</link>, so it is defined as the locus of points
|
||||
with Declination of zero degrees. It is also the projection of the
|
||||
Earth's equator onto the sky.
|
||||
</para>
|
||||
<para>
|
||||
The Celestial Equator and the <link linkend="ai-ecliptic">Ecliptic</link>
|
||||
are set at an angle of 23.5 degrees in the sky. The points where they
|
||||
intersect are the Vernal and Autumnal <link
|
||||
linkend="ai-equinox">Equinoxes</link>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 77 KiB |
@ -0,0 +1,174 @@
|
||||
<sect1 id="ai-colorandtemp">
|
||||
|
||||
<sect1info>
|
||||
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Star Colors and Temperatures</title>
|
||||
<indexterm><primary>Star Colors and Temperatures</primary>
|
||||
<seealso>Blackbody Radiation</seealso>
|
||||
<seealso>Magnitude Scale</seealso>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
Stars appear to be exclusively white at first glance.
|
||||
But if we look carefully, we can notice a range of colors: blue,
|
||||
white, red, and even gold. In the winter constellation of Orion, a
|
||||
beautiful contrast is seen between the red Betelgeuse at Orion's
|
||||
"armpit" and the blue Bellatrix at the shoulder. What causes stars to
|
||||
exhibit different colors remained a mystery until two centuries ago,
|
||||
when Physicists gained enough understanding of the nature of light and
|
||||
the properties of matter at immensely high temperatures.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Specifically, it was the physics of
|
||||
<link linkend="ai-blackbody">blackbody radiation</link> that enabled
|
||||
us to understand the variation of stellar colors. Shortly after
|
||||
blackbody radiation was understood, it was noticed that the spectra of
|
||||
stars look extremely similar to blackbody radiation curves of
|
||||
various temperatures, ranging from a few thousand Kelvin to ~50,000
|
||||
Kelvin. The obvious conclusion is that stars are similar to
|
||||
blackbodies, and that the color variation of stars is a direct
|
||||
consequence of their surface temperatures.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Cool stars (i.e., Spectral Type K and M) radiate most
|
||||
of their energy in the red and infrared region of the
|
||||
electromagnetic spectrum and thus appear red, while hot stars (i.e.,
|
||||
Spectral Type O and B) emit mostly at blue and ultra-violet
|
||||
wavelengths, making them appear blue or white.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To estimate the surface temperature of a star, we can use the known
|
||||
relationship between the temperature of a blackbody, and the
|
||||
wavelength of light where its spectrum peaks. That is, as you
|
||||
increase the temperature of a blackbody, the peak of its spectrum
|
||||
moves to shorter (bluer) wavelengths of light.
|
||||
This is illustrated in Figure 1 where the intensity of three
|
||||
hypothetical stars is plotted against wavelength. The "rainbow"
|
||||
indicates the range of wavelengths that are visible to the human eye.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="star_colors.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<caption><para><phrase>Figure 1</phrase></para></caption>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This simple method is conceptually correct, but it cannot be used to
|
||||
obtain stellar temperatures accurately, because stars are
|
||||
<emphasis>not</emphasis> perfect blackbodies. The presence of various
|
||||
elements in the star's atmosphere will cause certain wavelengths of
|
||||
light to be absorbed. Because these absorption lines are not uniformly
|
||||
distributed over the spectrum, they can skew the position of
|
||||
the spectral peak.
|
||||
Moreover, obtaining a usable spectrum of a star
|
||||
is a time-intensive process and is prohibitively inefficient for large
|
||||
samples of stars.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
An alternative method utilizes photometry to measure the intensity of
|
||||
light
|
||||
passing through different filters. Each filter allows
|
||||
<emphasis>only</emphasis> a specific part of the spectrum
|
||||
of light to pass through while rejecting all others. A widely used
|
||||
photometric system is called the <firstterm>Johnson UBV
|
||||
system</firstterm>. It employs three bandpass filters: U
|
||||
("Ultra-violet"), B ("Blue"), and V ("Visible"); each occupying different regions of the
|
||||
electromagnetic spectrum.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The process of UBV photometry involves using light sensitive devices
|
||||
(such as film or CCD cameras) and aiming a telescope at a star to
|
||||
measure the intensity of light that passes through each of the
|
||||
filters individually. This procedure gives three apparent
|
||||
brightnesses or <link linkend="ai-flux">fluxes</link> (amount of
|
||||
energy per cm^2 per second) designated by Fu, Fb, and Fv. The ratio of
|
||||
fluxes Fu/Fb and Fb/Fv is a quantitative measure of the star's
|
||||
"color", and these ratios can be used to establish a temperature scale
|
||||
for stars. Generally speaking, the larger the Fu/Fb and Fb/Fv ratios
|
||||
of a star, the hotter its surface temperature.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For example, the star Bellatrix in Orion has Fb/Fv = 1.22, indicating
|
||||
that it is brighter through the B filter than through the V filter.
|
||||
furthermore, its Fu/Fb ratio is 2.22, so it is brightest through the U
|
||||
filter. This indicates that the star must be very hot indeed, since
|
||||
the position of its spectral peak must be somewhere in the range of
|
||||
the U filter, or at an even shorter wavelength. The surface
|
||||
temperature of Bellatrix (as determined from comparing its spectrum to
|
||||
detailed models that account for its absorption lines) is about 25,000
|
||||
Kelvin.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
We can repeat this analysis for the star Betelgeuse. Its Fb/Fv and
|
||||
Fu/Fb ratios are 0.15 and 0.18, respectively, so it is brightest
|
||||
in V and dimmest in U. So, the spectral peak of Betelgeuse must be
|
||||
somewhere in the range of the V filter, or at an even longer
|
||||
wavelength. The surface temperature of Betelgeuse is only 2,400
|
||||
Kelvin.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Astronomers prefer to express star colors in terms of a difference in
|
||||
<link linkend="ai-magnitude">magnitudes</link>, rather than a ratio of
|
||||
<link linkend="ai-flux">fluxes</link>. Therefore, going back to blue
|
||||
Bellatrix we have a color index equal to
|
||||
</para>
|
||||
|
||||
<para>
|
||||
B - V = -2.5 log (Fb/Fv) = -2.5 log (1.22) = -0.22,
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Similarly, the color index for red Betelgeuse is
|
||||
</para>
|
||||
|
||||
<para>
|
||||
B - V = -2.5 log (Fb/Fv) = -2.5 log (0.18) = 1.85
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The color indices, like the <link linkend="ai-magnitude">magnitude
|
||||
scale</link>, run backward. <emphasis>Hot and blue</emphasis>
|
||||
stars have <emphasis>smaller and negative</emphasis> values of B-V
|
||||
than the cooler and redder stars.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
An Astronomer can then use the color indices for a star, after
|
||||
correcting for reddening and interstellar extinction, to obtain an accurate temperature of that star.
|
||||
The relationship between B-V and temperature is illustrated in Figure
|
||||
2.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="color_indices.png" />
|
||||
</imageobject>
|
||||
<caption><para><phrase>Figure 2</phrase></para></caption>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The Sun with surface temperature of 5,800 K has a B-V index of 0.62.
|
||||
</para>
|
||||
</sect1>
|
||||
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,379 @@
|
||||
<chapter id="config">
|
||||
<title>Configuring &kstars;</title>
|
||||
|
||||
<sect1 id="setgeo">
|
||||
<title>Setting the Geographic Location</title>
|
||||
|
||||
<para>
|
||||
Here is a screenshot of the <guilabel>Set Geographic Location</guilabel>
|
||||
window:
|
||||
<screenshot>
|
||||
<screeninfo>Changing the Geographic Location</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="geolocator.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Set Location Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
There is a list of over 2500 predefined cities available to choose from.
|
||||
You set your location by highlighting a city from this list. Each
|
||||
city is represented in the world map as a small dot, and when a city
|
||||
is highlighted in the list, a red crosshairs appears on its location
|
||||
in the map.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Geographic Location Tool</primary>
|
||||
<secondary>Filtering</secondary></indexterm>
|
||||
It is not practical to scroll through the full list of 2500 locations,
|
||||
looking for a specific city. To make searches easier, the list can be
|
||||
filtered by entering text in the boxes below the map. For example, in
|
||||
the screenshot, the text <quote>Ba</quote> appears in the
|
||||
<guilabel>City Filter</guilabel> box, while <quote>M</quote> has been
|
||||
entered in the <guilabel>Province Filter</guilabel> box, and
|
||||
<quote>USA</quote> is in the <guilabel>Country Filter</guilabel>
|
||||
box. Note that all of the cities displayed in the list have city,
|
||||
province, and country names that begin with the entered filter
|
||||
strings, and that the message below the filter boxes indicates that 7
|
||||
cities are matched by the filters. Also notice that the dots
|
||||
representing these seven cities in the map have been colored white,
|
||||
while the unmatched cities remain gray.
|
||||
</para><para>
|
||||
The list can also be filtered by location in the map. Clicking anywhere
|
||||
in the world map will show only those cities within two degrees of the
|
||||
clicked location. At this time, you can search by name, or by location,
|
||||
but not both at once. In other words, when you click on the map, the
|
||||
name filters are ignored, and vice versa.
|
||||
</para><para>
|
||||
<indexterm><primary>Geographic Location Tool</primary>
|
||||
<secondary>Custom locations</secondary></indexterm>
|
||||
The <link linkend="ai-geocoords">longitude, latitude</link> and
|
||||
<link linkend="ai-timezones">time zone</link> information for the
|
||||
currently-selected location are displayed in the boxes at the bottom of
|
||||
the window. If you feel that any of these values are inaccurate, you
|
||||
can modify them and press the <guibutton>Add to List</guibutton> button
|
||||
to record your custom version of the location. You can also define a
|
||||
completely new location by pressing the
|
||||
<guibutton>Clear Fields</guibutton> button, and entering the data for
|
||||
the new location. Note that all fields except the optional
|
||||
<guilabel>State/Province</guilabel> must be filled before the new
|
||||
location can be added to the list. &kstars; will automatically load
|
||||
your custom locations for all future sessions. Please note, at this
|
||||
point, the only way to remove a custom location is to remove the
|
||||
appropriate line from the file
|
||||
<filename>~/.kde/share/apps/kstars/mycities.dat</filename>.
|
||||
</para><para>
|
||||
If you add custom locations (or modify existing ones), please send us
|
||||
your <filename>mycities.dat</filename> file so that we can add your
|
||||
locations to the master list.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="settime">
|
||||
<title>Setting the Time</title>
|
||||
<para>
|
||||
<indexterm><primary>Date and Time</primary>
|
||||
<secondary>The simulation clock</secondary></indexterm>
|
||||
When &kstars; starts up, the time is set to your computer's system
|
||||
clock, and the &kstars; clock is running to keep up with the real time.
|
||||
If you want to stop the clock, select <guimenuitem>Stop
|
||||
Clock</guimenuitem> from the <guimenu>Time</guimenu> menu, or simply
|
||||
click on the <guiicon>Pause</guiicon> icon in the toolbar. You can
|
||||
make the clock run slower or faster than normal, or even make it run
|
||||
backward, using the time-step spinbox in the toolbar. This spinbox
|
||||
has two sets of up/down buttons. The first one will step through all
|
||||
83 available time steps, one by one. The second one will skip to the
|
||||
next higher (or lower) unit of time, which allows you to make large
|
||||
timestep changes more quickly.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Date and Time</primary>
|
||||
<secondary>Setting</secondary></indexterm>
|
||||
You can set the time and date by selecting <guimenuitem>Set
|
||||
Time...</guimenuitem> from the <guimenu>Time</guimenu> menu, or by
|
||||
pressing the <guiicon>time</guiicon> icon in the toolbar. The
|
||||
<guilabel>Set Time</guilabel> window uses a standard &kde; Date Picker
|
||||
widget, coupled with three spinboxes for setting the hours, minutes and
|
||||
seconds. If you want to re-synchronize the simulation clock back to the
|
||||
current CPU time, just select <guimenuitem>Set Time to Now</guimenuitem>
|
||||
from the <guimenu>Time</guimenu> menu.</para>
|
||||
|
||||
<note><para>
|
||||
<indexterm><primary>Date and Time</primary>
|
||||
<secondary>Extended range of dates</secondary></indexterm>
|
||||
&kstars; can accept very remote dates beyond the usual limits imposed by
|
||||
QDate. Currently, you can set the date between the years -50000 and +50000.
|
||||
We may extend this range even further in future releases. However, please
|
||||
be aware that the accuracy of the simulation becomes more and more degraded
|
||||
as more remote dates are examined. This is especially true for the positions
|
||||
of solar system bodies.
|
||||
</para></note>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="viewops">
|
||||
<title>The Configure &kstars; Window</title>
|
||||
<para>
|
||||
<indexterm><primary>Configure &kstars; window</primary></indexterm>
|
||||
The <guilabel>Configure &kstars;</guilabel> window allows you to modify
|
||||
a wide range of display options. You can access the window with the
|
||||
<guiicon>configure</guiicon> toolbar icon, or by selecting
|
||||
<guimenuitem>Configure &kstars;...</guimenuitem> from the
|
||||
<guimenu>Settings</guimenu> menu.
|
||||
The window is depicted below:
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Configure &kstars; Window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="viewops.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Configure &kstars; Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The <guilabel>Configure &kstars;</guilabel> window is divided into five
|
||||
tabs:
|
||||
<guilabel>Catalogs</guilabel>, <guilabel>Guides</guilabel>,
|
||||
<guilabel>Solar System</guilabel>, <guilabel>Colors</guilabel>, and
|
||||
<guilabel>Advanced</guilabel>.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Configure &kstars; window</primary>
|
||||
<secondary>Catalogs Tab</secondary></indexterm>
|
||||
In the <guilabel>Catalogs</guilabel> tab, you determine which object
|
||||
catalogs are displayed in the map. The <guilabel>Stars</guilabel> section
|
||||
also allows you to set the
|
||||
<quote>faint <link linkend="ai-magnitude">magnitude</link> limit</quote>
|
||||
for stars, and the <link linkend="ai-magnitude">magnitude</link> limit for
|
||||
displaying the names and/or magnitudes of stars. Below the stars section,
|
||||
the <guilabel>Deep-Sky Objects</guilabel> section controls the display of
|
||||
several non-stellar object catalogs. By default, the list includes the
|
||||
Messier, NGC and IC catalogs. You can add your own custom object catalogs
|
||||
by pressing the <guibutton>Add Custom Catalog</guibutton> button. For
|
||||
detailed instructions on preparing a catalog data file, see the
|
||||
<filename>README.customize</filename> file that ships with &kstars;.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Configure &kstars; window</primary>
|
||||
<secondary>Solar System Tab</secondary></indexterm>
|
||||
In the <guilabel>Solar System</guilabel> tab, you can specify whether
|
||||
the Sun, Moon, planets, comets and asteroids are displayed, and
|
||||
whether the major bodies are drawn as colored circles or actual images.
|
||||
You can also toggle whether solar system bodies have name labels attached,
|
||||
and control how many of the comets and asteroids get name labels.
|
||||
There is an option to automatically attach a temporary <quote>orbit
|
||||
trail</quote> whenever a solar system body is tracked, and another to
|
||||
toggle whether the color of the orbit trail fades into the background
|
||||
sky color.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Configure &kstars; window</primary>
|
||||
<secondary>Guides Tab</secondary></indexterm>
|
||||
The <guilabel>Guides</guilabel> tab lets you toggle whether non-objects
|
||||
are displayed (&ie;, constellation lines, constellation names, the
|
||||
Milky Way contour, the <link linkend="ai-cequator">celestial
|
||||
equator</link>, <link linkend="ai-ecliptic">the ecliptic</link>, <link
|
||||
linkend="ai-horizon">the horizon line</link>, and the opaque ground).
|
||||
You can also choose whether you would like to see Latin constellation
|
||||
names, <acronym>IAU</acronym>-standard three-letter abbreviations, or
|
||||
constellation names using your local language.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Configure &kstars; window</primary>
|
||||
<secondary>Colors Tab</secondary></indexterm>
|
||||
<indexterm><primary>Color Schemes</primary>
|
||||
<secondary>Customizing</secondary></indexterm>
|
||||
The <guilabel>Colors</guilabel> tab allows you to set the color scheme,
|
||||
and to define custom color schemes. The tab is split into two panels:
|
||||
</para>
|
||||
<para>
|
||||
The left panel shows a list of all display items with adjustable
|
||||
colors. Click on any item to bring up a color selection window to
|
||||
adjust its color. Below the list is the <guilabel>Star Color
|
||||
Mode</guilabel> selection box. By default, &kstars; draws stars with
|
||||
a <link linkend="ai-colorandtemp">realistic color</link> tint according
|
||||
to the spectral type of the star. However, you may also choose to draw
|
||||
the stars as solid white, black or red circles. If you are using the
|
||||
realistic star colors, you can set the saturation level of the star
|
||||
colors with the <guilabel>Star Color Intensity</guilabel> spinbox.
|
||||
</para>
|
||||
<para>
|
||||
The right panel lists the defined color schemes. There are four
|
||||
predefined schemes: the <guilabel>Default</guilabel> scheme,
|
||||
<guilabel>Star Chart</guilabel>, which uses black stars on a white
|
||||
background, <guilabel>Night Vision</guilabel>, which uses only shades
|
||||
of red in order to protect dark-adapted vision, and <guilabel>Moonless
|
||||
Night</guilabel>, a more realistic, dark theme. Additionally,
|
||||
you can save the current color settings as a custom scheme by clicking
|
||||
the <guibutton>Save Current Colors</guibutton> button. It will prompt
|
||||
you for a name for the new scheme, and then your scheme will appear in
|
||||
the list in all future &kstars; sessions. To remove a custom scheme,
|
||||
simply highlight it in the list, and press the <guibutton>Remove Color
|
||||
Scheme</guibutton> button.
|
||||
</para><para>
|
||||
<indexterm><primary>Configure &kstars; window</primary>
|
||||
<secondary>Advanced Tab</secondary></indexterm>
|
||||
The <guilabel>Advanced</guilabel> Tab provides fine-grained control
|
||||
over the more subtle behaviors of &kstars;.
|
||||
</para><para>
|
||||
<indexterm><primary>Atmospheric Refraction</primary></indexterm>
|
||||
The <guilabel>Correct for atmospheric refraction</guilabel> checkbox
|
||||
controls whether the positions of objects are corrected for the effects
|
||||
of the atmosphere. Because the atmosphere is a spherical shell, light from
|
||||
outer space is <quote>bent</quote> as it passes through the atmosphere to
|
||||
our telescopes or eyes on the Earth's surface. The effect is largest for
|
||||
objects near the horizon, and actually changes the predicted rise or set
|
||||
times of objects by a few minutes. In fact, when you <quote>see</quote> a
|
||||
sunset, the Sun's actual position is already well below the horizon;
|
||||
atmospheric refraction makes it seem as if the Sun is still in the sky.
|
||||
Note that atmospheric refraction is never applied if you are using
|
||||
<guilabel>Equatorial coordinates</guilabel>.
|
||||
</para><para>
|
||||
<indexterm><primary>Animated Slewing</primary></indexterm>
|
||||
The <guilabel>Use animating slewing</guilabel> checkbox controls how the
|
||||
display changes when a new focus position is selected in the map. By
|
||||
default, you will see the sky drift or <quote>slew</quote> to the new
|
||||
position; if you uncheck this option, then the display will instead
|
||||
<quote>snap</quote> immediately to the new focus position.
|
||||
</para><para>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Labeling</secondary>
|
||||
<tertiary>Automatic</tertiary>
|
||||
</indexterm>
|
||||
If the <guilabel>Attach label to centered object</guilabel> checkbox is
|
||||
selected, then a name label will automatically be attached to an object
|
||||
when it is being tracked by the program. The label will be removed when
|
||||
the object is no longer being tracked. Note that you can also manually
|
||||
attach a persistent name label to any object with its <link
|
||||
linkend="popup-menu">popup menu</link>.
|
||||
</para><para>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Hiding</secondary></indexterm>
|
||||
There are three situations when &kstars; must redraw the sky display very
|
||||
rapidly: when a new focus position is selected (and <guilabel>Use
|
||||
animated slewing</guilabel> is checked), when the sky is dragged with the
|
||||
mouse, and when the time step is large. In these situations, the positions
|
||||
of all objects must be recomputed as rapidly as possible, which can put
|
||||
a large load on the <abbrev>CPU</abbrev>. If the <abbrev>CPU</abbrev>
|
||||
cannot keep up with the demand, then the display will seem sluggish or jerky.
|
||||
To mitigate this, &kstars; will hide certain objects during these rapid-redraw
|
||||
situations, as long as the <guilabel>Hide objects while moving</guilabel>
|
||||
checkbox is selected. The timestep threshold above which objects will be
|
||||
hidden is determined by the <guilabel>Also hide if timescale greater
|
||||
than:</guilabel> timestep-spinbox. You can specify the objects that should
|
||||
be hidden in the <guilabel>Configure Hidden Objects</guilabel> group box.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="customize">
|
||||
<title>Customizing the Display</title>
|
||||
|
||||
<para>
|
||||
There are several ways to modify the display to your liking.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
<indexterm><primary>Color Schemes</primary><secondary>Selecting</secondary></indexterm>
|
||||
Select a different color scheme in the
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Color Schemes</guimenuitem></menuchoice>
|
||||
menu. There are four predefined color schemes, and you can define your own in the
|
||||
<link linkend="config"><guilabel>Configure &kstars;</guilabel></link> window.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<indexterm><primary>Toolbars</primary>
|
||||
<secondary>Customizing</secondary></indexterm>
|
||||
Toggle whether the Toolbars are drawn in the
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Toolbars</guimenuitem></menuchoice>
|
||||
menu. Like most KDE toolbars, they can also be dragged around and
|
||||
anchored on any window edge, or even detached from the window completely.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<indexterm><primary>Info Boxes</primary><secondary>Customizing</secondary></indexterm>
|
||||
<indexterm><primary>Info Boxes</primary><secondary>Shading</secondary></indexterm>
|
||||
Toggle whether the Info Boxes are drawn in the
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Info Boxes</guimenuitem></menuchoice>
|
||||
menu. In addition, you can manipulate the three Info Boxes with the
|
||||
mouse. Each box has additional lines of data that are hidden by default.
|
||||
You can toggle whether these additional lines are visible by double-clicking
|
||||
a box to <quote>shade</quote> it. Also, you can reposition a box by
|
||||
dragging it with the mouse. When a box hits a window edge, it will
|
||||
<quote>stick</quote> to the edge when the window is resized.
|
||||
</para></listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<indexterm><primary>Field-of-View Symbols</primary><secondary>Description</secondary></indexterm>
|
||||
Choose an <quote>FOV Symbol</quote> using the
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>FOV Symbols</guimenuitem></menuchoice>
|
||||
menu. <firstterm>FOV</firstterm> is an acronym for <quote>field-of-view</quote>.
|
||||
An FOV symbol is drawn at the center of the window to indicate where the display
|
||||
is pointing. Different symbols have different angular sizes; you can use a symbol to show
|
||||
what the view through a particular telescope would look like. For example, if you choose
|
||||
the <quote>7x35 Binoculars</quote> FOV symbol, then a circle is drawn on the display that is
|
||||
9.2 degrees in diameter; this is the field-of-view for 7x35 binoculars.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Field-of-View Symbols</primary><secondary>Customizing</secondary></indexterm>
|
||||
You can define your own FOV symbols (or modify the existing symbols) using the
|
||||
<guimenuitem>Edit FOV Symbols...</guimenuitem> menu item, which launches the FOV Editor:
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Field-of-View Symbols Editor</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="fovdialog.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>FOV Symbol Editor</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The list of defined FOV symbols is displayed on the left. On the right are buttons for
|
||||
adding a new symbol, editing the highlighted symbol's properties, and removing the
|
||||
highlighted symbol from the list. Note that you can even modify or remove the four
|
||||
predefined symbols (if you remove all symbols, the four defaults will be restored the
|
||||
next time you start &kstars;). Below these three buttons is a graphical preview display
|
||||
showing the highlighted symbol from the list. When the <guibutton>New...</guibutton> or
|
||||
<guibutton>Edit...</guibutton> button is pressed, the <guilabel>New FOV Symbol</guilabel>
|
||||
window is opened:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>New Field-of-View Symbol</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="newfov.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>New FOV Symbol</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
<indexterm><primary>Field-of-View Symbols</primary><secondary>Defining New</secondary></indexterm>
|
||||
This window lets you modify the four properties that define a FOV symbol: name, size,
|
||||
shape, and color. The angular size for the symbol can either be entered directly in the
|
||||
<guilabel>Field of View</guilabel> edit box, or you can use the Eyepiece/Camera Tabs to
|
||||
calculate the field-of-view angle, given parameters of your telescope/eyepiece or
|
||||
telescope/camera setup. The four available shapes are: Circle, Square, Crosshairs, and
|
||||
Bullseye. Once you have specified all four parameters, press <guibutton>Ok</guibutton>,
|
||||
and the symbol will appear in the list of defined symbols. It will also be available
|
||||
from the <guimenu>Settings</guimenu> | <guisubmenu>FOV</guisubmenu> menu.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,58 @@
|
||||
<sect1 id="ai-cpoles">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Celestial Poles</title>
|
||||
<indexterm><primary>Celestial Poles</primary>
|
||||
<seealso>Equatorial Coordinates</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The sky appears to drift overhead from east to west, completing a full circuit
|
||||
around the sky in 24 (<link linkend="ai-sidereal">Sidereal</link>) hours. This
|
||||
phenomenon is due to the spinning of the Earth on its axis. The Earth's
|
||||
spin axis intersects the <link linkend="ai-csphere">Celestial Sphere</link> at
|
||||
two points. These points are the <firstterm>Celestial Poles</firstterm>. As the
|
||||
Earth spins; they remain fixed in the sky, and all other points seem to rotate
|
||||
around them. The celestial poles are also the poles of the <link
|
||||
linkend="equatorial">Equatorial Coordinate System</link>, meaning
|
||||
they have <firstterm>Declinations</firstterm> of +90 degrees and -90 degrees
|
||||
(for the North and South celestial poles, respectively).
|
||||
</para><para>
|
||||
The North Celestial Pole currently has nearly the same coordinates as
|
||||
the bright star <firstterm>Polaris</firstterm> (which is Latin for <quote>Pole Star</quote>).
|
||||
This makes Polaris useful for navigation: not only is it always above the North
|
||||
point of the horizon, but its <link
|
||||
linkend="horizontal">Altitude</link> angle is always (nearly)
|
||||
equal to the observer's <link linkend="ai-geocoords">Geographic Latitude</link>
|
||||
(however, Polaris can only be seen from locations in the Northern hemisphere).
|
||||
</para><para>
|
||||
The fact that Polaris is near the pole is purely a coincidence. In fact,
|
||||
because of <link linkend="ai-precession">Precession</link>, Polaris is only near
|
||||
the pole for a small fraction of the time.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercises:</para>
|
||||
<para>
|
||||
Use the <guilabel>Find Object</guilabel> window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo>) to locate
|
||||
Polaris. Notice that its Declination is almost (but not exactly) +90 degrees.
|
||||
Compare the Altitude reading when focused on Polaris to your location's
|
||||
geographic latitude. They are always within one degree of each other.
|
||||
They are not exactly the same because Polaris isn't exactly at the Pole.
|
||||
(you can point exactly at the pole by switching to Equatorial
|
||||
coordinates, and pressing the up-arrow key until the sky stops scrolling).
|
||||
</para><para>
|
||||
Use the <guilabel>Time Step</guilabel> spinbox in the toolbar to accelerate time
|
||||
to a
|
||||
step of 100 seconds. You can see the entire sky appears to rotate around
|
||||
Polaris, while Polaris itself remains nearly stationary.
|
||||
</para><para>
|
||||
We said that the celestial pole is the pole of the Equatorial coordinate
|
||||
system. What do you think is the pole of the horizontal (Altitude/Azimuth)
|
||||
coordinate system? (The <link linkend="ai-zenith">Zenith</link>).
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,75 @@
|
||||
<chapter id="credits">
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>&kstars;</para>
|
||||
<para>
|
||||
Program copyright 2001-2003 The &kstars; Team <email>kstars@30doradus.org</email>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The &kstars; Team:
|
||||
<itemizedlist>
|
||||
<listitem><para>Jason Harris <email>kstars@30doradus.org</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Jasem Mutlaq <email>mutlaqja@ku.edu</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Pablo de Vicente <email>pvicentea@wanadoo.es</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Heiko Evermann <email>heiko@evermann.de</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Thomas Kabelmann <email>tk78@gmx.de</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Mark Hollomon <email>mhh@mindspring.com</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Carsten Niehaus <email>cniehaus@gmx.de</email></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Data Sources:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Object catalogs and planet position tables: <ulink
|
||||
url="http://adc.gsfc.nasa.gov">NASA Astronomical Data Center</ulink></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Detailed credit information for all of the images used in the program
|
||||
is presented in the file README.images
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
References:
|
||||
<itemizedlist>
|
||||
<listitem><para><quote>Practical Astronomy With Your
|
||||
Calculator</quote> by Peter Duffet-Smith</para></listitem>
|
||||
<listitem><para><quote>Astronomical Algorithms</quote> by Jean
|
||||
Meeus</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para> Special thanks: To the &kde; and &Qt; developers for providing
|
||||
the world with a peerless set of free <acronym>API</acronym>
|
||||
libraries. To the <application>KDevelop</application> team, for their
|
||||
excellent <acronym>IDE</acronym>, which made developing &kstars; so
|
||||
much easier and more fun. To everyone on the
|
||||
<application>KDevelop</application> message board, the &kde;
|
||||
mailing lists, and on irc.kde.org, for answering our frequent
|
||||
questions. Thank you to Anne-Marie Mahfouf, for inviting &kstars; to
|
||||
join the &kde;-Edu module. Finally, thanks to everyone who has
|
||||
submitted bug reports and other feedback. Thank you, everyone.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2001-2003 Jason Harris and the KStars Team
|
||||
<email>kstars@30doradus.org</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,28 @@
|
||||
<sect1 id="ai-csphere">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Celestial Sphere</title>
|
||||
<indexterm><primary>Celestial Sphere</primary>
|
||||
<seealso>Celestial Coordinate Systems</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The celestial sphere is an imaginary sphere of gigantic radius, centered
|
||||
on the Earth. All objects which can be seen in the sky can be thought
|
||||
of as lying on the surface of this sphere.
|
||||
</para><para>
|
||||
Of course, we know that the objects in the sky are not on the surface of
|
||||
a sphere centered on the Earth, so why bother with such a construct?
|
||||
Everything we see in the sky is so very far away, that their distances
|
||||
are impossible to gauge just by looking at them. Since their distances
|
||||
are indeterminate, you only need to know the <emphasis>direction</emphasis>
|
||||
toward the object to locate it in the sky. In this sense, the celestial sphere
|
||||
model is a very practical model for mapping the sky.
|
||||
</para><para>
|
||||
The directions toward various objects in the sky can be quantified by
|
||||
constructing a <link linkend="ai-skycoords">Celestial Coordinate System</link>.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,119 @@
|
||||
<sect1 id="ai-darkmatter">
|
||||
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Dark Matter</title>
|
||||
<indexterm><primary>Dark Matter</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
Scientists are now quite comfortable with the idea that 90% of the
|
||||
mass is the universe is in a form of matter that cannot be seen.
|
||||
</para>
|
||||
|
||||
<para> Despite comprehensive maps of the nearby universe that cover
|
||||
the spectrum from radio to gamma rays, we are only able to account of
|
||||
10% of the mass that must be out there. As Bruce H. Margon, an
|
||||
astronomer at the University of Washington, told the New York Times in
|
||||
2001: <citation>It's a fairly embarrassing situation to admit that we
|
||||
can't find 90 percent of the universe</citation>. </para>
|
||||
|
||||
<para> The term given this <quote>missing mass</quote> is
|
||||
<firstterm>Dark Matter</firstterm>, and those two words pretty well
|
||||
sum up everything we know about it at this point. We know there is
|
||||
<quote>Matter</quote>, because we can see the effects of its
|
||||
gravitational influence. However, the matter emits no detectable
|
||||
electromagnetic radiation at all, hence it is <quote>Dark</quote>.
|
||||
There exist several theories to account for the missing mass ranging
|
||||
from exotic subatomic particles, to a population of isolated black
|
||||
holes, to less exotic brown and white dwarfs. The term <quote>missing
|
||||
mass</quote> might be misleading, since the mass itself is not
|
||||
missing, just its light. But what is exactly dark matter and how do
|
||||
we really know it exists, if we cannot see it? </para>
|
||||
|
||||
<para>
|
||||
The story began in 1933 when Astronomer Fritz Zwicky was studying the
|
||||
motions of distant and massive clusters of galaxies, specifically the
|
||||
Coma cluster and the Virgo cluster. Zwicky estimated the mass of each
|
||||
galaxy in the cluster based on their luminosity, and added up all of
|
||||
the galaxy masses to get a total cluster mass. He then made a second,
|
||||
independent estimate of the cluster mass, based on measuring the
|
||||
spread in velocities of the individual galaxies in the cluster.
|
||||
To his suprise, this second <firstterm>dynamical mass</firstterm>
|
||||
estimate was <emphasis>400 times</emphasis> larger than the estimate
|
||||
based on the galaxy light.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Although the evidence was strong at Zwicky's time, it was not until
|
||||
the 1970s that scientists began to explore this discrepancy
|
||||
comprehensively. It was at this time that the existence of Dark
|
||||
Matter began to be taken seriously. The existence of such matter
|
||||
would not only resolve the mass deficit in galaxy clusters; it
|
||||
would also have far more reaching consequences for the evolution and
|
||||
fate of the universe itself.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Another phenomenon that suggested the need for dark matter is the
|
||||
rotational curves of <firstterm>Spiral Galaxies</firstterm>. Spiral Galaxies
|
||||
contain a large population of stars that orbit the Galactic center on
|
||||
nearly circular orbits, much like planets orbit a star. Like
|
||||
planetary orbits, stars with larger galactic orbits are expected to
|
||||
have slower orbital speeds (this is just a statement of Kepler's 3rd Law).
|
||||
Actually, Kepler's 3rd Law only applies to stars near the perimeter of a Spiral
|
||||
Galaxy, because it assumes the mass enclosed by the orbit to be
|
||||
constant.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
However, astronomers have made observations of the orbital speeds of
|
||||
stars in the outer parts of a large number of spiral galaxies, and
|
||||
none of them follow Kepler's 3rd Law as expected. Instead of falling
|
||||
off at larger radii, the orbital speeds remain remarkably constant.
|
||||
The implication is that the mass enclosed by larger-radius orbits
|
||||
increases, even for stars that are apparently near the edge of the
|
||||
galaxy. While they are near the edge of the luminous part of the
|
||||
galaxy, the galaxy has a mass profile that apparently continues well
|
||||
beyond the regions occupied by stars.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Here is another way to think about it: Consider the stars near the
|
||||
perimeter of a spiral galaxy, with typical observed orbital
|
||||
velocities of 200 kilometers per second. If the galaxy consisted of
|
||||
only the matter that we can see, these stars would very quickly fly
|
||||
off from the galaxy, because their orbital speeds are four times
|
||||
larger than the galaxy's escape velocity. Since galaxies are not seen
|
||||
to be spinning apart, there must be mass in the galaxy that we are not
|
||||
accounting for when we add up all the parts we can see.
|
||||
</para>
|
||||
|
||||
<para> Several theories have surfaced in literature to account for the
|
||||
missing mass such as <acronym>WIMP</acronym>s (Weakly Interacting
|
||||
Massive Particles), <acronym>MACHO</acronym>s (MAssive Compact Halo
|
||||
Objects), primordial black holes, massive neutrinos, and others; each
|
||||
with their pros and cons. No single theory has yet been accepted by
|
||||
the astronomical community, because we so far lack the means to
|
||||
conclusively test one theory against the other. </para>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
You can see the galaxy clusters that Professor Zwicky studied to
|
||||
discover Dark Matter. Use the &kstars; Find Object Window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo>) to
|
||||
center on <quote>M 87</quote> to find the Virgo Cluster, and on
|
||||
<quote>NGC 4884</quote> to find the Coma Cluster. You may have to
|
||||
zoom in to see the galaxies. Note that the Virgo Cluster appears to
|
||||
be much larger on the sky. In reality, Coma is the larger cluster;
|
||||
it only appears smaller because it is further away.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,229 @@
|
||||
<chapter id="dcop">
|
||||
<title>Scripting KStars: The DCOP Interface</title>
|
||||
<para>
|
||||
One of the goals of &kstars; is to provide the ability to playback
|
||||
complicated behaviors from a script. This will allow you to
|
||||
create <quote>virtual tours</quote> of the heavens, and will enable
|
||||
teachers to construct classroom demos to illustrate certain
|
||||
astronomical concepts. It is already possible to write such scripts
|
||||
for &kstars;, although not all of the desired functions have been
|
||||
included. Also, while we will eventually have a GUI-based script
|
||||
builder tool, the scripts must currently be written by hand. This
|
||||
chapter will explain how to write &kstars; scripts.
|
||||
</para>
|
||||
<para>
|
||||
The &kde; architecture provides the necessary framework for scriptable
|
||||
applications via the <abbrev>DCOP</abbrev> interface.
|
||||
<abbrev>DCOP</abbrev> stands for <quote>Desktop Communication
|
||||
Protocol</quote>; through <abbrev>DCOP</abbrev>, &kde; applications
|
||||
can be controlled by other applications, from a terminal prompt, or
|
||||
through a text script.
|
||||
</para>
|
||||
|
||||
<sect1 id="dcop-interface">
|
||||
<title>DCOP Functions</title>
|
||||
<para>
|
||||
The &kstars; <abbrev>DCOP</abbrev> Interface includes the following
|
||||
functions:
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><function>
|
||||
lookTowards( const QString direction )</function>:
|
||||
Point the display focus in a direction specified by the argument.
|
||||
This can be the name of any object in the sky, or one of the following
|
||||
directional words or abbreviations: zenith (or z), north (n),
|
||||
northeast (ne), east (e), southeast (se), south (s), southwest(sw),
|
||||
west(w), northwest (nw).
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setRaDec( double ra, double dec )</function>:
|
||||
Point the display focus at the specified equatorial coordinates.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setAltAz(double alt, double az)</function>:
|
||||
Point the display focus at the specified horizontal coordinates.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
zoomIn()</function>:
|
||||
Increase the display's Zoom level.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
zoomOut()</function>:
|
||||
Decrease the display's Zoom level.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
defaultZoom()</function>:
|
||||
Reset the display to Zoom level = 3 (the default).
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setLocalTime(int yr, int mth, int day, int hr, int min, int sec)</function>:
|
||||
Set the simulation clock to the specified date and time.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
waitFor( double t )</function>:
|
||||
Pause for t seconds before continuing with subsequent script commands.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
waitForKey( const QString k )</function>:
|
||||
Halt the script execution until the user presses the specified key.
|
||||
At this point, you cannot specify combination keystrokes (such as
|
||||
<keycombo action="simul">&Ctrl;<keycap>C</keycap></keycombo>); just use
|
||||
simple keys. You can type <quote>space</quote> to indicate the
|
||||
spacebar.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setTracking( bool track )</function>:
|
||||
Toggle whether tracking mode is engaged.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
changeViewOption( const QString option, const QString value )</function>:
|
||||
Adjust a view option. There are dozens and dozens of options available;
|
||||
basically everything you can change in the <guilabel>Configure &kstars;
|
||||
Window</guilabel> can be changed here as well. The first argument is
|
||||
the name of the option (the names are taken from the
|
||||
<filename>kstarsrc</filename> configuration file), and the second
|
||||
argument is the desired value. The argument parser is designed to be
|
||||
robust, so if you accidentally send it bad data it should fail
|
||||
gracefully.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setGeoLocation( const QString city, const QString province,
|
||||
const QString country )</function>:
|
||||
Change the observing location to the specified city. If no city matching
|
||||
the argument strings is found, then nothing happens.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
stop()</function> [clock]:
|
||||
Halt the simulation clock.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
start()</function> [clock]:
|
||||
Start the simulation clock.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para><function>
|
||||
setScale(float s)</function> [clock]:
|
||||
Set the rate of the simulation clock. s=1.0 corresponds to real time;
|
||||
2.0 is twice as fast as real-time, etc.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="dcop-test">
|
||||
<title>Testing the DCOP Functions</title>
|
||||
<para>
|
||||
You can try out the DCOP functions very easily using the
|
||||
<application>kdcop</application> program. When you run
|
||||
<application>kdcop</application>, you will see a tree-list of all
|
||||
running programs; if &kstars; is running it will be listed. Most of
|
||||
the <abbrev>DCOP</abbrev> functions are listed under the
|
||||
<quote>KStarsInterface</quote> heading, but the clock functions are
|
||||
listed under <quote>clock</quote>. Double-click on any function to
|
||||
execute it. If the function requires arguments, a window will open
|
||||
in which you can input the values.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="dcop-script">
|
||||
<title>Writing a DCOP Script</title>
|
||||
<para>
|
||||
<abbrev>DCOP</abbrev> functions can also be called from the UNIX
|
||||
command line, and these can be encapsulated in a script. We will
|
||||
create an example script that switches to Equatorial coordinates,
|
||||
points the display at the Moon, zooms in a bit, and accelerates
|
||||
the clock to 1 hour per second. After tracking the Moon
|
||||
for 20 seconds, the clock is paused and the display zooms out.
|
||||
You can use this script as a template for making new scripts.
|
||||
I will list the entire script first, and then explain its various
|
||||
parts.
|
||||
</para>
|
||||
<para>
|
||||
<programlisting>
|
||||
#!/bin/bash
|
||||
#KStars script: Track the Moon!
|
||||
#
|
||||
KSTARS=`dcopfind -a 'kstars*'`
|
||||
MAIN=KStarsInterface
|
||||
CLOCK=clock#1
|
||||
dcop $KSTARS $MAIN changeViewOption UseAltAz false
|
||||
dcop $KSTARS $MAIN lookTowards Moon
|
||||
dcop $KSTARS $MAIN defaultZoom
|
||||
dcop $KSTARS $MAIN zoomIn
|
||||
dcop $KSTARS $MAIN zoomIn
|
||||
dcop $KSTARS $MAIN zoomIn
|
||||
dcop $KSTARS $MAIN zoomIn
|
||||
dcop $KSTARS $MAIN zoomIn
|
||||
dcop $KSTARS $CLOCK setScale 3600.
|
||||
dcop $KSTARS $CLOCK start
|
||||
dcop $KSTARS $MAIN waitFor 20.
|
||||
dcop $KSTARS $CLOCK stop
|
||||
dcop $KSTARS $MAIN defaultZoom
|
||||
##
|
||||
</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
Save this script to a file. The filename can be anything you like; I
|
||||
suggest something descriptive like
|
||||
<filename>trackmoon.kstars</filename>. Then type the following command
|
||||
to make the script executable:
|
||||
<userinput><command>chmod</command> <option>a+x</option>
|
||||
<parameter>trackmoon.kstars</parameter>
|
||||
</userinput>. The script can then be executed at any time by typing
|
||||
<userinput><command>./trackmoon.kstars</command></userinput> in the
|
||||
folder which contains the script. Note that the script will only
|
||||
work if an instance of &kstars; is already running. You can use the
|
||||
<command>dcopstart</command> command in a script to launch a new instance
|
||||
&kstars;.
|
||||
</para>
|
||||
<para>
|
||||
Now to the explanation of the script. The top line identifies the file
|
||||
as a <command>BASH</command> shell script. The following two lines
|
||||
are <firstterm>comments</firstterm> (any line beginning with
|
||||
<quote>#</quote> is a comment, and is ignored by the shell). The next
|
||||
three lines define some convenience variables that will be used later.
|
||||
The <varname>KSTARS</varname> variable identifies the currently-running
|
||||
&kstars; process, using the <command>dcopfind</command> command.
|
||||
<varname>MAIN</varname> and <varname>CLOCK</varname> identify the
|
||||
two <abbrev>DCOP</abbrev> interfaces associated with &kstars;.
|
||||
</para>
|
||||
<para>
|
||||
The remainder of the script is the actual list of <abbrev>DCOP</abbrev>
|
||||
calls. The first command sets the display to use Equatorial
|
||||
coordinates by setting the <quote>UseAltAz</quote> option to
|
||||
<quote>false</quote> (again, you can see a list of all options that
|
||||
<quote>changeViewOption</quote> can use by examining your
|
||||
<filename>kstarsrc</filename> configuration file). The next command
|
||||
centers the display on the Moon, and automatically engages tracking.
|
||||
We then set the default zoom level, and then zoom in five times.
|
||||
Next, the clock's timescale is set to 1 hour per second (3600 seconds
|
||||
is one hour), and the clock is started (in case it was not already
|
||||
running). The next line pauses the script for 20 seconds while we
|
||||
track the Moon as it moves across the sky. Finally, we stop the clock
|
||||
and reset the zoom level to its default setting.
|
||||
</para>
|
||||
<para>
|
||||
We hope you enjoy the scripting abilities of KStars. If you create an
|
||||
interesting script, please email it to
|
||||
<email>kstars@30doradus.org</email>; we would like to see what you have done,
|
||||
and may post some scripts on our webpage. Also, if you have any
|
||||
ideas for how to improve scripting (or any part of &kstars;), let us
|
||||
know at <email>kstars-devel@lists.sourceforge.net</email> or submit a
|
||||
wishlist item to bugzilla.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 46 KiB |
@ -0,0 +1,113 @@
|
||||
<sect1 id="tool-details">
|
||||
<title>Object Details Window</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Object Details Window</secondary></indexterm>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Details</secondary></indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Object Details Window
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="detaildialog.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Object Details Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The Object Details Window presents advanced data available about
|
||||
a specific object in the sky. To access this tool,
|
||||
<mousebutton>right</mousebutton>-click on any object, and select the
|
||||
<guimenuitem>Details...</guimenuitem> item from the popup menu.
|
||||
</para>
|
||||
<para>
|
||||
The window is divided into a number of Tabs. In the
|
||||
<guilabel>General</guilabel> Tab, we present basic data about
|
||||
the current object. This includes names and catalog designations,
|
||||
object type, and <link linkend="ai-magnitude">magnitude</link>
|
||||
(brightness). Also shown are the object's Equatorial and Horizontal
|
||||
coordinates, as well as its rise, set and transit times.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Internet Links</secondary>
|
||||
<tertiary>Customizing</tertiary></indexterm>
|
||||
In the <guilabel>Links</guilabel> tab, you can manage the internet
|
||||
links associated with this object. The Image and Information links
|
||||
associated with the object are listed. These are the links that
|
||||
appear in the popup menu when the object is
|
||||
<mousebutton>right</mousebutton>-clicked. You can add custom
|
||||
links to the object with the <guibutton>Add Link...</guibutton>
|
||||
button. This will open a window in which you fill in the URL and link
|
||||
text for the new link (you can also test the URL in the web browser
|
||||
from this window). Keep in mind that the custom link can easily point
|
||||
to a file on your local disk, so you can use this feature to index
|
||||
your personal astronomical images or observing logs.
|
||||
</para>
|
||||
<para>
|
||||
You can also modify or remove any link using the
|
||||
<guibutton>Edit Link...</guibutton> and
|
||||
<guibutton>Remove Link...</guibutton> buttons.
|
||||
</para>
|
||||
<para>
|
||||
The <guilabel>Advanced</guilabel> Tab allows you to query professional
|
||||
astronomical databases on the internet for information regarding the
|
||||
current object. To use these databases, simply highlight the
|
||||
desired database in the list, and press the <guibutton>View</guibutton>
|
||||
button to see the results of your query in a web browser window. The
|
||||
query is made using the primary name of the object you clicked on to
|
||||
open the Details Dialog. The following databases are available for
|
||||
querying:
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>High Energy Astrophysical Archive (HEASARC). Here you
|
||||
can retrieve data about the current object from a number of
|
||||
<quote>High-energy</quote> observatories, which covers the
|
||||
Ultraviolet, X-ray and Gamma Ray portions of the electromagnetic
|
||||
spectrum.</para></listitem>
|
||||
<listitem><para>Multimission Archive at Space Telescope (MAST).
|
||||
The Space Telescope Science Institute provides access to the entire
|
||||
collection of images and spectra taken with the Hubble Space
|
||||
Telescope, as well as several other space-based observatories.
|
||||
</para></listitem>
|
||||
<listitem><para>NASA Astrophysical Data System (ADS). This
|
||||
incredible bibliographic database encompass the entire body of
|
||||
literature published in international peer-review Journals about
|
||||
astronomy and astrophysics. The database is divided into four
|
||||
general subject areas (Astronomy and Astrophysics, Astrophysics
|
||||
Preprints, Instrumentation, and Physics and Geophysics). Each of these
|
||||
has three sub-nodes that query the database
|
||||
in different ways. <quote>Keyword search</quote> will return articles
|
||||
which listed the object's name as a keyword. <quote>Title word
|
||||
search</quote> will return articles which included the object name in
|
||||
their Title, and the <quote>Title & Keyword search</quote> uses
|
||||
both options together.
|
||||
</para></listitem>
|
||||
<listitem><para>NASA/IPAC Extragalactic Database (NED). NED provides
|
||||
encapsulated data and bibliographic links about
|
||||
extragalactic objects. You should only use NED if your target is
|
||||
extragalactic; &ie; if it is itself a galaxy.
|
||||
</para></listitem>
|
||||
<listitem><para>Set of Identifications, Measurements, and Bibliography
|
||||
for Astronomical Data (SIMBAD). SIMBAD is similar to NED, except it
|
||||
provides data about all kinds of objects, not just galaxies.
|
||||
</para></listitem>
|
||||
<listitem><para>SkyView provides images from All-Sky surveys that have
|
||||
been performed in dozens of different parts of the spectrum, from
|
||||
Gamma Rays to the Radio. The &kstars; interface will retrieve an image
|
||||
from any of these surveys, centered on the selected object.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para>
|
||||
Finally, in the <guilabel>Log</guilabel> Tab, you can type in some text
|
||||
that will remain associated with this object's Details window.
|
||||
You could use this to attach personal observing notes, for example.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
After Width: | Height: | Size: 24 KiB |
@ -0,0 +1,67 @@
|
||||
<chapter id="dumpmode">
|
||||
<title>Command-Line mode for Image Generation</title>
|
||||
<indexterm><primary>Image-dump Mode</primary></indexterm>
|
||||
|
||||
<para>
|
||||
You can use &kstars; to generate an image of the sky
|
||||
without actually launching the <acronym>GUI</acronym>
|
||||
portion of the program. To use this feature, start
|
||||
&kstars; from a command prompt using arguments to
|
||||
specify the filename for the image, as well as the
|
||||
desired image dimensions:
|
||||
|
||||
<cmdsynopsis>
|
||||
<command>kstars</command>
|
||||
<arg choice="plain">--dump</arg>
|
||||
<arg>--filename <replaceable>kstars.png</replaceable></arg>
|
||||
<arg>--height <replaceable>640</replaceable></arg>
|
||||
<arg>--width <replaceable>480</replaceable></arg>
|
||||
<arg>--script <replaceable>myscript.kstars</replaceable></arg>
|
||||
<arg>--date <replaceable>"4 July 1976
|
||||
12:30:00"</replaceable></arg>
|
||||
</cmdsynopsis>
|
||||
</para>
|
||||
<para>
|
||||
If no filename is specified, it generates a file
|
||||
named <filename>kstars.png</filename>. It will attempt to
|
||||
generate an image that matches the extension of your filename.
|
||||
The following extensions are recognized: <quote>png</quote>,
|
||||
<quote>jpg</quote>, <quote>jpeg</quote>, <quote>gif</quote>,
|
||||
<quote>pnm</quote>, and <quote>bmp</quote>. If the filename
|
||||
extension is not recognized, it defaults to the
|
||||
<acronym>PNG</acronym> image type.
|
||||
</para>
|
||||
<para>
|
||||
Likewise, if the image width and height are not specified,
|
||||
they default to 640 and 480, respectively.
|
||||
</para>
|
||||
<para>
|
||||
By default, &kstars; will read in the options values stored in
|
||||
your <filename>$KDEHOME/share/config/kstarsrc</filename> file
|
||||
to determine where the image will be centered, and how it is
|
||||
rendered. This means you need to run &kstars; in normal GUI
|
||||
mode, and exit the program when it is set up with the desired
|
||||
options for the generated images. This is not very flexible,
|
||||
so we also provide the ability to execute a &kstars;
|
||||
<acronym>DCOP</acronym> script to set the scene before
|
||||
generating the image. The filename you specify as the
|
||||
script argument should be a valid &kstars;
|
||||
<acronym>DCOP</acronym> script, such as one created with the
|
||||
<link linkend="tool-scriptbuilder">Script Builder Tool</link>.
|
||||
The script can be used to set where the image is pointing,
|
||||
set the geographic location, set the time and date, change the
|
||||
Zoom level, and adjust other view options. Some of the
|
||||
<acronym>DCOP</acronym> functions make no sense in non-GUI
|
||||
mode (such as <function>waitForKey()</function>); if these
|
||||
functions are encountered while parsing the script, they are
|
||||
simply ignored.
|
||||
</para>
|
||||
<para>
|
||||
By default, &kstars; will use the system CPU time and date for
|
||||
generating the image. Alternatively, you may specify a time
|
||||
and date with the <quote>--date</quote> argument. You can also
|
||||
use this argument for specifying the startup date in normal
|
||||
GUI mode.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,58 @@
|
||||
<sect1 id="ai-ecliptic">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>John</firstname>
|
||||
<surname>Cirillo</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Ecliptic</title>
|
||||
<indexterm><primary>Ecliptic</primary>
|
||||
<seealso>Ecliptic Coordinates</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The ecliptic is an imaginary <link linkend="ai-greatcircle">Great Circle</link>
|
||||
on the <link linkend="ai-csphere">Celestial Sphere</link> along which the Sun
|
||||
appears to move over the course of a year. Of course, it is really the
|
||||
Earth's orbit around the Sun causing the change in the Sun's apparent
|
||||
direction. The ecliptic is inclined from the <link linkend="ai-cequator">Celestial
|
||||
Equator</link> by 23.5 degrees. The two points where the Ecliptic crosses
|
||||
the Celestial Equator are known as the <link
|
||||
linkend="ai-equinox">Equinoxes</link>.
|
||||
</para><para>
|
||||
Since our solar system is relatively flat, the orbits of the planets are
|
||||
also close to the plane of the ecliptic. In addition, the constellations of the
|
||||
zodiac are located along the ecliptic. This makes the ecliptic a very useful
|
||||
line of reference to anyone attempting to locate the planets or the
|
||||
constellations of the zodiac, since they all literally <quote>follow the
|
||||
Sun</quote>.
|
||||
</para><para>
|
||||
Because of the 23.5-degree tilt of the Ecliptic, the
|
||||
<firstterm>Altitude</firstterm> of the Sun at noon changes over the course of the
|
||||
year, as it follows the path of the Ecliptic across the sky. This causes the
|
||||
seasons. In the Summer, the Sun is high in the sky at noon,
|
||||
and it remains above the <link linkend="ai-horizon">Horizon</link> for more than
|
||||
twelve hours. Whereas, in the winter, the Sun is low in the sky at noon, and remains
|
||||
above the Horizon for less than twelve hours. In addition, sunlight is received at
|
||||
the Earth's surface at a more direct angle in the Summer, which means that a given
|
||||
area at the surface receives more energy per second in the Summer than in Winter.
|
||||
The differences in day duration and in energy received per unit area lead to the
|
||||
differences in temperature we experience in Summer and Winter.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercises:</para>
|
||||
<para>
|
||||
Make sure your location is set to somewhere that is not very near the equator
|
||||
for these experiments. Open the <guilabel>Configure &kstars;</guilabel> window, and
|
||||
switch to Horizontal coordinates, with the Opaque Ground shown. Open the
|
||||
<guilabel>Set Time</guilabel> window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo>),and change the
|
||||
Date to sometime in the middle of Summer, and the Time to 12:00 Noon. Back in
|
||||
the Main Window, point toward the Southern Horizon (press <keycap>S</keycap>).
|
||||
Note the height of the Sun above the Horizon at Noon in the Summer. Now, change
|
||||
the Date to something in the middle of Winter (but keep the Time at 12:00 Noon).
|
||||
The Sun is now much lower in the Sky. You will also notice that the day durations
|
||||
are different if you open the <guilabel>What's Up Tonight?</guilabel> tool for
|
||||
each date.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,115 @@
|
||||
<sect1 id="ai-ellipgal">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Elliptical Galaxies</title>
|
||||
<indexterm><primary>Elliptical Galaxies</primary>
|
||||
</indexterm>
|
||||
|
||||
<para> Elliptical galaxies are spheroidal concentrations of billions
|
||||
of stars that resemble Globular Clusters on a grand scale. They have
|
||||
very little internal structure; the density of stars declines smoothly
|
||||
from the concentrated center to the diffuse edge, and they can have a
|
||||
broad range of ellipticities (or aspect ratios). They typically
|
||||
contain very little interstellar gas and dust, and no young stellar
|
||||
populations (although there are exceptions to these rules). Edwin
|
||||
Hubble referred to Elliptical galaxies as <quote>early-type</quote>
|
||||
galaxies, because he thought that they evolved to become Spiral
|
||||
Galaxies (which he called <quote>late-type</quote> galaxies).
|
||||
Astronomers actually now believe the opposite is the case (&ie;, that
|
||||
Spiral galaxies can turn into Elliptical galaxies), but Hubble's
|
||||
early- and late-type labels are still used. </para>
|
||||
|
||||
<para>
|
||||
Once thought to be a simple galaxy type, ellipticals are now known to
|
||||
be quite complex objects. Part of this complexity is due
|
||||
to their amazing history: ellipticals are thought to be the end
|
||||
product of the merger of two Spiral galaxies. You can
|
||||
view a computer simulation MPEG movie of such a merger at <ulink
|
||||
url="http://oposite.stsci.edu/pubinfo/pr/2002/11/vid/v0211d3.mpg">
|
||||
this NASA HST webpage</ulink> (warning: the file is 3.4 MB).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Elliptical galaxies span a very wide range of sizes and
|
||||
luminosities, from giant Ellipticals hundreds of thousands of light
|
||||
years across and nearly a trillion times brighter than the sun, to
|
||||
dwarf Ellipticals just a bit brighter than the average globular
|
||||
cluster. They are divided to several morphological classes:
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>cD galaxies:</term>
|
||||
<listitem><para>
|
||||
Immense and bright objects that can
|
||||
measure nearly 1 Megaparsec (3 million light years) across. These
|
||||
titans are only found near the centers of large, dense clusters of
|
||||
galaxies, and are likely the result of many galaxy
|
||||
mergers.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Normal Elliptical galaxies</term>
|
||||
<listitem><para>Condensed Object with
|
||||
relatively high central surface brightness. They include the giant
|
||||
ellipticals (gE'e), intermediate-luminosity ellipticals (E's), and
|
||||
compact ellipticals.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Dwarf elliptical galaxies (dE's)</term>
|
||||
<listitem><para> This class of
|
||||
galaxies is fundamentally different from normal ellipticals. Their
|
||||
diameters on the order of 1 to 10 kiloparsec with surface brightness
|
||||
that is much lower than normal ellipticals, giving them a much more
|
||||
diffuse appearance. They display the same characteristic gradual
|
||||
decline of star density from a relatively dense core out to a diffuse
|
||||
periphery.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Dwarf spheroidal galaxies (dSph's)</term>
|
||||
<listitem><para>Extreme low-luminosity, low
|
||||
surface-brightness and have only been observed in the vicinity of the
|
||||
Milky Way, and possibly other very nearby galaxy groups, such as the
|
||||
Leo group. Their absolute magnitudes are only -8 to -15 mag.
|
||||
The Draco dwarf spheroidal galaxy has an absolute magnitude of -8.6,
|
||||
making it fainter than the average globular cluster in the Milky Way!
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Blue compact dwarf galaxies (BCD's)</term>
|
||||
<listitem>
|
||||
<para> Small galaxies that are unusually
|
||||
blue. Thehave photometric colors of B-V = 0.0 to 0.30 mag, which is
|
||||
typical for relatively young stars of <firstterm>spectral type</firstterm> A.
|
||||
This suggests that BCDs
|
||||
are currently actively forming stars. These systems also have
|
||||
abundant interstellar gas (unlike other Elliptical galaxies).
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
You can see examples of Elliptical galaxies in &kstars;, using the Find
|
||||
Object window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo>).
|
||||
Search for NGC 4881, which is the Giant cD galaxy in the Coma
|
||||
cluster of galaxies. M 86 is a normal Elliptical galaxy in the Virgo
|
||||
cluster of galaxies. M 32 is a dwarf Elliptical that is a satellite
|
||||
of our neighbor, the Andromeda galaxy (M 31). M 110 is another
|
||||
satellite of M 31 that is a borderline dwarf spheroidal galaxy
|
||||
(<quote>borderline</quote> because it is somewhat brighter than most other
|
||||
dwarf spheroidals).
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,37 @@
|
||||
<sect1 id="ai-equinox">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Equinoxes</title>
|
||||
<indexterm><primary>Equinoxes</primary>
|
||||
<seealso>Celestial Equator</seealso>
|
||||
<seealso>Ecliptic</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
Most people know the Vernal and Autumnal Equinoxes as
|
||||
calendar dates, signifying the beginning of the Northern hemisphere's Spring
|
||||
and Autumn, respectively. Did you know that the equinoxes are also positions in
|
||||
the sky?
|
||||
</para><para>
|
||||
The <link linkend="ai-cequator">Celestial Equator</link> and the
|
||||
<link linkend="ai-ecliptic">Ecliptic</link> are two
|
||||
<link linkend="ai-greatcircle">Great Circles</link> on the
|
||||
<link linkend="ai-csphere">Celestial Sphere</link>, set at an angle of 23.5
|
||||
degrees. The two points where they intersect are called the
|
||||
<firstterm>Equinoxes</firstterm>. The <firstterm>Vernal Equinox</firstterm>
|
||||
has coordinates RA=0.0 hours, Dec=0.0 degrees. The <firstterm>Autumnal
|
||||
Equinox</firstterm> has coordinates RA=12.0 hours, Dec=0.0 degrees.
|
||||
</para><para>
|
||||
The Equinoxes are important for marking the seasons. Because they are on
|
||||
the <link linkend="ai-ecliptic">Ecliptic</link>, the Sun passes through each
|
||||
equinox every year. When the Sun passes through the Vernal Equinox (usually on
|
||||
March 21st), it crosses the <link linkend="ai-cequator">Celestial Equator</link>
|
||||
from South to North, signifying the end of Winter for the Northern hemisphere.
|
||||
Similarly, whenthe Sun passes through the Autumnal Equinox (usually on September
|
||||
21st), it crosses the Celestial Equator from North to South, signifying the
|
||||
end of Winter for the Southern hemisphere.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,274 @@
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<qandaset id="faqlist">
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What is the &kstars; Icon?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The <guiicon>&kstars; Icon</guiicon> is a sextant, a handheld telescope which
|
||||
was used by navigators on sailing ships back when the stars were important for
|
||||
navigation. By carefully reckoning the positions of the stars, the navigator
|
||||
could get an accurate estimate of the ship's current <link
|
||||
linkend="ai-geocoords">longitude and latitude</link>.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What do the different symbols for deep-sky objects mean?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The symbol indicates the object type:
|
||||
<itemizedlist>
|
||||
<listitem><para>dotted circle: Open Cluster</para></listitem>
|
||||
<listitem><para>cross-in-circle: Globular Cluster</para></listitem>
|
||||
<listitem><para>box: Gaseous Nebula</para></listitem>
|
||||
<listitem><para>diamond: Supernova Remnant</para></listitem>
|
||||
<listitem><para>circle with outer lines: Planetary Nebula</para></listitem>
|
||||
<listitem><para>ellipse: Galaxy</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What do the different colors of Deep-sky objects mean?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Generally, the different colors indicate to which catalog the object
|
||||
belongs (Messier, NGC or IC). However, some objects have a different
|
||||
color which indicates that there are extra images available in the
|
||||
<link linkend="popup-menu">popup menu</link> (the default
|
||||
<quote>extras</quote> color is red).
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
Why are there so many more U.S. cities than in other countries?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
When we started &kstars;, we were unable to find a longitude/latitude
|
||||
database that covered the globe equitably. However, the &kstars;
|
||||
community is rapidly overcoming this problem! We have already
|
||||
received city lists from many users around the world. If you can
|
||||
contribute to this effort, please send us your list of cities and
|
||||
coordinates.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
I have added a custom location to &kstars; that I no longer want. How
|
||||
do I remove it from the program?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
You will have to edit the
|
||||
<filename>~/.kde/share/apps/kstars/mycities.dat</filename> file, and
|
||||
remove the location's line from that file.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why can I not display the ground when using Equatorial
|
||||
Coordinates?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The short answer is, this is a temporary limitation. There is a
|
||||
problem when constructing the filled polygon that represents the ground
|
||||
when in Equatorial mode. However, it does not make too much sense to draw
|
||||
the ground in equatorial coordinates, which is why this fix has been given
|
||||
a low priority.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why do some objects disappear when I am scrolling the
|
||||
display?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
When the display is in motion, &kstars; must recompute the screen
|
||||
coordinates of every object in its database, which involves
|
||||
some pretty heavy trigonometry. When scrolling the display (either
|
||||
with the arrow keys or by dragging with the mouse), the display may
|
||||
become slow and jerky, because the computer is having trouble keeping
|
||||
up. By excluding many of the objects, the computational load is
|
||||
greatly reduced, which allows for smoother scrolling. You can turn
|
||||
off this feature in the <guilabel>Configure &kstars;</guilabel> window,
|
||||
and you can also configure which objects get hidden.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I do not understand all the terms used in &kstars;. Where can I
|
||||
learn more about the astronomy behind the program?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The &kstars; Handbook includes the <link linkend="astroinfo">AstroInfo
|
||||
Project</link>; a series of short, hyperlinked articles about
|
||||
astronomical topics that can be explored and illustrated with &kstars;.
|
||||
AstroInfo is a community effort, like GNUpedia or Everything2. If
|
||||
you'd like to contribute to AstroInfo, please join our mailing list:
|
||||
<email>kstars-info@lists.sourceforge.net</email>.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I want &kstars; to start up with a time and date different from
|
||||
my system CPU clock. Is this possible?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes; to start kstars with a different time/date, use the
|
||||
<quote>--date</quote> argument, followed by a date string like
|
||||
<quote>4 July 1976 12:30:00</quote>
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I want &kstars; to start up with the simulation clock paused.
|
||||
Is this possible?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes; to start kstars with the clock paused, simply add the
|
||||
<quote>--paused</quote> argument to the command line.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>How accurate/precise is &kstars;?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
&kstars; is pretty accurate, but it is not (yet) as precise as it can
|
||||
possibly be. The problem with high-precision calculations is that
|
||||
you start having to deal with a large number of complicating factors.
|
||||
If you are not a professional astronomer, you will probably never have a
|
||||
problem with its accuracy or precision.
|
||||
</para>
|
||||
<para>
|
||||
Here is a list of some of the complicating factors which limit the
|
||||
program's precision:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Planet positions are only accurate for dates within 4000 years
|
||||
or so of the current epoch. The planet positions are predicted using
|
||||
a Fourier-like analysis of their orbits, as observed over the past few
|
||||
centuries. We learnt in school that planets follow simple elliptical
|
||||
orbits around the Sun, but this is not strictly true. It would be true
|
||||
only if there was only one planet in the Solar system, and if the Sun
|
||||
and the planet were both point masses. As it is, the planets are
|
||||
constantly tugging on each other, perturbing the orbits slightly, and
|
||||
tidal effects also induce precessional wobbling. In fact, recent
|
||||
analysis suggests that the planets' orbits may not even be stable in
|
||||
the long term (i.e., millions or billions of years). As a rule of
|
||||
thumb, you can expect the position of a planet to be accurate to a few
|
||||
arcseconds between the dates -2000 and 6000.
|
||||
</para><para>
|
||||
Pluto is the exception to this; its position is perhaps ten times less
|
||||
precise than the positions of the other planets. Still, for dates
|
||||
near the present epoch, its position can be trusted to about an
|
||||
arcsecond.
|
||||
</para><para>
|
||||
The moon's position is the most difficult to predict to high precision.
|
||||
This is because its motion is quite perturbed by the Earth. Also,
|
||||
since it is so nearby, even minute effects that would be undetectable
|
||||
in more distant bodies are easily apparent in the moon.
|
||||
</para><para>
|
||||
The objects with the worst long-term precision in the program are the
|
||||
comets and asteroids. We use a very simplistic orbital model for the
|
||||
minor planets that does not include third-body perturbations.
|
||||
Therefore, their positions can only be trusted for dates near the
|
||||
present epoch. Even for the present epoch, one can expect positional
|
||||
errors among the minor planets of order 10 arcseconds or more.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why do I have to download an improved NGC/IC catalog and Messier
|
||||
object images? Why not just include them as part of the &kstars; distribution?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The author of the downloadable NGC/IC catalog has released it with the restriction that it may not be used commercially. For most &kstars; users, this is not a problem. However, it is technically against the &kstars; license (the
|
||||
<acronym>GPL</acronym>) to restrict usage in this way. We removed the Messier object images from the standard distribution for two reasons: to simply reduce the size of &kstars;, and also because of similar licensing concerns with a couple of the images. The inline images are significantly compressed to a very low quality from their original form, so I doubt there is a real copyright concern, but I did obtain explicit permission from the images' authors to use the few images for which there was any question about it (see <filename>README.images</filename>). Still, just to be absolutely safe, I removed them from the standard distribution, and marked the download archive as being "free for non-commercial use".
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>I am really enjoying the beautiful images I have downloaded through &kstars;! I would like to share them with the world; can I publish a calendar featuring these images (or are there any usage restrictions on the images)?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
It depends on the image, but many of the images restrict against commercial usage. The Image Viewer's statusbar will usually contain information about the image's copyright holder, and what usage restrictions apply. As a rule of thumb: anything published by NASA is in the public domain (including all HST images). For everything else, you can pretty safely assume that the images may not be used commercially without permission. When in doubt, contact the image's copyright holder directly.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Can I help contribute to future versions of &kstars;?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes, definitely! Introduce yourself on our mailing list:
|
||||
<email>kstars-devel@kde.org</email>. If you want to
|
||||
help with the coding, download the latest <ulink
|
||||
url="http://edu.kde.org/kstars/cvs.html">CVS</ulink> version of the
|
||||
code and dive right in. There are several README files in the
|
||||
distribution that explain some of the code's subsystems. If you
|
||||
need ideas of what to work on, see the TODO file. You can submit
|
||||
patches to kstars-devel, and feel free to post any questions you
|
||||
have about the code there as well.
|
||||
</para><para>
|
||||
If you are not into coding, we can still use your help with i18n, docs,
|
||||
AstroInfo articles, URL links, bug reports, and feature requests.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
</qandaset>
|
||||
</chapter>
|
||||
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 249 KiB |
@ -0,0 +1,59 @@
|
||||
<sect1 id="tool-fitsviewer">
|
||||
<title><acronym>FITS</acronym> Viewer Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>FITS Viewer</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>The Flexible Image Transport System (FITS) is the standard format for representing images and data in Astronomy.</para>
|
||||
|
||||
<para>The KStars FITS Viewer tool is integrated with the <link linkend="indi">INDI</link> framework for seamless display and manipulation of captured FITS images. Furthermore, the FITS Viewer can be used to post-process raw data. To open a FITS file, select <guimenuitem>Open FITS...</guimenuitem> from the
|
||||
<guimenu>File</guimenu> menu, or press <keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>.</para>
|
||||
|
||||
<para>FITS Viewer features:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Support for 8, 16, 32, IEEE -32, and IEEE -64 bits formats.</para></listitem>
|
||||
<listitem><para>Histogram with auto, linear, logarithmic, and square-root scales.</para></listitem>
|
||||
<listitem><para>Image reduction tool.</para></listitem>
|
||||
<listitem><para>Brightness/Contrast controls.</para></listitem>
|
||||
<listitem><para>Pan and Zoom.</para></listitem>
|
||||
<listitem><para>Auto levels.</para></listitem>
|
||||
<listitem><para>Statistics.</para></listitem>
|
||||
<listitem><para>FITS header query.</para></listitem>
|
||||
<listitem><para>Undo/Redo.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The FITS Viewer Tool</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="fitsarea.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>FITS Viewer Tool</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The above diagram illustrates the FITS Viewer work area and window. The tool provides basic functions for image display and processing. FITS data depth is preserved throughout all processing, open, and save functions. While the tool adhere to the FITS standard, it does not support all possible FITS features:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Support for only <emphasis>one</emphasis> image per file.</para></listitem>
|
||||
<listitem><para>Support for only 2D data. 1D and 3D data are discarded.</para></listitem>
|
||||
<listitem><para>No support for WCS (World Coordinate System).</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>The following is a brief description of the tool's functional units:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Brightness/Contrast: Adjusts brightness and contrast. The function can be CPU and memory intensive for very large FITS.</para></listitem>
|
||||
<listitem><para>Histogram: Displays one-channel FITS histogram. The user can rescale the image by optionally defining an upper and lower limit for the cutoff region. The rescaling operation (linear, logarithmic, or square-root) may then be applied to the region enclosed by the upper and lower limits.</para></listitem>
|
||||
<listitem><para>Image reduction: Removes background noise and optical anamolies from the image. Raw CCD images are often processed to remove instrument and temperature noise, in addition to aberrations inherit in the optical system. The function supports three types of raw CCD frames:</para>
|
||||
<orderedlist>
|
||||
<listitem><para>Dark Frames</para></listitem>
|
||||
<listitem><para>Flat Field Frames</para></listitem>
|
||||
<listitem><para>Dark Flat Field Frames</para></listitem>
|
||||
</orderedlist>
|
||||
<para>The user can stack up multiple frames in each category to increase the signal-to-noise ratio. Two combination methods are provided: mean and median. The two methods produce similar results most of the time, but the median method insures that the data is not skewed due to random cosmic ray hits.</para>
|
||||
</listitem>
|
||||
<listitem><para>Statistics: Provides simple statistics for minimum and maximum pixel values and the their respective locations. FITS depth, dimension, mean, and standard deviation.</para></listitem>
|
||||
<listitem><para>FITS header: Displays FITS header information.</para></listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
@ -0,0 +1,69 @@
|
||||
<sect1 id="ai-flux">
|
||||
|
||||
<sect1info>
|
||||
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Flux</title>
|
||||
<indexterm><primary>Flux</primary>
|
||||
<seealso>Luminosity</seealso>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
The <firstterm>flux</firstterm> is the amount of energy that passes through a unit area each second.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Astronomers use flux to denote the apparent brightness of a celestial body. The apparent brightness is defined as the the amount of light received from a star
|
||||
above the earth atmosphere passing through a unit area each second. Therefore, the apparent brightness is simply the flux we receive from a star.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The flux measures the <emphasis>rate of flow</emphasis> of energy that passes through each cm^2 (or any unit area) of an object's surface each second.
|
||||
The detected flux depends on the distance from the source that radiates the energy. This is because the energy has to spread over a volume of space before it reaches us.
|
||||
Let us assume that we have an imaginary balloon that encloses a star. Each dot on the balloon represents a unit of energy emitted from the star. Initially, the dots in an area
|
||||
of one cm^2 are in close proximity to each other and the flux (energy emitted per square centimeter per second) is high. After a distance d, the volume and surface area of the
|
||||
balloon increased causing the dots to <emphasis>spread away</emphasis> from each. Consequently, the number of dots (or energy) enclosed in one cm^2 has decreased as illustrated in Figure 1.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="flux.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<caption><para><phrase>Figure 1</phrase></para></caption>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The flux is inversely proportional to distance by a simple r^2 relation. Therefore, if the distance is doubled, we receive 1/2^2 or 1/4th of the original flux.
|
||||
From a fundamental standpoint, the flux is the <link linkend="ai-luminosity">luminosity</link> per unit area:
|
||||
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="flux1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
where (4 * PI * R^2) is the surface area of a sphere (or a balloon!) with a radius R.
|
||||
Flux is measured in Watts/m^2/s or as commonly used by astronomers: Ergs/cm^2/s.
|
||||
For example, the luminosity of the sun is L = 3.90 * 10^26 W. That is, in one second the sun radiates 3.90 * 10^26 joules of energy into space. Thus, the flux we receive
|
||||
passing through one square centimeter from the sun at a distance of one AU (1.496 * 10^13 cm) is:
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="flux2.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 492 KiB |
|
After Width: | Height: | Size: 761 B |
|
After Width: | Height: | Size: 2.1 KiB |
|
After Width: | Height: | Size: 20 KiB |
@ -0,0 +1,56 @@
|
||||
<sect1 id="ai-geocoords">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Geographic Coordinates</title>
|
||||
<indexterm><primary>Geographic Coordinate System</primary></indexterm>
|
||||
<indexterm><primary>Longitude</primary><see>Geographic Coordinate System</see></indexterm>
|
||||
<indexterm><primary>Latitude</primary><see>Geographic Coordinate System</see></indexterm>
|
||||
<para>
|
||||
Locations on Earth can be specified using a spherical coordinate system.
|
||||
The geographic (<quote>earth-mapping</quote>) coordinate system is aligned
|
||||
with the spin axis of the Earth. It defines two angles measured from
|
||||
the center of the Earth. One angle, called the <firstterm>Latitude</firstterm>,
|
||||
measures the angle between any point and the Equator. The other angle, called
|
||||
the <firstterm>Longitude</firstterm>, measures the angle
|
||||
<emphasis>along</emphasis> the Equator from an arbitrary point on the Earth
|
||||
(Greenwich, England is the accepted zero-longitude point in most modern
|
||||
societies).
|
||||
</para><para>
|
||||
By combining these two angles, any location on Earth can be specified.
|
||||
For example, Baltimore, Maryland (USA) has a latitude of 39.3 degrees
|
||||
North, and a longitude of 76.6 degrees West. So, a vector drawn from
|
||||
the center of the Earth to a point 39.3 degrees above the Equator and
|
||||
76.6 degrees west of Greenwich, England will pass through Baltimore.
|
||||
</para><para>
|
||||
The Equator is obviously an important part of this coordinate system; it
|
||||
represents the <emphasis>zeropoint</emphasis> of the latitude angle, and the
|
||||
halfway point between the poles. The Equator is the <firstterm>Fundamental
|
||||
Plane</firstterm> of the geographic coordinate system. <link
|
||||
linkend="ai-skycoords">All Spherical Coordinate Systems</link> define such a
|
||||
Fundamental Plane.
|
||||
</para><para>
|
||||
Lines of constant Latitude are called <firstterm>Parallels</firstterm>. They
|
||||
trace circles on the surface of the Earth, but the only parallel that is a <link
|
||||
linkend="ai-greatcircle">Great Circle</link> is the Equator (Latitude=0
|
||||
degrees). Lines of constant Longitude are called
|
||||
<firstterm>Meridians</firstterm>. The Meridian passing through Greenwich is the
|
||||
<firstterm>Prime Meridian</firstterm> (longitude=0 degrees). Unlike Parallels,
|
||||
all Meridians are great circles, and Meridians are not parallel: they intersect
|
||||
at the north and south poles.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
What is the longitude of the North Pole? Its latitude
|
||||
is 90 degrees North.
|
||||
</para>
|
||||
<para>
|
||||
This is a trick question. The Longitude is meaningless at the north pole (and the
|
||||
south pole too). It has all longitudes at the same time.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 142 KiB |
@ -0,0 +1,27 @@
|
||||
<sect1 id="ai-greatcircle">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Great Circles</title>
|
||||
<indexterm><primary>Great Circles</primary>
|
||||
<seealso>Celestial Sphere</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
Consider a sphere, such as the Earth, or the
|
||||
<link linkend="ai-csphere">Celestial Sphere</link>. The intersection
|
||||
of any plane with the sphere will result in a circle on the surface of
|
||||
the sphere. If the plane happens to contain the center of the sphere,
|
||||
the intersection circle is a <firstterm>Great Circle</firstterm>.
|
||||
Great circles are the largest circles that can be drawn on a sphere.
|
||||
Also, the shortest path between any two points on a sphere is always
|
||||
along a great circle.
|
||||
</para><para>
|
||||
Some examples of great circles on the celestial sphere include: the
|
||||
<link linkend="ai-horizon">Horizon</link>, the
|
||||
<link linkend="ai-cequator">Celestial Equator</link>, and the
|
||||
<link linkend="ai-ecliptic">Ecliptic</link>.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,25 @@
|
||||
<sect1 id="ai-horizon">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Horizon</title>
|
||||
<indexterm><primary>Horizon</primary>
|
||||
<seealso>Horizontal Coordinates</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The <firstterm>Horizon</firstterm> is the line that separates Earth from Sky.
|
||||
More precisely, it is the line that divides all of the directions you can
|
||||
possibly look into two categories: those which intersect the Earth,
|
||||
and those which do not. At many locations, the Horizon is
|
||||
obscured by trees, buildings, mountains, &etc;. However, if you are on
|
||||
a ship at sea, the Horizon is strikingly apparent.
|
||||
</para><para>
|
||||
The horizon is the <firstterm>Fundamental Plane</firstterm> of the <link
|
||||
linkend="horizontal">Horizontal Coordinate System</link>. In other
|
||||
words, it is the locus of points which have an <firstterm>Altitude</firstterm>
|
||||
of zero degrees.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,33 @@
|
||||
<sect1 id="ai-hourangle">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Hour Angle</title>
|
||||
<indexterm><primary>Hour Angle</primary>
|
||||
<seealso>Local Meridian</seealso>
|
||||
<seealso>Sidereal Time</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
As explained in the <link linkend="ai-sidereal">Sidereal Time</link> article,
|
||||
the <firstterm>Right Ascension</firstterm> of an object indicates the Sidereal
|
||||
Time at which it will transit across your <link linkend="ai-meridian">Local
|
||||
Meridian</link>. An object's <firstterm>Hour Angle</firstterm> is
|
||||
defined as the difference between the current Local Sidereal Time and the Right
|
||||
Ascension of the object:
|
||||
</para><para>
|
||||
<abbrev>HA</abbrev><subscript>obj</subscript> =
|
||||
<abbrev>LST</abbrev> - <abbrev>RA</abbrev><subscript>obj</subscript>
|
||||
</para><para>
|
||||
Thus, the object's Hour Angle indicates how much Sidereal Time has passed
|
||||
since the object was on the Local Meridian. It is also the angular distance
|
||||
between the object and the meridian, measured in hours (1 hour = 15 degrees).
|
||||
For example, if an object has an hour angle of 2.5 hours, it transited across
|
||||
the Local Meridian 2.5 hours ago, and is currently 37.5 degrees West of the
|
||||
Meridian. Negative Hour Angles indicate the time until the
|
||||
<emphasis>next</emphasis> transit across the Local Meridian. Of course, an Hour
|
||||
Angle of zero means the object is currently on the Local Meridian.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,299 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&kstars;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY astroinfo SYSTEM "astroinfo.docbook">
|
||||
<!ENTITY blackbody SYSTEM "blackbody.docbook">
|
||||
<!ENTITY calc-angdist SYSTEM "calc-angdist.docbook">
|
||||
<!ENTITY calc-apcoords SYSTEM "calc-apcoords.docbook">
|
||||
<!ENTITY calc-ecliptic SYSTEM "calc-ecliptic.docbook">
|
||||
<!ENTITY calc-eqgal SYSTEM "calc-eqgal.docbook">
|
||||
<!ENTITY calc-equinox SYSTEM "calc-equinox.docbook">
|
||||
<!ENTITY calc-horiz SYSTEM "calc-horizontal.docbook">
|
||||
<!ENTITY calc-planetcoords SYSTEM "calc-planetcoords.docbook">
|
||||
<!ENTITY calc-precess SYSTEM "calc-precess.docbook">
|
||||
<!ENTITY calc-geodetic SYSTEM "calc-geodetic.docbook">
|
||||
<!ENTITY calc-dayduration SYSTEM "calc-dayduration.docbook">
|
||||
<!ENTITY calc-julian SYSTEM "calc-julianday.docbook">
|
||||
<!ENTITY calc-sidereal SYSTEM "calc-sidereal.docbook">
|
||||
<!ENTITY calculator SYSTEM "calculator.docbook">
|
||||
<!ENTITY cequator SYSTEM "cequator.docbook">
|
||||
<!ENTITY colorandtemp SYSTEM "colorandtemp.docbook">
|
||||
<!ENTITY commands SYSTEM "commands.docbook">
|
||||
<!ENTITY config SYSTEM "config.docbook">
|
||||
<!ENTITY contents SYSTEM "ai-contents.docbook">
|
||||
<!ENTITY cpoles SYSTEM "cpoles.docbook">
|
||||
<!ENTITY credits SYSTEM "credits.docbook">
|
||||
<!ENTITY csphere SYSTEM "csphere.docbook">
|
||||
<!ENTITY darkmatter SYSTEM "darkmatter.docbook">
|
||||
<!ENTITY dumpmode SYSTEM "dumpmode.docbook">
|
||||
<!ENTITY ecliptic SYSTEM "ecliptic.docbook">
|
||||
<!ENTITY ellipgal SYSTEM "ellipticalgalaxies.docbook">
|
||||
<!ENTITY equinox SYSTEM "equinox.docbook">
|
||||
<!ENTITY faq SYSTEM "faq.docbook">
|
||||
<!ENTITY flux SYSTEM "flux.docbook">
|
||||
<!ENTITY geocoords SYSTEM "geocoords.docbook">
|
||||
<!ENTITY greatcircle SYSTEM "greatcircle.docbook">
|
||||
<!ENTITY horizon SYSTEM "horizon.docbook">
|
||||
<!ENTITY hourangle SYSTEM "hourangle.docbook">
|
||||
<!ENTITY indi SYSTEM "indi.docbook">
|
||||
<!ENTITY install SYSTEM "install.docbook">
|
||||
<!ENTITY julianday SYSTEM "julianday.docbook">
|
||||
<!ENTITY leapyear SYSTEM "leapyear.docbook">
|
||||
<!ENTITY lightcurves SYSTEM "lightcurves.docbook">
|
||||
<!ENTITY luminosity SYSTEM "luminosity.docbook">
|
||||
<!ENTITY magnitude SYSTEM "magnitude.docbook">
|
||||
<!ENTITY meridian SYSTEM "meridian.docbook">
|
||||
<!ENTITY parallax SYSTEM "parallax.docbook">
|
||||
<!ENTITY precession SYSTEM "precession.docbook">
|
||||
<!ENTITY quicktour SYSTEM "quicktour.docbook">
|
||||
<!ENTITY retrograde SYSTEM "retrograde.docbook">
|
||||
<!ENTITY sidereal SYSTEM "sidereal.docbook">
|
||||
<!ENTITY skycoords SYSTEM "skycoords.docbook">
|
||||
<!ENTITY spiralgal SYSTEM "spiralgalaxies.docbook">
|
||||
<!ENTITY stars SYSTEM "stars.docbook">
|
||||
<!ENTITY timezones SYSTEM "timezones.docbook">
|
||||
<!ENTITY tool-aavso SYSTEM "lightcurves.docbook">
|
||||
<!ENTITY tool-altvstime SYSTEM "altvstime.docbook">
|
||||
<!ENTITY tool-calculator SYSTEM "calculator.docbook">
|
||||
<!ENTITY tool-details SYSTEM "details.docbook">
|
||||
<!ENTITY tool-whatsup SYSTEM "wut.docbook">
|
||||
<!ENTITY tool-scriptbuilder SYSTEM "scriptbuilder.docbook">
|
||||
<!ENTITY tool-solarsys SYSTEM "solarsys.docbook">
|
||||
<!ENTITY tool-jmoons SYSTEM "jmoons.docbook">
|
||||
<!ENTITY tool-observinglist SYSTEM "observinglist.docbook">
|
||||
<!ENTITY tool-fitsviewer SYSTEM "fitsviewer.docbook">
|
||||
<!ENTITY tools SYSTEM "tools.docbook">
|
||||
<!ENTITY utime SYSTEM "utime.docbook">
|
||||
<!ENTITY zenith SYSTEM "zenith.docbook">
|
||||
<!ENTITY % addindex "INCLUDE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
<title>The &kstars; Handbook</title>
|
||||
<bookinfo>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
<affiliation>
|
||||
<address><email>&Jason.Harris.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Heiko</firstname>
|
||||
<surname>Evermann</surname>
|
||||
<affiliation>
|
||||
<address><email>&Heiko.Evermann.mail;</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Thomas</firstname>
|
||||
<surname>Kabelmann</surname>
|
||||
<affiliation>
|
||||
<address><email>&Thomas.Kabelmann.mail;</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Pablo</firstname>
|
||||
<surname>de Vicente</surname>
|
||||
<affiliation>
|
||||
<address><email>&Pablo.de.Vicente.mail;</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation>
|
||||
<address><email>mutlaqja@ikarustech.com</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Carsten</firstname>
|
||||
<surname>Niehaus</surname>
|
||||
<affiliation>
|
||||
<address><email>cniehaus@gmx.de</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
|
||||
<othercredit role="developer">
|
||||
<firstname>Mark</firstname>
|
||||
<surname>Holloman</surname>
|
||||
<affiliation>
|
||||
<address><email>&Mark.Holloman.mail;</email></address>
|
||||
</affiliation>
|
||||
<contrib>Core Developer</contrib>
|
||||
</othercredit>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001</year><year>2002</year><year>2003</year>
|
||||
<holder>&Jason.Harris; and the &kstars; Team</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2002-10-08</date>
|
||||
<releaseinfo>1.0</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kstars; is a graphical desktop planetarium for &kde;. It depicts an
|
||||
accurate simulation of the night sky, including stars, constellations,
|
||||
star clusters, nebulae, galaxies, all planets, the Sun, the Moon,
|
||||
comets and asteroids. You can see the sky as it appears
|
||||
from any location on Earth, on any date. The user interface is highly
|
||||
intuitive and flexible; the display can be panned and zoomed with the
|
||||
mouse, and you can easily identify objects, and track their motion
|
||||
across the sky. &kstars; includes many powerful features, yet the
|
||||
interface is clean and simple, and fun to use.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>Astronomy</keyword>
|
||||
<keyword>KStars</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>
|
||||
&kstars; lets you explore the night sky from
|
||||
the comfort of your computer chair. It provides an accurate graphical
|
||||
representation of the night sky for any date, from any location on
|
||||
Earth. The display includes 126,000 stars to 9th magnitude (well below
|
||||
the naked-eye limit), 13,000 deep-sky objects (Messier, NGC, and IC
|
||||
catalogs), all planets, the Sun and Moon, hundreds of comets and
|
||||
asteroids, the Milky Way, 88 constellations, and guide lines such as
|
||||
the <link linkend="ai-cequator">celestial equator</link>,
|
||||
the <link linkend="ai-horizon">horizon</link> and
|
||||
the <link linkend="ai-ecliptic">ecliptic</link>.
|
||||
</para>
|
||||
<para>
|
||||
However, &kstars; is more than a simple night-sky simulator. The
|
||||
display provides a compelling interface to a number of tools with
|
||||
which you can learn more about astronomy and the night sky. There is
|
||||
a context-sensitive <link linkend="popup-menu">popup menu</link>
|
||||
attached to each displayed object, which displays object-specific
|
||||
information and actions. Hundreds of objects provide links in their
|
||||
popup menus to informative web pages and beautiful images taken by the
|
||||
Hubble Space Telescope and other observatories.
|
||||
</para><para>
|
||||
From an object's popup menu, you can open its <link
|
||||
linkend="tool-details">Detailed Information Window</link>, where
|
||||
you can examine positional data about the object, and query a huge
|
||||
treasury of online databases for professional-grade astronomical data
|
||||
and literature references about the object. You can even attach your
|
||||
own Internet links, images and text notes, making &kstars; a graphical
|
||||
front-end to your observing logs and your personal astronomical notebook.
|
||||
</para>
|
||||
<para>
|
||||
Our <link linkend="tool-calculator">Astrocalculator</link> tool
|
||||
provides direct access to many of the algorithms the program uses
|
||||
behind the scenes, including coordinate converters and time
|
||||
calculators. The <link linkend="tool-aavso">AAVSO Lightcurve
|
||||
Generator</link> tool will download a lightcurve for any of the 6000+
|
||||
variable stars monitored by the American Association of Variable Star
|
||||
Observers (AAVSO). The lightcurves are generated <quote>on the
|
||||
fly</quote> by querying the AAVSO server directly, ensuring that you
|
||||
have the very latest data points.
|
||||
</para>
|
||||
<para>
|
||||
You can plan an observing session using our <link
|
||||
linkend="tool-altvstime">Altitude vs. Time</link> tool, which will
|
||||
plot curves representing the Altitude as a function of time for any
|
||||
group of objects. If that is too much detail, we also provide a
|
||||
<link linkend="tool-whatsup">What's Up Tonight?</link> tool that
|
||||
summarizes the objects that you will be able to see from your location
|
||||
on any given night. You can add your favorite objects to the <link
|
||||
linkend="tool-observinglist">Observing List</link> tool, which
|
||||
provides convenient access to common actions for a list of objects.
|
||||
</para>
|
||||
<para>
|
||||
&kstars; also provides a <link linkend="tool-solarsys">Solar System
|
||||
Viewer</link>, which shows the current configuration of the major
|
||||
planets in our solar system. There is also a <link
|
||||
linkend="tool-jmoons">Jupiter Moons Tool</link> which shows the positions
|
||||
of Jupiter's four largest moons as a function of time.
|
||||
</para>
|
||||
<para>
|
||||
Our primary goal is to make &kstars; an interactive educational tool for
|
||||
learning about astronomy and the night sky. To this end, the &kstars;
|
||||
Handbook includes the <link linkend="astroinfo">AstroInfo
|
||||
Project</link>, a series of short, hyperlinked articles on astronomical
|
||||
topics that can be explored with &kstars;. In addition, &kstars;
|
||||
includes &DCOP; functions that allow you to <link
|
||||
linkend="tool-scriptbuilder">write complex scripts</link>, making &kstars;
|
||||
a powerful "demo engine" for classroom use or general illustration of
|
||||
astronomical topics.
|
||||
</para>
|
||||
<para>
|
||||
However, &kstars; is not just for students. You can control telescopes
|
||||
and cameras with &kstars;, using the elegant and powerful <link
|
||||
linkend="indi">INDI</link> protocol. &kstars; supports several popular
|
||||
telescopes including Meade's LX200 family and Celestron GPS. Several
|
||||
popular CCD cameras, webcams, and computerized focusers are also supported.
|
||||
Simple slew/track commands are integrated directly into the main window's
|
||||
popup menu, and the INDI Control Panel provides full access to all of
|
||||
your telescope's functions. Many of these actions can also be scripted
|
||||
through &kde;'s &DCOP; mechanism (our own <link
|
||||
linkend="tool-scriptbuilder">Script Builder</link> tool provides a simple
|
||||
point-and-click interface for these scripts). INDI's Client/Server
|
||||
architecture allows for seamless control of any number of <link
|
||||
linkend="indi-kstars-setup">local</link> or <link
|
||||
linkend="indi-remote-control">remote</link> telescopes using a single
|
||||
&kstars; session.
|
||||
</para>
|
||||
<para>
|
||||
We are very interested in your feedback; please report bugs or
|
||||
feature requests to the &kstars; development mailing list:
|
||||
<email>kstars-devel@kde.org</email>. You can also use
|
||||
the automated bug reporting tool, accessible from the Help menu.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
&quicktour; <!--A Quick Tour of KStars-->
|
||||
&config; <!--Configuring KStars-->
|
||||
&commands; <!--Command Reference-->
|
||||
&astroinfo; <!--AstroInfo Articles-->
|
||||
&tools; <!--KStars Tools-->
|
||||
&dumpmode; <!--Command-line image-dump mode-->
|
||||
&indi; <!-- INDI-->
|
||||
&faq; <!--Questions and Answers-->
|
||||
&credits; <!--Credits and License-->
|
||||
&install; <!--Installation-->
|
||||
|
||||
<index id='doc-index'></index>
|
||||
<!-- For DocBook 4.2, remove the above line and use this instead
|
||||
&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,835 @@
|
||||
<chapter id="indi">
|
||||
<title>Astronomical Device Control with <acronym>INDI</acronym></title>
|
||||
<indexterm><primary>INDI Control</primary>
|
||||
<secondary>Overview</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>KStars provides an interface to configure and control astronomical instruments via
|
||||
the <acronym><link linkend="what-is-indi">INDI</link></acronym> protocol.</para>
|
||||
|
||||
<para>The <acronym>INDI</acronym> protocol supports a variety of astronomical instruments
|
||||
such as CCD cameras and focusers. Currently, KStars supports the following
|
||||
devices:</para>
|
||||
|
||||
<table id="device-table" pgwide="1" frame="all">
|
||||
<title>Supported Telescopes</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Telescope</entry>
|
||||
<entry>Device driver</entry>
|
||||
<entry>Version</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>LX200 8"-12" Classic</entry>
|
||||
<entry>lx200classic</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Autostar based telescopes</entry>
|
||||
<entry>lx200autostar</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>LX200 GPS 8"-16"</entry>
|
||||
<entry>lx200gps</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>LX200 Classic 16"</entry>
|
||||
<entry>lx200_16</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>NexStar GPS, CGE, AS-GT</entry>
|
||||
<entry>celestrongps</entry>
|
||||
<entry>0.9</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>New GT, NexStar 5i/8i</entry>
|
||||
<entry>celestrongps</entry>
|
||||
<entry>0.9</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Takahashi Temma</entry>
|
||||
<entry>temma</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Astro-Physics AP</entry>
|
||||
<entry>apmount</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Astro-Electronic FS-2</entry>
|
||||
<entry>lx200basic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Argo Navis</entry>
|
||||
<entry>lx200basic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Losmandy Gemini</entry>
|
||||
<entry>lx200basic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Mel Bartels Controllers</entry>
|
||||
<entry>lx200basic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Sky Commander</entry>
|
||||
<entry>skycommander</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
<table id="focuser-table" pgwide="1" frame="all">
|
||||
<title>Supported Focusers</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Focuser</entry>
|
||||
<entry>Device driver</entry>
|
||||
<entry>Version</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Meade LX200GPS Microfocuser</entry>
|
||||
<entry>lx200gps</entry>
|
||||
<entry>0.9</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Meade 1206 Primary Mirror Focuser</entry>
|
||||
<entry>lx200generic</entry>
|
||||
<entry>0.9</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>JMI NGF Series</entry>
|
||||
<entry>lx200generic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>JMI MOTOFOCUS</entry>
|
||||
<entry>lx200generic</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table id="ccd-table" pgwide="1" frame="all">
|
||||
<title>Supported CCDs</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>CCD</entry>
|
||||
<entry>Device driver</entry>
|
||||
<entry>Version</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Finger Lakes Instruments CCDs</entry>
|
||||
<entry>fliccd</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Santa Barbara Instrument CCDs</entry>
|
||||
<entry>sbigccd</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Apogee CCDs</entry>
|
||||
<entry>apogee_ppi, apogee_pci, apogee_isa, apogee_usb</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table id="filter-table" pgwide="1" frame="all">
|
||||
<title>Supported Filter Wheels</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Filter Wheel</entry>
|
||||
<entry>Device driver</entry>
|
||||
<entry>Version</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>FLI Filter Wheels</entry>
|
||||
<entry>fliwheel</entry>
|
||||
<entry>0.9</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<table id="video-table" pgwide="1" frame="all">
|
||||
<title>Supported Webcams</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>Webcam</entry>
|
||||
<entry>Device driver</entry>
|
||||
<entry>Version</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Any Video4Linux compatible device</entry>
|
||||
<entry>v4ldriver</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Philips webcam</entry>
|
||||
<entry>v4lphilips</entry>
|
||||
<entry>1.0</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Meade Lunar Planetary Imager</entry>
|
||||
<entry>meade_lpi</entry>
|
||||
<entry>0.1</entry>
|
||||
</row>
|
||||
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<sect1 id="indi-kstars-setup">
|
||||
<title>INDI Setup</title>
|
||||
<indexterm><primary>INDI</primary>
|
||||
<secondary>Setup</secondary>
|
||||
</indexterm>
|
||||
<para>
|
||||
KStars can control local and remote devices seamlessly via the <link linkend="what-is-indi">INDI</link> server/client architecture. INDI devices may be run in three different modes:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem><para>Local: The local mode is the most common and is used to control local device (&ie; a device attached to your machine).</para></listitem>
|
||||
<listitem><para>Server: The server mode establishes an INDI server for a particular device and waits for connections from remote clients. You cannot operate server devices, you can only start and shut them down.</para></listitem>
|
||||
<listitem><para>Client: The client mode is used to connect to remote INDI servers running INDI devices. You can control remote devices seamlessly like local devices.</para></listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>You can run local device, establish INDI servers, and connect to remote clients from the <guimenuitem>Device Manager</guimenuitem> in the <guimenu>Devices</guimenu> menu.</para>
|
||||
|
||||
<para>Here is a screenshot of the <guilabel>Device Manager</guilabel>
|
||||
window:</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Running device drivers</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="devicemanager.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Start device drivers</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>You can run devices by browsing the device tree, selecting a specific device, and then clicking on the <guibutton>Run Service button</guibutton>. You can select the operation mode, either local or server as defined above.</para>
|
||||
|
||||
<para>To control remove devices, refer to the <link linkend="indi-remote-control">remote device control</link> section.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-telescope-setup">
|
||||
<title>Telescope Setup</title>
|
||||
<indexterm><primary>INDI</primary>
|
||||
<secondary>Setup</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>Most telescopes are equipped with <hardware>RS232</hardware> interface
|
||||
for remote control. Connect the RS232 jack in your telescope to your
|
||||
computer's <hardware>Serial/USB</hardware> port. Traditionally, the RS232
|
||||
connects to the serial port of your computer, but since many new laptops
|
||||
abandoned the serial port in favor of <hardware>USB/FireWire</hardware>
|
||||
ports, you might need to obtain a Serial to USB adaptor to use with new
|
||||
laptops.</para>
|
||||
|
||||
<para>After connecting your telescope to the Serial/USB port, turn your
|
||||
telescope on. It is <emphasis>highly</emphasis> recommended that you
|
||||
download and install the latest firmware for your telescope
|
||||
controller.</para>
|
||||
|
||||
<para>The telescope needs to be aligned before it can be used properly.
|
||||
Align your telescope (one or two stars alignment) as illustrated in your
|
||||
telescope manual.</para>
|
||||
|
||||
<para>&kstars; needs to verify time and location settings before connecting to the telescope. This insures proper tracking and synchronization between the telescope and &kstars;. The following steps will enable you to connect to a device that is connected to your computer. To connect and control remote devices, please refer to <link linkend="indi-remote-control">remote device control</link> section.</para>
|
||||
|
||||
<para>You can use the Telescope Setup Wizard and it will verify all the required information in the process. It can automatically scan ports for attached telescopes. You can run the wizard by selecting <guimenuitem>Telescope Setup Wizard</guimenuitem> from the <guimenu>Devices</guimenu> menu.</para>
|
||||
|
||||
<para>Alternatively, you can connect to a local telescope by performing the following
|
||||
steps:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem><para>Set your geographical location. Open the <guilabel>Geographic...</guilabel> window by selecting
|
||||
<guimenuitem>Set Geographic Location...</guimenuitem> from the
|
||||
<guimenu>Settings</guimenu> menu, or by pressing the <guiicon>Globe</guiicon> icon in the toolbar, or by pressing <keycombo
|
||||
action="simul">&Ctrl;<keycap>g</keycap></keycombo>.</para>
|
||||
</listitem>
|
||||
<listitem><para>Set your local time and date. You can change to any time or
|
||||
date by selecting <guimenuitem>Set Time...</guimenuitem> from the <guimenu>Time</guimenu> menu, or by
|
||||
pressing the <guiicon>time</guiicon> icon in the toolbar. The <guilabel>Set Time</guilabel> window uses a standard &kde; Date Picker widget, coupled with three spinboxes for setting the hours, minutes and seconds. If you ever need to reset the clock back to the current time, just select <guimenuitem>Set Time to Now</guimenuitem> from the <guimenu>Time</guimenu> menu.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Click on the <guimenu>Devices</guimenu> menu and select the
|
||||
<guimenuitem>Device Manager</guimenuitem>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Under the <guilabel>Device</guilabel> column, select your telescope model.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para> <mousebutton>Right</mousebutton>-click on the device and select
|
||||
<guilabel>Run Service</guilabel>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Click <guibutton>Ok</guibutton> to close the Device Manager
|
||||
Dialog.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<note id="geo-time-note">
|
||||
<title>Frequent Settings</title>
|
||||
<para>You do not need to set the geographic location and time every time you connect to a telescope. Only adjust the settings as needed.</para></note>
|
||||
|
||||
<para>You are now ready to use the device features, &kstars; conveniently provides two interchangeable GUI interfaces for controlling telescopes:</para>
|
||||
|
||||
<orderedlist>
|
||||
<title>Controlling your telescope</title>
|
||||
<listitem>
|
||||
<para>
|
||||
<guilabel>Sky map Control</guilabel>: For each device you run in the <guilabel>Device Manager</guilabel>, a corresponding entry will show up in popup menu that allows you to control the properties of the device. You can
|
||||
issue commands like <command>Slew, Sync,</command> and
|
||||
<command>Track</command> directly from the sky map.
|
||||
</para>
|
||||
<para>Here is a screenshot of the popup menu with an active LX200 Classic
|
||||
device:</para>
|
||||
<screenshot>
|
||||
<screeninfo>Controlling devices from sky map</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="skymapdevice.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<guilabel>INDI Control Panel</guilabel>: The panel offers the user with all the
|
||||
features supported by a device.
|
||||
</para>
|
||||
|
||||
<para>The panel is divided into three main sections:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
<guilabel>Device tabs</guilabel>: Each additional active device occupies a
|
||||
tab in the INDI panel. Multiple devices can run simultaneously without
|
||||
affecting the operation of other devices.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<guilabel>Property view</guilabel>: Properties are the key element in INDI
|
||||
architecture. Each device defines a set of properties to communicate with
|
||||
the client. The current position of the telescope is an example of a
|
||||
property. Semantically similar properties are usually contained in logical
|
||||
blocks or groupings.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<guilabel>Log viewers</guilabel>: Devices report their status and acknowledge commands by sending INDI messages. Each device has its own log view, and all devices share one generic log viewer. A device usually sends messages to its device driver only, but a device is permitted to send a generic message when appropriate.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<screenshot>
|
||||
<screeninfo>INDI Control Panel</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="indicontrolpanel.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>You are not restricted on using one interface over another as they can be both used simultaneously. Actions from the <guilabel>Sky map</guilabel> are automatically reflected in the <guilabel>INDI Control Panel</guilabel>
|
||||
and vice versa.</para>
|
||||
|
||||
<para>To connect to your telescope, you can either select <guimenuitem>Connect</guimenuitem> from your device popup menu or
|
||||
alternatively, you can press <guibutton>Connect</guibutton> under your device tab in the <guilabel>INDI Control Panel</guilabel>.</para>
|
||||
|
||||
<important><para>By default, KStars will try to connect to the <constant>/dev/ttyS0</constant>
|
||||
port. To change the connection port, select <guilabel>INDI Control Panel</guilabel> from the <guimenu>Devices</guimenu> menu and change the port under your device tab.</para></important>
|
||||
|
||||
<para>&kstars; automatically updates the telescope's longitude, latitude, and
|
||||
time based on current settings in &kstars;. You can enable/disable these
|
||||
updates from <guimenuitem>Configure INDI</guimenuitem> dialog under the
|
||||
<guimenu>Devices</guimenu> menu.
|
||||
</para>
|
||||
|
||||
<para>If &kstars; communicates successfully with the telescope, it will retrieve the current <abbrev>RA</abbrev> and <abbrev>DEC</abbrev> from the telescope and will display a crosshair on the sky map indicating the telescope position.</para>
|
||||
|
||||
<note id="indi-sync">
|
||||
<title>Synchronizing your telescope</title>
|
||||
<para>If you aligned your telescope and the last alignment star was, for example, Vega, then the crosshair should be centered around Vega. If the crosshair was off target, then you can <mousebutton>right</mousebutton>-click Vega from the sky map and select
|
||||
<command>Sync</command> from your telescope menu. This action will instruct the telescope to synchronize its internal coordinates to match those of Vega, and the telescope's crosshair should now be centered around Vega.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
<para>That is it: your telescope is ready to explore the heavens.</para>
|
||||
|
||||
<warning>
|
||||
<title>WARNING</title>
|
||||
<para>Never use the telescope to look at the sun. Looking at the sun might cause irreversible damage to your eyes and as well as your equipment.</para>
|
||||
</warning>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-other-setup">
|
||||
<title>CCD and Video-Capture Setup</title>
|
||||
<indexterm><primary>CCD Video Control</primary>
|
||||
<secondary>Setup</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>KStars supports the following imaging devices:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Finger Lakes instruments CCDs</para></listitem>
|
||||
<listitem><para>Apogee CCDs: Parallel, ISA, PCI, and USB modes are supported. You need to install <ulink url="http://indi.sf.net/apogee_kernel.tar.gz">Apogee kernel drivers</ulink> for your specific mode (for USB mode, you only need libusb).</para></listitem>
|
||||
<listitem><para><ulink url="http://www.exploits.org/v4l/">Video4Linux</ulink> compatible devices. Philips webcam extended features are supported as well.</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>You can run CCD and Video Capture devices from the <guimenuitem>Device Manager</guimenuitem> in the <guimenu>Devices</guimenu> menu. Like all INDI devices, some of the device controls will be accessible from the skymap. The device can be controlled fully from the <guimenuitem>INDI Control Panel.</guimenuitem></para>
|
||||
|
||||
<para>The standard format for image capture is FITS. Once an image is captured and downloaded, it will be automatically displayed in the KStars <link linkend="tool-fitsviewer">FITS Viewer</link>. To capture a sequence of images, use the <guimenuitem>Capture Image Sequence</guimenuitem> tool from the <guimenu>Devices</guimenu> menu. This tool is inactive until you establish a connection to an image device.</para>
|
||||
|
||||
<important>
|
||||
<para>The FLICCD driver requires root privileges in order to operate properly. Note that running the driver as root is considered a security risk</para>
|
||||
</important>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-capture">
|
||||
<title>Capture Image Sequence</title>
|
||||
<indexterm><primary>Capture</primary>
|
||||
<secondary>Image</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>The Capture Image Sequence tool can be used to aquire images from cameras and CCDs in interactive and batch modes. Furthermore, you can select which filter, if any, you want to use for your images. The capture tool remains disabled until you establish a connection to an imaging device.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Capture Image Sequence</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="indicapture.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The above screenshot depicts a sample capture session. The tool provides the following options:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Camera/CCD</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Device:</option> The desired imaging device.</para></listitem>
|
||||
<listitem><para><option>Prefix:</option> The image prefix which will be prepended to each captured filename.</para></listitem>
|
||||
<listitem><para><option>Exposure:</option> The number of seconds to expose each frame.</para></listitem>
|
||||
<listitem><para><option>Count:</option> The number of images to aquire.</para></listitem>
|
||||
<listitem><para><option>Delay:</option> The delay in seconds between consecutive images.</para></listitem>
|
||||
<listitem><para><option>ISO 8601 time stamp:</option> Append ISO 8601 time stamp to the filename. (e.g. image_01_20050427T09:48:05).</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Filter</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Device:</option> The desired filter device.</para></listitem>
|
||||
<listitem><para><option>Filter:</option> The desired filter slot. You can assign color values to slot numbers using the <link linkend="indi-configure">Configure INDI</link> window (e.g. Slot #1 = Red, Slot #2 = Blue..etc).</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>After you fill in the desired options, you can begin the capture procedure by pressing the <guibutton>Start</guibutton> button. You may cancel at any time using the <guibutton>Stop</guibutton> button. All captured images will be saved to the default FITS directory which can be specified in the <link linkend="indi-configure">Configure INDI</link> window.</para>
|
||||
|
||||
<para>If you have more complex capturing requirements and conditions to fulfil, it is recommended to create a script to meet your specific needs using the <link linkend="tool-scriptbuilder">Script Builder</link> tool in the <guimenu>Tools</guimenu> menu.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-configure">
|
||||
<title>Configure INDI</title>
|
||||
<indexterm><primary>Configure</primary>
|
||||
<secondary>INDI</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>The Configure INDI window allows you to modify <emphasis>Client side</emphasis> INDI specific options. The window is divided into four main categories: General, Automatic device updates, Display, and Filter Wheel:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para>General</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Default FITS directory:</option> Specify the directory where all captured FITS images will be saved to. If no directory is specified, images will be stored in $HOME.</para></listitem>
|
||||
<listitem><para><option>Automatic Display of FITS upon capture:</option> When checked, KStars will display captured FITS in KStars <link linkend="tool-fitsviewer">FITS Viewer</link> tool. If you use the <link linkend="indi-capture">Capture Image Sequence</link> tool, all captured images will be saved to disk regardless of this option.</para></listitem>
|
||||
<listitem><para><option>Telescope port:</option> The default telescope port. When you connect to a local or remote telescope service, KStars will automatically fill the telescope's device port with the specified default port.</para></listitem>
|
||||
<listitem><para><option>Video port:</option> The default video port. When you connect to a local or remote video service, KStars will automatically fill the webcam's device port with the specified default port.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Automatic device updates</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Time:</option> Update the telescope's date and time, if supported, upon connection.</para></listitem>
|
||||
<listitem><para><option>Geographic location:</option> Update the telescope's geographical location information (current longitude and latitude), if supported, upon connection.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Display</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Device target crosshair:</option> When checked, KStars displays the telescope's target crosshair on the sky map. The crosshair is displayed upon a successful connection to the telescope and its location is updated periodically. The telescope's name is displayed next to the crosshair. KStars displays one crosshair per each connected telescope. To change the color of the telescope's crosshair, open the <link linkend="viewops">Configure KStars</link> window. Select the <guilabel>Colors</guilabel> tab, and then change the color of the <emphasis>Target Indicator</emphasis> item to the desired color.</para></listitem>
|
||||
<listitem><para><option>INDI messages in status bar:</option> When checked, KStars displays INDI status messages in the KStars status bar.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Filter Wheel: Assign color codes to the filter wheel slots (e.g. Slot #0 Red, Slot #1 Blue..etc). You can assign color codes for up to 10 filter slots (0 to 9). To assign a color code, select a slot number from the drop down combo box, and then type the corresponding color code in the edit field. Repeat the process for all desired slots and then press OK.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-concepts">
|
||||
<title>INDI Concepts</title>
|
||||
<indexterm><primary>Telescope Control</primary>
|
||||
<secondary>Concepts</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
The main key concept in INDI is that devices have the ability to describe themselves. This is accomplished by using XML to describe a generic hierarchy that can represent both canonical and non-canonical devices. In INDI, all <emphasis>devices</emphasis> may contain one or more <emphasis>properties</emphasis>. Any <emphasis>property</emphasis> may contain one or more <emphasis>elements</emphasis>. There are four types of INDI properties:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>Text property.</para></listitem>
|
||||
<listitem><para>Number property.</para></listitem>
|
||||
<listitem><para>Switch property (Represented in GUI by buttons and checkboxes).</para></listitem>
|
||||
<listitem><para>Light property (Represented in GUI by colored LEDs).</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>For example, all INDI devices share the CONNECTION standard switch <emphasis>property</emphasis>. The CONNECTION property has two elements: CONNECT and DISCONNECT switches. KStars parses the generic XML description of properties and builds a GUI representation suitable for direct human interaction.</para>
|
||||
|
||||
<para>The INDI control panel offers many device properties not accessible from the sky map. The properties offered differ from one device to another. Nevertheless, all properties share common features that constrains how they are displayed and used:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
Permission: All properties can either be read-only, write-only, or read and
|
||||
write enabled. An example of a read-write property is the telescope's Right
|
||||
Ascension. You can enter a new Right Ascension and the telescope, based on
|
||||
current settings, will either slew or sync to the new input. Furthermore,
|
||||
when the telescope slews, its Right Ascension gets updated and sent back to
|
||||
the client.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>State: Prefixed to each property is a state indicator (round LED).
|
||||
Each property has a state and an associated color code:</para>
|
||||
<table frame="top"><title>INDI State color code</title>
|
||||
<tgroup cols="3" colsep="1" rowsep="1">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>State</entry>
|
||||
<entry>Color</entry>
|
||||
<entry>Description</entry>
|
||||
</row>
|
||||
</thead>
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>Idle</entry>
|
||||
<entry>Gray</entry>
|
||||
<entry>Device is performing no action with respect to this property</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Ok</entry>
|
||||
<entry>Green</entry>
|
||||
<entry>Last operation performed on this property was successful and
|
||||
active</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Busy</entry>
|
||||
<entry>Yellow</entry>
|
||||
<entry>The property is performing an action</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>Alert</entry>
|
||||
<entry>Red</entry>
|
||||
<entry>The property is in critical condition and needs immediate
|
||||
attention</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
|
||||
<para>The device driver updates the property state in real-time when
|
||||
necessary. For example, if the telescope is in the process of slewing to a
|
||||
target, then the RA/DEC properties will be signaled as
|
||||
<guilabel>Busy</guilabel>. When the slew process is completed successfully,
|
||||
the properties will be signaled as
|
||||
<guilabel>Ok</guilabel>.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Context: Numerical properties can accept and process numbers in two formats:
|
||||
decimal and sexagesimal. The sexagesimal format is convenient when expressing
|
||||
time or equatorial/geographical coordinates. You can use any format at your
|
||||
convenience. For example, all the following numbers are equal:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para>-156.40</para></listitem>
|
||||
<listitem><para>-156:24:00</para></listitem>
|
||||
<listitem><para>-156:24</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Time: The standard time for all INDI-related communications is Universal Time UTC specified as YYYY-MM-DDTHH:MM:SS in accord with ISO 8601. &kstars; communicates the correct UTC time with device drivers automatically. You can enable/disable automatic time updates from the <guimenuitem>Configure INDI</guimenuitem> dialog under the <guimenu>Devices</guimenu> menu.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-remote-control">
|
||||
<title>Remote Device Control</title>
|
||||
<indexterm><primary>Telescope Control</primary>
|
||||
<secondary>Remote Devices</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>KStars provides a simple yet powerful layer for remote device control.
|
||||
A detailed description of the layer is described in the INDI <ulink
|
||||
url="http://www.clearskyinstitute.com/INDI/INDI.pdf">white
|
||||
paper</ulink>.</para>
|
||||
|
||||
<para>You need to configure both the server and client machines for remote
|
||||
control:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Server: To prepare a device for remote control, follow the same steps in the <link linkend="indi-kstars-setup">local/server</link> setup. When you start a device service in the <guimenu>Device Manager</guimenu>, a port number is displayed under the <guilabel>Listening port</guilabel> column. In addition to the port number, you also need the hostname or IP address of your server.
|
||||
</para>
|
||||
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Client: Select the <guimenuitem>Device Manager</guimenuitem> from the <guimenu>Device</guimenu> menu and click on the <guilabel>Client</guilabel> tab. You can add, modify, or delete hosts under the <guilabel>Client</guilabel> tab. Add a host by clicking on the <guibutton>Add</guibutton> button. Enter the hostname/IP address of the server in the <guilabel>Host</guilabel> field, and enter the port number obtained from the <emphasis>server</emphasis> machine in step 1.
|
||||
</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>INDI Client</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="indiclient.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>After you add a host, right click on the host to
|
||||
<guimenuitem>Connect</guimenuitem> or <guimenuitem>Disconnect</guimenuitem>.
|
||||
If a connection is established, you can control the telescope from the
|
||||
<guilabel>Sky map</guilabel> or <guilabel>INDI Control Panel</guilabel>
|
||||
exactly as described in the <link linkend="indi-kstars-setup">local/server</link> section. It is as easy at that.
|
||||
</para>
|
||||
|
||||
<sect2 id="indi-commandline">
|
||||
<title>Running an INDI server from the command line</title>
|
||||
<para>While &kstars; allows you to easily deploy an INDI server; you can launch an INDI server from the command line.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Since INDI is an independent backend component, you can run an INDI server on a host without KStars. INDI can be compiled separately to run on remote hosts. Furthermore, device drivers log messages to <constant>stderr</constant> and that can be helpful in a debugging situation. The syntax for INDI server is
|
||||
as following:</para>
|
||||
|
||||
<para>$ <command>indiserver</command> [options] [<filename>driver</filename>
|
||||
...]</para>
|
||||
|
||||
<para>Options:</para>
|
||||
<para> -p p : alternate IP port, default 7624</para>
|
||||
<para> -r n : max restart attempts, default 2</para>
|
||||
<para> -v : more verbose to stderr</para>
|
||||
|
||||
<para>For example, if you want to start an INDI server running an LX200 GPS
|
||||
driver and listening to connections on port 8000, you would run the
|
||||
following command:</para>
|
||||
|
||||
<para>$ <command>indiserver</command> -p 8000 <filename>lx200gps</filename></para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="indi-secure-remote">
|
||||
<title>Secure Remote Operation</title>
|
||||
|
||||
<para>Suppose we want to run an indiserver with INDI drivers on a remote host,
|
||||
<constant>remote_host</constant>, and connect them to &kstars; running on the local machine.</para>
|
||||
|
||||
<para>From the local machine log onto the remote host, <constant>remote_host</constant>, by typing:</para>
|
||||
|
||||
<para>$ <command>ssh</command> -L <varname>local_port</varname>:<constant>remote_host</constant>:<varname>remote_port</varname></para>
|
||||
|
||||
<para>This binds the <varname>local_port</varname> on the local machine to the <varname>remote_port</varname> on the <constant>remote_host</constant>. After logging in, run indiserver on the remote host:</para>
|
||||
|
||||
<para>$ <command>indiserver</command> -p <varname>remote_port</varname> [<filename>driver</filename>...]</para>
|
||||
|
||||
<para>Back on the local machine, start &kstars; then open the <guimenuitem>Device Manager</guimenuitem> and add a host under the <guilabel>Client</guilabel> tab. The host should be the local host (usually 127.0.0.1) and the port number should be the <varname>local_port</varname> used in the steps above. <mousebutton>Right</mousebutton>-click on the host and select <guimenuitem>Connect</guimenuitem> from the popup menu. &kstars; will connect to the remote INDI server securely. The host information will be saved for future sessions.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="indi-faq">
|
||||
<title>INDI Frequently Asked Questions</title>
|
||||
<indexterm><primary>Telescope Control</primary>
|
||||
<secondary><acronym>FAQ</acronym></secondary>
|
||||
</indexterm>
|
||||
|
||||
<qandaset defaultlabel="qanda">
|
||||
<qandaentry>
|
||||
<question id="what-is-indi">
|
||||
<para>What is INDI?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para> <acronym>INDI</acronym> is the <ulink url="http://indi.sourceforge.net"> Instrument-Neutral-Distributed-Interface</ulink> control protocol developed by <author><firstname>Elwood</firstname><surname>C.
|
||||
Downey</surname></author> of <ulink url="http://www.clearskyinstitute.com/">ClearSky Institute</ulink>. &kstars; employs device drivers that are compatible with the INDI protocol. INDI has many advantages including loose coupling between hardware devices and
|
||||
software drivers. Clients that use the device drivers (like &kstars;) are completely unaware of the device capabilities. In run time, &kstars; communicates with the device drivers and builds a completely dynamical GUI based on services provided by the device. Therefore, new device drivers can be written or updated and KStars can take full advantage of them without any changes on the client side.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
Do you plan to support more devices?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes. We plan to support major CCD cameras and focusers and extend support
|
||||
for more telescopes. If you would like INDI to support a particular device,
|
||||
please send an email to <email>indi-devel@lists.sourceforge.net</email>
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
What operations does KStars provide to control the telescope?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
It depends on the particular telescope you're running, but the minimum three operations are <command>Slew</command>, <command>Track</command>, and <command>Sync</command>, which you can issue directly from the sky map. Your telescope must be aligned for those operations to perform correctly. Some telescopes offer you more operations like site management, slew modes, focusing, parking, and more. You can access the telescopes extended features from the INDI Control Panel in the Devices Menu.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
What's the difference between <command>Slew</command>, <command>Track</command>, and <command>Sync</command> exactly?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The command <command>Slew</command> orders the telescope to move to a particular target, and once the telescope reaches its target, the telescope keeps tracking that target at a <emphasis>sidereal</emphasis> rate (i.e. the rate at which stars move across the sky). This works well for stars, Messier objects, and about everything outside our solar system. But solar system objects travel differently across the sky and so the telescope must <command>Track</command> the objects as they move.
|
||||
</para>
|
||||
<para>
|
||||
Therefore, you need to issue a track command if you want to track an object with non-sidereal motion. On the other hand, <command>Sync</command> is used to synchronize the telescope's internal coordinates with that of an object you select.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
Can I control my telescope remotely?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes. You can start an INDI server on the machine connected to your telescope and the server will listen to requests from &kstars; clients. Once you're connected, you can control your telescope directly from the sky map. This procedure is described in detail in the <link linkend="indi-remote-control">Remote device control</link> section.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>
|
||||
When I try to <guibutton>Connect</guibutton>, &kstars; reports that the
|
||||
telescope is not connected to the serial/USB port. What can I do?
|
||||
</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>This message is triggered when &kstars; cannot communicate with the telescope. Here are few things you can do:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Check that you have both reading and writing permission for the port you are trying to connect to.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Check the connection cable, make sure it is in good condition and test it with other applications.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Check your telescope power, make sure the power is on and that the telescope is getting enough power.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Set the correct port in the <guilabel>INDI Control Panel</guilabel>
|
||||
under the <guimenu>Devices</guimenu> menu. The default device is
|
||||
<constant>/dev/ttyS0</constant></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Restart &kstars; and retry again.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>&kstars; reports that the telescope is online and ready, but I cannot find the telescope's crosshair, where is it?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>&kstars; retrieves the telescopes RA and DEC coordinates upon connection. If your alignment was performed correctly, then you should see the crosshair around your target in the Sky Map. However, the RA and DEC coordinates provided by the telescope may be incorrect (even below the horizon) and you need to <link linkend="indi-sync">Sync</link> your telescope to your current target. You can use the right-click menu to center and track the telescope crosshair in the sky map.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The telescope is moving erratically or not moving at all. What can I do?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>This behavior is mostly due to incorrect settings, please verify the following check list:</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Is the telescope aligned?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Is the telescope alignment mode correct? Use <guilabel>INDI Control Panel</guilabel> to check and change these settings (<constant>Alt/Az,Polar, Land</constant>).</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Are the telescope's time and date settings correct?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Are the telescope's longitude and latitude settings correct?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Is the telescope's UTC offset correct?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Are the telescope's RA and DEC axis locked firmly?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Is the telescope's N/S switch (when applicable) setup correctly for your hemisphere?</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Is the cable between the telescope and computer in good condition?</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>If you think all settings are correct but the telescope still moves erratically or not at all, then please send a report to
|
||||
<email>kstars-devel@kde.org</email></para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 110 KiB |
@ -0,0 +1,105 @@
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kstars">
|
||||
<title>How to obtain &kstars;</title>
|
||||
<para>
|
||||
&kstars; is distributed with &kde; as part of the kdeedu "Edutainment"
|
||||
module.
|
||||
</para>
|
||||
<para>
|
||||
We also occasionally make an independent release. These independent
|
||||
releases will be available as a gzipped tar archive from the following
|
||||
website:
|
||||
<ulink
|
||||
url="http://prdownloads.sourceforge.net/kstars/">http://prdownloads.sourceforge.net/kstars/</ulink>.
|
||||
</para>
|
||||
<para>
|
||||
Independent releases are announced through the
|
||||
<email>kstars-announce@lists.sourceforge.net</email> mailing list.
|
||||
Releases are also posted to <ulink url="http://edu.kde.org/kstars">the
|
||||
&kstars; home page</ulink>,
|
||||
<ulink url="http://www.kde-apps.org/content/show.php?content=9862">kde-apps.org</ulink>, and
|
||||
<ulink url="http://freshmeat.net/projects/kstars">freshmeat.net</ulink>.
|
||||
</para>
|
||||
<para>
|
||||
&kstars; is been packaged by many Linux/BSD distributions, including Redhat, Suse,
|
||||
and Mandrake. Some distributions package &kstars; as a separate application, some
|
||||
just provide a kdeedu package, which includes &kstars;.
|
||||
</para><para>
|
||||
If you would like the latest CVS development version of &kstars;, please
|
||||
follow <ulink url="http://edu.kde.org/kstars/cvs.html">these instructions</ulink>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="requirements">
|
||||
<title>Requirements</title>
|
||||
<para>
|
||||
In order to successfully run &kstars;, you need &kde; >=3.2 and
|
||||
&Qt;>=3.2.
|
||||
</para>
|
||||
<para>
|
||||
To compile &kstars;, you will also have to have the following packages
|
||||
installed:
|
||||
<itemizedlist>
|
||||
<listitem><para>kdelibs-devel</para></listitem>
|
||||
<listitem><para>qt-devel</para></listitem>
|
||||
<listitem><para>zlib-devel</para></listitem>
|
||||
<listitem><para>fam-devel</para></listitem>
|
||||
<listitem><para>png-devel</para></listitem>
|
||||
<listitem><para>jpeg-devel</para></listitem>
|
||||
<listitem><para>autoconf (>=2.5)</para></listitem>
|
||||
</itemizedlist></para>
|
||||
|
||||
<para>
|
||||
On my system, &kstars; uses about 60 MB of system memory with the
|
||||
default settings. Most of this usage is due to the loaded object
|
||||
databases. You can dramatically reduce the memory footprint by
|
||||
reducing the faint limit for stars in the Configuration Window, or
|
||||
eliminating catalogs of objects (NGC, IC, comets, asteroids, &etc;).
|
||||
If &kstars; is idling, it uses very little <acronym>CPU</acronym>;
|
||||
but it will use as much as you have got when panning or zooming.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
<para>
|
||||
In order to compile and install &kstars; on your system, type the
|
||||
following in the base folder of the unpacked &kstars; distribution:
|
||||
<screen width="40">
|
||||
<prompt>%</prompt> <userinput>./configure --prefix=$KDEDIR</userinput>
|
||||
<prompt>%</prompt> <userinput>make</userinput>
|
||||
<prompt>%</prompt> <userinput>make install</userinput>
|
||||
</screen>
|
||||
</para><para>
|
||||
Please do not forget the prefix argument to configure. If your <envar>KDEDIR</envar>
|
||||
variable is not set, set prefix to whatever folder &kde; is installed in: this is
|
||||
usually either <filename class="directory">/usr</filename>,
|
||||
<filename class="directory">/opt/kde</filename>, or
|
||||
<filename class="directory">/opt/kde3</filename>.
|
||||
Also, make sure you do the
|
||||
last step as <systemitem class="username">root</systemitem>.
|
||||
</para><para>
|
||||
&kstars; uses <command>autoconf</command> and <command>automake</command>,
|
||||
so you should not have trouble compiling it. Should you run into problems
|
||||
please report them to the &kstars; mailing list
|
||||
<email>kstars-devel@kde.org</email>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="configuration">
|
||||
<title>Configuration</title>
|
||||
<para>
|
||||
At this point, there are no special configuration options or
|
||||
requirements. If &kstars; complains that there are missing data files,
|
||||
become <systemitem class="username">root</systemitem> and manually copy
|
||||
all files in <filename class="directory">kstars/data/</filename> to
|
||||
<filename class="directory">$(KDEDIR)/apps/kstars/</filename> (If you
|
||||
do not have <systemitem class="username">root</systemitem> privileges,
|
||||
copy them to
|
||||
<filename class="directory">~/.kde/share/apps/kstars/.</filename>)
|
||||
</para>
|
||||
</sect1>
|
||||
</appendix>
|
||||
@ -0,0 +1,38 @@
|
||||
<sect1 id="tool-jmoons">
|
||||
<title>Jupiter Moons Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Jupiter Moons Tool</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Jupiter Moons Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="jmoons.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Jupiter Moons Tool</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This tool displays the positions of Jupiter's four largest
|
||||
moons (Io, Europa, Ganymede, and Callisto) relative to Jupiter,
|
||||
as a function of time. Time is plotted vertically; the units are days
|
||||
and <quote>time=0.0</quote> corresponds to the current simulation time.
|
||||
The horizontal axis displays the angular offset from Jupiter's position,
|
||||
in arcminutes. The offset is measured along the direction of Jupiter's
|
||||
equator. Each moon's position as a function of time traces a sinusoidal
|
||||
path in the plot, as the moon orbits around Jupiter. Each track is
|
||||
assigned a different color to distinguish it from the others; the name
|
||||
labels at the top of the window indicate the color used by each moon.
|
||||
</para><para>
|
||||
The plot can be manipulated with the keyboard. The time axis can be
|
||||
expanded or compressed using the <keycap>+</keycap> and
|
||||
<keycap>-</keycap> keys. The time displayed at the center of the window
|
||||
can be changed with the <keycap>[</keycap> and <keycap>]</keycap> keys.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 22 KiB |
@ -0,0 +1,58 @@
|
||||
<sect1 id="ai-julianday">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>John</firstname>
|
||||
<surname>Cirillo</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Julian Day</title>
|
||||
<indexterm><primary>Julian Day</primary>
|
||||
</indexterm>
|
||||
<para>
|
||||
Julian Days are a way of reckoning the current date by a simple count of
|
||||
the number of days that have passed since some remote, arbitrary date. This
|
||||
number of days is called the <firstterm>Julian Day</firstterm>,
|
||||
abbreviated as <abbrev>JD</abbrev>. The starting point, <abbrev>JD=0</abbrev>,
|
||||
is January 1, 4713 BC (or -4712 January 1, since there was no year '0'). Julian
|
||||
Days are very useful because they make it easy to determine the number of days
|
||||
between two events by simply subtracting their Julian Day numbers.
|
||||
Such a calculation is difficult for the standard (Gregorian) calendar, because
|
||||
days are grouped into months, which contain a variable number of days, and
|
||||
there is the added complication of <link linkend="ai-leapyear">Leap
|
||||
Years</link>.
|
||||
</para><para>
|
||||
Converting from the standard (Gregorian) calendar to Julian Days and vice versa
|
||||
is best left to a special program written to do this, such as the &kstars;
|
||||
<link linkend="tool-calculator">Astrocalculator</link>. However, for those
|
||||
interested, here is a simple example of a Gregorian to Julian day converter:
|
||||
</para><para>
|
||||
<abbrev>JD</abbrev> = <abbrev>D</abbrev> - 32075 + 1461*( <abbrev>Y</abbrev> +
|
||||
4800 + ( <abbrev>M</abbrev> - 14 ) / 12 ) / 4 + 367*( <abbrev>M</abbrev> - 2 -
|
||||
( <abbrev>M</abbrev> - 14 ) / 12 * 12 ) / 12 - 3*( ( <abbrev>Y</abbrev> + 4900 +
|
||||
( <abbrev>M</abbrev> - 14 ) / 12 ) / 100 ) / 4
|
||||
</para><para>
|
||||
where <abbrev>D</abbrev> is the day (1-31), <abbrev>M</abbrev> is the Month
|
||||
(1-12), and <abbrev>Y</abbrev> is the year (1801-2099). Note that this formula
|
||||
only works for dates between 1801 and 2099. More remote dates require a more
|
||||
complicated transformation.
|
||||
</para><para>
|
||||
An example Julian Day is: <abbrev>JD</abbrev> 2440588, which corresponds to
|
||||
1 Jan, 1970.
|
||||
</para><para>
|
||||
Julian Days can also be used to tell time; the time of day is expressed as a
|
||||
fraction of a full day, with 12:00 noon (not midnight) as the zero point. So,
|
||||
3:00 pm on 1 Jan 1970 is <abbrev>JD</abbrev> 2440588.125 (since 3:00 pm is 3
|
||||
hours since noon, and 3/24 = 0.125 day). Note that the Julian Day is always
|
||||
determined from <link linkend="ai-utime">Universal Time</link>, not Local Time.
|
||||
</para><para>
|
||||
Astronomers use certain Julian Day values as important reference points, called
|
||||
<firstterm>Epochs</firstterm>. One widely-used epoch is called J2000; it is the
|
||||
Julian Day for 1 Jan, 2000 at 12:00 noon = <abbrev>JD</abbrev> 2451545.0.
|
||||
</para><para>
|
||||
Much more information on Julian Days is available on the internet. A good
|
||||
starting point is the <ulink
|
||||
url="http://aa.usno.navy.mil/faq/docs/JD_Formula.html">U.S. Naval
|
||||
Observatory</ulink>. If that site is not available when you read this, try
|
||||
searching for <quote>Julian Day</quote> with your favorite search engine.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 62 KiB |
|
After Width: | Height: | Size: 406 B |
|
After Width: | Height: | Size: 1.1 KiB |
|
After Width: | Height: | Size: 762 B |
@ -0,0 +1,65 @@
|
||||
<sect1 id="ai-leapyear">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Leap Years</title>
|
||||
<indexterm><primary>Leap Years</primary>
|
||||
</indexterm>
|
||||
<para>
|
||||
The Earth has two major components of motion. First, it spins on its rotational
|
||||
axis; a full spin rotation takes one <firstterm>Day</firstterm> to complete.
|
||||
Second, it orbits around the Sun; a full orbital rotation takes one
|
||||
<firstterm>Year</firstterm> to complete.
|
||||
</para><para>
|
||||
There are normally 365 days in one <emphasis>calendar</emphasis> year, but it
|
||||
turns out that a <emphasis>true</emphasis> year (&ie;, a full orbit of the Earth
|
||||
around the Sun; also called a <firstterm>tropical year</firstterm>) is a little
|
||||
bit longer than 365 days. In other words, in the time it takes the Earth to
|
||||
complete one orbital circuit, it completes 365.24219 spin rotations. Do not be
|
||||
too surprised by this; there is no reason to expect the spin and orbital motions
|
||||
of the Earth to be synchronized in any way. However, it does make marking
|
||||
calendar time a bit awkward....
|
||||
</para><para>
|
||||
What would happen if we simply ignored the extra 0.24219 rotation at the end of
|
||||
the year, and simply defined a calendar year to always be 365.0 days long? The
|
||||
calendar is basically a charting of the Earth's progress around the Sun. If we
|
||||
ignore the extra bit at the end of each year, then with every passing year, the
|
||||
calendar date lags a little more behind the true position of Earth around the
|
||||
Sun. In just a few decades, the dates of the solstices and equinoxes will have
|
||||
drifted noticeably.
|
||||
</para><para>
|
||||
In fact, it used to be that all years <emphasis>were</emphasis> defined to have
|
||||
365.0 days, and the calendar <quote>drifted</quote> away from the true seasons
|
||||
as a result. In the year 46 <abbrev>BCE</abbrev>, Julius Caeser established the
|
||||
<firstterm>Julian Calendar</firstterm>, which implemented the world's first
|
||||
<firstterm>leap years</firstterm>: He decreed that every 4th year would be 366
|
||||
days long, so that a year was 365.25 days long, on average. This basically
|
||||
solved the calendar drift problem.
|
||||
</para><para>
|
||||
However, the problem wasn't completely solved by the Julian calendar, because a
|
||||
tropical year isn't 365.25 days long; it's 365.24219 days long. You still have
|
||||
a calendar drift problem, it just takes many centuries to become
|
||||
noticeable. And so, in 1582, Pope Gregory XIII instituted the
|
||||
<firstterm>Gregorian calendar</firstterm>, which was largely the same as the
|
||||
Julian Calendar, with one more trick added for leap years: even Century years
|
||||
(those ending with the digits <quote>00</quote>) are only leap years if they are divisible by
|
||||
400. So, the years 1700, 1800, and 1900 were not leap years (though they would
|
||||
have been under the Julian Calendar), whereas the year 2000
|
||||
<emphasis>was</emphasis> a leap year. This change makes the average length of a
|
||||
year 365.2425 days. So, there is still a tiny calendar drift, but it amounts to
|
||||
an error of only 3 days in 10,000 years. The Gregorian calendar is still used as
|
||||
a standard calendar throughout most of the world.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
Fun Trivia: When Pope Gregory instituted the Gregorian Calendar, the Julian
|
||||
Calendar had been followed for over 1500 years, and so the calendar date had
|
||||
already drifted by over a week. Pope Gregory re-synchronized the calendar by
|
||||
simply <emphasis>eliminating</emphasis> 10 days: in 1582, the day after October
|
||||
4th was October 15th!
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 28 KiB |
@ -0,0 +1,176 @@
|
||||
<sect1 id="tool-aavso">
|
||||
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Aaron</firstname>
|
||||
<surname>Price</surname>
|
||||
<affiliation><address>
|
||||
<email>aavso@aavso.org</email>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>AAVSO Light Curves</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>AAVSO Lightcurve Generator</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The AAVSO Lightcurves Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="aavso.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>AAVSO Lightcurves</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<sect2 id="aavso-intro">
|
||||
<title>Introduction</title>
|
||||
<para>
|
||||
&kstars; can display light curves for variable stars from the observing
|
||||
program of the <ulink url="http://www.aavso.org">American Association
|
||||
of Variable Star Observers</ulink> (<abbrev>AAVSO</abbrev>). This
|
||||
program monitors over 6,000 variable stars and consists of 10 million
|
||||
observations going back almost a century. &kstars; downloads the very
|
||||
latest data directly from the <abbrev>AAVSO</abbrev> database via the
|
||||
Internet, so a network connection is required to use this tool.
|
||||
</para>
|
||||
<para>
|
||||
To use the tool, select a variable star either by
|
||||
<firstterm>designation</firstterm> or name in the left panel, and
|
||||
set the start and end dates to be plotted. In the right panel,
|
||||
select the type of data that should be plotted (see below). When you have
|
||||
made you selections, press the <guibutton>Retrieve Curve</guibutton>
|
||||
button. &kstars; will automatically connect to the AAVSO server,
|
||||
which will generate the lightcurve plot and send it to your computer for
|
||||
display. A sample lightcurve plot is shown below:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
A Sample Lightcurve
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="lightcurve.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Sample Lightcurve</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Please not these light curves should <emphasis>NEVER</emphasis> be used
|
||||
in research, papers, presentations, publications, &etc;. They are only
|
||||
meant to be used as a source of info for &kstars;. They have not been
|
||||
validated and passed the <abbrev>AAVSO</abbrev>'s strict quality control
|
||||
measures. We will be glad to give you good raw data simply by requesting
|
||||
it at <ulink url="http://www.aavso.org/adata/onlinedata/">http://www.aavso.org/adata/onlinedata/</ulink>.
|
||||
</para>
|
||||
<para>
|
||||
Specific questions about the data in the light curves can be sent to
|
||||
<email>aavso@aavso.org</email>.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="aavso-about">
|
||||
<title>About Variable Stars</title>
|
||||
<para>
|
||||
<firstterm>Variable stars</firstterm> are stars that change in
|
||||
brightness. A <firstterm>light curve</firstterm> is a plot of a
|
||||
variable star's brightness over time. By looking at a light curve you
|
||||
can see how the star has behaved in the past and try to predict how it
|
||||
will behave in the future. Astronomers also use this data to model
|
||||
astrophysical processes in the star. This important to help us
|
||||
understand how stars work.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="aavso-data">
|
||||
<title>The Data</title>
|
||||
|
||||
<para>
|
||||
Here is a summary of the various types of data available in the light
|
||||
curves:
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><firstterm>Visual Observation</firstterm>:
|
||||
This is an observation of a variable star by an observer with a
|
||||
regular telescope. It means that an observer saw the star at Y
|
||||
brightness on X date and time.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>Fainter than</firstterm>:
|
||||
Sometimes the star is too faint to be seen by the observer. When that
|
||||
happens, the observer reports the faintest star seen in the field.
|
||||
These are called <quote>fainter thans</quote> because the variable star
|
||||
was fainter than the brightness reported.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>Average</firstterm>:
|
||||
This is a computed running average of all the data reported. The
|
||||
<firstterm>bin</firstterm> number tells the computer how many days to
|
||||
use in each average calculation. This will need to be adjusted based on
|
||||
the frequency of observations. The error bars represent the 1 sigma
|
||||
standard deviation of error.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>CCDV</firstterm>:
|
||||
These are observations reported using a <abbrev>CCD</abbrev> with a
|
||||
Johnson <abbrev>V</abbrev> filter. <abbrev>CCDV</abbrev> observations
|
||||
tend to be more accurate than visual (but not
|
||||
always).</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>CCDB</firstterm>:
|
||||
<abbrev>CCD</abbrev> observations with a Johnson <abbrev>B</abbrev>
|
||||
filter.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>CCDI</firstterm>:
|
||||
<abbrev>CCD</abbrev> observations with a Cousins <abbrev>Ic</abbrev>
|
||||
filter.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>CCDR</firstterm>:
|
||||
<abbrev>CCD</abbrev> observations with a Cousins <abbrev>R</abbrev>
|
||||
filter.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>Discrepant Data</firstterm>:
|
||||
This is data that has been flagged by an <abbrev>AAVSO</abbrev> staff
|
||||
member as being discrepant following <abbrev>HQ</abbrev> rules for
|
||||
data validation. Contact <email>aavso@aavso.org</email> for more
|
||||
information.</para></listitem>
|
||||
|
||||
<listitem><para><firstterm>Dates</firstterm>:
|
||||
The observational database the light curves are based on is updated
|
||||
every 10 minutes so you can get data in near real-time. Right now
|
||||
light curve data is only available back to 1961, but this will likely
|
||||
be expanded further back in time in the future.</para></listitem>
|
||||
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="aavso-update">
|
||||
<title>Updating your local copy of Variable Stars</title>
|
||||
<para>
|
||||
The <abbrev>AAVSO</abbrev> publishes the
|
||||
<ulink url="http://www.aavso.org/valnam.txt">full list of variable
|
||||
stars</ulink> in their monitoring program. This file is updated
|
||||
monthly with newly discovered variable stars. To sync the list that
|
||||
&kstars; uses with the <abbrev>AAVSO</abbrev> master list, click
|
||||
on the <guibutton>Update List</guibutton> button in the
|
||||
<abbrev>AAVSO</abbrev> dialog. &kstars; will then attempt to
|
||||
connect to the <abbrev>AAVSO</abbrev> database and download the
|
||||
latest list.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
The customized data stream provided by the AAVSO was implemented for
|
||||
&kstars; by Aaron Price. Thank you, Aaron!
|
||||
</para>
|
||||
</note>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
@ -0,0 +1,54 @@
|
||||
<sect1 id="ai-luminosity">
|
||||
|
||||
<sect1info>
|
||||
|
||||
<author>
|
||||
<firstname>Jasem</firstname>
|
||||
<surname>Mutlaq</surname>
|
||||
<affiliation><address>
|
||||
</address></affiliation>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Luminosity</title>
|
||||
<indexterm><primary>Luminosity</primary>
|
||||
<seealso>Flux</seealso>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<firstterm>Luminosity</firstterm> is the amount of energy emitted by a star each second.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
All stars radiate light over a broad range of frequencies in the electromagnetic spectrum from the low energy radio waves up to the highly energetic gamma rays. A star that emits predominately in the ultra-violet region of the spectrum produces a total amount of energy magnitudes larger than that produced in a star that emits principally in the infrared.
|
||||
Therefore, luminosity is a measure of energy emitted by a star over all wavelengths. The relationship between wavelength and energy was quantified by Einstein as
|
||||
E = h * v
|
||||
where v is the frequency, h is the Planck constant, and E is the photon energy in joules.
|
||||
That is, shorter wavelengths (and thus higher frequencies) correspond to higher energies.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
For example, a wavelength of lambda = 10 meter lies in the radio region of the electromagnetic spectrum and has a frequency of
|
||||
|
||||
f = c / lambda = 3 * 10^8 m/s / 10 = 30 MHz
|
||||
|
||||
where c is the speed of light.
|
||||
The energy of this photon is
|
||||
|
||||
E = h * v = 6.625 * 10^-34 J s * 30 Mhz = 1.988 * 10^-26 joules.
|
||||
|
||||
On the other hand, visible light has much shorter wavelengths and higher frequencies. A photon that has a wavelength of lambda = 5 * 10^-9 meters (A greenish photon) has an energy
|
||||
E = 3.975 * 10^-17 joules which is over a billion times higher than the energy of a radio photon. Similarly, a photon of red light (wavelength lambda = 700 nm) has less energy
|
||||
than a photon of violet light (wavelength lambda = 400 nm).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Luminosity depends both on temperature and surface area. This makes sense because a burning log radiates more energy than a match, even though both have the same temperature.
|
||||
Similarly, an iron rod heated to 2000 degrees emits more energy than when it is heated to only 200 degrees.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Luminosity is a very fundamental quantity in Astronomy and Astrophysics. Much of what is learnt about celestial objects comes from analyzing their light. This is because the physical processes that occur inside stars gets recorded and transmitted by light.
|
||||
Luminosity is measured in units of energy per second. Astronomers prefer to use Ergs, rather than Watts, when quantifying luminosity.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 490 B |
|
After Width: | Height: | Size: 629 B |
@ -0,0 +1,80 @@
|
||||
<sect1 id="ai-magnitude">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Girish</firstname> <surname>V</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Magnitude Scale</title>
|
||||
<indexterm><primary>Magnitude Scale</primary>
|
||||
<seealso>Flux</seealso>
|
||||
<seealso>Star Colors and Temperatures</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
2500 years ago, the ancient Greek astronomer Hipparchus classified the
|
||||
brightnesses of visible stars in the sky on a scale from 1 to 6. He
|
||||
called the very brightest stars in the sky <quote>first magnitude</quote>, and the
|
||||
very faintest stars he could see <quote>sixth magnitude</quote>. Amazingly, two
|
||||
and a half millenia later, Hipparchus's classification scheme is still
|
||||
widely used by astronomers, although it has since been modernized and
|
||||
quantified.</para>
|
||||
<note><para>The magnitude scale runs backwards to what you
|
||||
might expect: brighter stars have <emphasis>smaller</emphasis>
|
||||
magnitudes than fainter stars.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
The modern magnitude scale is a quantitative measurement of the
|
||||
<firstterm>flux</firstterm> of light coming from a star, with a
|
||||
logarithmic scaling:
|
||||
</para><para>
|
||||
m = m_0 - 2.5 log (F / F_0)
|
||||
</para><para>
|
||||
If you do not understand the math, this just says that the magnitude
|
||||
of a given star (m) is different from that of some standard star (m_0)
|
||||
by 2.5 times the logarithm of their flux ratio. The 2.5 *log factor
|
||||
means that if the flux ratio is 100, the difference in magnitudes is 5
|
||||
mag. So, a 6th magnitude star is 100 times fainter than a 1st magnitude
|
||||
star. The reason Hipparchus's simple classification translates to a
|
||||
relatively complex function is that the human eye responds
|
||||
logarithmically to light.
|
||||
</para><para>
|
||||
There are several different magnitude scales in use, each of which serves
|
||||
a different purpose. The most common is the apparent magnitude scale;
|
||||
this is just the measure of how bright stars (and other objects) look
|
||||
to the human eye. The apparent magnitude scale defines the star Vega
|
||||
to have magnitude 0.0, and assigns magnitudes to all other objects using
|
||||
the above equation, and a measure of the flux ratio of each object to
|
||||
Vega.
|
||||
</para><para>
|
||||
It is difficult to understand stars using just the apparent magnitudes.
|
||||
Imagine two stars in the sky with the same apparent magnitude, so they
|
||||
appear to be equally bright. You cannot know just by looking if the
|
||||
two have the same <emphasis>intrinsic</emphasis> brightness; it is
|
||||
possible that one star is intrinsically brighter, but further away.
|
||||
If we knew the distances to the stars (see the <link
|
||||
linkend="ai-parallax">parallax</link> article), we could account for
|
||||
their distances and assign <firstterm>Absolute magnitudes</firstterm>
|
||||
which would reflect their true, intrinsic brightness. The absolute
|
||||
magnitude is defined as the apparent magnitude the star would have if
|
||||
observed from a distance of 10 parsecs (1 parsec is 3.26 light-years,
|
||||
or 3.1 x 10^18 cm). The absolute magnitude (M) can be determined
|
||||
from the apparent magnitude (m) and the distance in parsecs (d)
|
||||
using the formula:
|
||||
</para><para>
|
||||
M = m + 5 - 5 * log(d) (note that M=m when d=10).
|
||||
</para><para>
|
||||
The modern magnitude scale is no longer based on the
|
||||
human eye; it is based on photographic plates and photoelectric
|
||||
photometers. With telescopes, we can see objects much fainter than
|
||||
Hipparchus could see with his unaided eyes, so the magnitude scale has
|
||||
been extended beyond 6th magnitude. In fact, the Hubble Space Telescope
|
||||
can image stars nearly as faint as 30th magnitude, which is one
|
||||
<emphasis>trillion</emphasis> times fainter than Vega.
|
||||
</para><para>
|
||||
A final note: the magnitude is usually measured through a color filter
|
||||
of some kind, and these magnitudes are denoted by a subscript
|
||||
describing the filter (&ie;, m_V is the magnitude through a <quote>visual</quote>
|
||||
filter, which is greenish; m_B is the magnitude through a blue filter;
|
||||
m_pg is the photographic plate magnitude, &etc;).
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,84 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>celestrongps</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>celestrongps</command></refname>
|
||||
<refpurpose>Celestrong GPS driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>celestrongps</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>celestrongps</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>celestrongps</command> was written by &Jasem.Mutlaq;</para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,86 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>fliccd</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>fliccd</command></refname>
|
||||
<refpurpose>Finger Lakes Instruments CCD driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>fliccd</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>fliccd</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>fliccd</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,136 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>indiserver</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>indiserver</command></refname>
|
||||
<refpurpose>INDI server for telescope control by KStars</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>indiserver</command>
|
||||
<group choice="opt"><option>-p <replaceable>port</replaceable></option></group>
|
||||
<group choice="opt"><option>-r
|
||||
<replaceable>attempts</replaceable></option></group>
|
||||
<group><option>-vv</option></group>
|
||||
<group choice="req" rep="repeat"><option><replaceable>driver</replaceable></option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the INDI protocol.
|
||||
<command>indiserver</command> is a server that sits between the &kstars;
|
||||
user interface and the low-level hardware drivers.</para>
|
||||
<para>The <acronym>INDI</acronym> server is a network server, int hat either
|
||||
local or remote clients may connect to it to control astronomical
|
||||
instruments. The <acronym>INDI</acronym> server must be running on the
|
||||
machine that is physically connected to the astronomical instruments.</para>
|
||||
<note><para>There is usually no need to run the <acronym>INDI</acronym>
|
||||
server directly. Using the &kstars; device manager, you can set up
|
||||
astronomical instruments and start or stop the <acronym>INDI</acronym>
|
||||
server all from within &kstars;</para></note>
|
||||
<para>Much more detailed information is available in the &kstars; handbook,
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde;, and forms part
|
||||
of the &kde; edutainment module.</para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><option>-p <replaceable>port</replaceable></option></term>
|
||||
<listitem><para>Alternate IP port. The default is 7624.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><option>-r
|
||||
<replaceable>attempts</replaceable></option></term>
|
||||
<listitem><para>Maximum attempts to restart, in case of a problem. The
|
||||
default is 2.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><option>-vv</option></term>
|
||||
<listitem><para>Be more verbose with output to stderr.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><option><replaceable>driver</replaceable></option></term>
|
||||
<listitem><para>The names of the <acronym>INDI</acronym> drivers to
|
||||
run.</para>
|
||||
<para>Currently available are:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><parameter>celestrongps</parameter> (Celestron
|
||||
GPS)</para></listitem>
|
||||
<listitem><para><parameter>fliccd</parameter> (Finger Lakes Instruments
|
||||
CCD)</para></listitem>
|
||||
<listitem><para><parameter>lx200_16</parameter> (LX200 16")</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>lx200autostar</parameter> (LX200 Autostar)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>lx200classic</parameter> (LX200 Classic)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>lx200generic</parameter> (LX200 Generic)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>lx200gps</parameter> (LX200 GPS)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>temma</parameter> (Temma Takahashi)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>v4ldriver</parameter> (Video4Linux
|
||||
Generic)</para>
|
||||
</listitem>
|
||||
<listitem><para><parameter>v4lphilips</parameter> (Philips Webcam)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
|
||||
<para>celestrongps(1), fliccd(1), lx200_16(1), lx200autostar(1), lx200classic(1), lx200generic(1), lx200gps(1), kstars(1), temma(1), v4ldriver(1), v4lphilips(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available in the &kstars;
|
||||
handbook, which you can reach from <ulink url="help:/kstars">help:/kstars</ulink> (either enter this
|
||||
<acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command> <parameter>help:/kstars</parameter></userinput>).</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Examples</title>
|
||||
<para>To start an <acronym>INDI</acronym> server running an LX200 GPS
|
||||
driver, and listening to connections on port 8000:</para>
|
||||
<screen><userinput><command>indiserver</command> <option>-p</option> <parameter>8000</parameter> <parameter>lx200gps</parameter></userinput></screen>
|
||||
</refsect1>
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<!--FIXME: Who wrote the indiserver? -->
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>lx200_16</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>lx200_16</command></refname>
|
||||
<refpurpose>LX200 16" driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>lx200_16</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>lx200_16</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>lx200_16</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>lx200autostar</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>lx200autostar</command></refname>
|
||||
<refpurpose>LX200 Autostar driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>lx200autostar</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>lx200autostar</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>lx200autostar</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>lx200classic</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>lx200classic</command></refname>
|
||||
<refpurpose>LX200 Classic driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>lx200classic</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>lx200classic</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>lx200classic</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>lx200gps</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>lx200gps</command></refname>
|
||||
<refpurpose>LX200 GPS driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>lx200gps</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>lx200gps</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>lx200gps</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>temma</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>temma</command></refname>
|
||||
<refpurpose>Temma Takahashi driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>temma</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>temma</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>temma</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>v4ldriver</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>v4ldriver</command></refname>
|
||||
<refpurpose>Video4Linux Generic driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>v4ldriver</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>v4ldriver</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>v4ldriver</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,85 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>May 25, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>v4lphilips</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>v4lphilips</command></refname>
|
||||
<refpurpose>Video4Linux Philips Webcam driver for INDI telescope control</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>v4lphilips</command>
|
||||
<group><option>-v</option></group>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&kstars; allows you to configure and control astronomical instruments
|
||||
such as telescopes and focusers via the <acronym>INDI</acronym> protocol.
|
||||
<command>v4lphilips</command> is a device driver for supporting particular
|
||||
types of external hardware.</para>
|
||||
<para>This driver is not intended to be run directly. Instead you should
|
||||
use &kstars; to configure and operate your astronomical instruments. Most
|
||||
operations can be found under the <guimenu>Devices</guimenu> menu in
|
||||
&kstars;.</para>
|
||||
<para>&kstars; will start the <acronym>INDI</acronym> server internally, and
|
||||
the <acronym>INDI</acronym> server will in turn start this device
|
||||
driver.</para>
|
||||
<para>Much more detailed information can be found in the &kstars; handbook
|
||||
as described below.</para>
|
||||
<para>&kstars; is a graphical desktop planetarium for &kde; and forms part
|
||||
of the official &kde; edutainment module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry><term><option>-v</option></term>
|
||||
<listitem><para>Write more verbose output to stderr</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>indiserver(1), kstars(1)</para>
|
||||
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/kstars">help:/kstars</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/kstars</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at <ulink
|
||||
url="http://edu.kde.org/kstars/">the &kde; Edutainment
|
||||
website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para><command>v4lphilips</command> was written by &Jasem.Mutlaq;</para>
|
||||
<para>This man page based on the one written for Debian by <personname><firstname>Ben</firstname><surname>Burton</surname></personname> <email>bab@debian.org</email></para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
@ -0,0 +1,28 @@
|
||||
<sect1 id="ai-meridian">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Local Meridian</title>
|
||||
<indexterm><primary>Local Meridian</primary>
|
||||
<seealso>Hour Angle</seealso>
|
||||
<seealso>Celestial Sphere</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The Local Meridian is an imaginary <link linkend="ai-greatcircle">Great Circle</link>
|
||||
on the <link linkend="ai-csphere">Celestial Sphere</link> that is perpendicular
|
||||
to the local <link linkend="ai-horizon">Horizon</link>. It passes through the
|
||||
North point on the Horizon, through the <link linkend="ai-cpoles">Celestial
|
||||
Pole</link>, up to the <link linkend="ai-zenith">Zenith</link>, and through the
|
||||
South point on the Horizon.
|
||||
</para><para>
|
||||
Because it is fixed to the local Horizon, stars will appear to drift past
|
||||
the Local Meridian as the Earth spins. You can use an object's <link
|
||||
linkend="equatorial">Right Ascension</link> and the <link
|
||||
linkend="ai-sidereal">Local Sidereal Time</link> to determine when it will
|
||||
cross your Local Meridian (see <link linkend="ai-hourangle">Hour Angle</link>).
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
After Width: | Height: | Size: 34 KiB |
@ -0,0 +1,99 @@
|
||||
<sect1 id="tool-observinglist">
|
||||
<title>Observing List Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Observing List Tool</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Observing List Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="observinglist.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Observing List Tool</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The purpose of the Observing List Tool is to provide convenient
|
||||
access to some common functions for a list of objects chosen by
|
||||
you. Objects are added to the list by using the <quote>Add to
|
||||
List</quote> action in the <link linkend="popup-menu">popup
|
||||
menu</link>, or by simply pressing the <keycap>O</keycap> key
|
||||
to add the currently-selected object.
|
||||
</para>
|
||||
<para>
|
||||
Objects in the list can be sorted by any of the data columns
|
||||
(Name, Right Ascension, Declination, Magnitude, and Type).
|
||||
To perform an action on an object, highlight it in the list,
|
||||
and then press one of the Action buttons at the top of the
|
||||
window. Some actions can be performed while multiple objects
|
||||
are selected; others only operate when one object is selected.
|
||||
The available actions are:
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>Center</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Center the display on the selected object, and begin Tracking
|
||||
it.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Scope</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Point your <link linkend="indi">telescope</link> at the
|
||||
selected object.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Alt vs. Time</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Open the <link linkend="tool-altvstime">Altitude vs. Time
|
||||
Tool</link>, with the selected object(s) preloaded
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Details</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Open the <link linkend="tool-details">Detailed Information
|
||||
Window</link> for the selected object.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>Remove</term>
|
||||
<listitem>
|
||||
<para>
|
||||
Remove the selected object(s) from the observing list.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The Observing List tool is a new feature and is still under
|
||||
development. We are planning to add more features, such as
|
||||
adding objects to the list by selecting a region in the sky, and
|
||||
the ability to save observing lists to disk.
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 51 KiB |
@ -0,0 +1,65 @@
|
||||
<sect1 id="ai-parallax">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>James</firstname> <surname>Lindenschmidt</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Parallax</title>
|
||||
<indexterm><primary>Parallax</primary></indexterm>
|
||||
<indexterm><primary>Astronomical Unit</primary><see>Parallax</see></indexterm>
|
||||
<indexterm><primary>Parsec</primary><see>Parallax</see></indexterm>
|
||||
<para>
|
||||
<firstterm>Parallax</firstterm> is the apparent change of an observed
|
||||
object's position caused by a shift in the observer's position. As an
|
||||
example, hold your hand in front of you at arm's length, and observe
|
||||
an object on the other side of the room behind your hand. Now tilt
|
||||
your head to your right shoulder, and your hand will appear on the
|
||||
left side of the distant object. Tilt your head to your left
|
||||
shoulder, and your hand will appear to shift to the right side of the
|
||||
distant object.
|
||||
</para>
|
||||
<para>
|
||||
Because the Earth is in orbit around the Sun, we observe the sky from
|
||||
a constantly moving position in space. Therefore, we should expect
|
||||
to see an <firstterm>annual parallax</firstterm> effect, in which the
|
||||
positions of nearby objects appear to <quote>wobble</quote> back and forth in
|
||||
response to our motion around the Sun. This does in fact happen, but
|
||||
the distances to even the nearest stars are so great that you need to
|
||||
make careful observations with a telescope to detect
|
||||
it<footnote><para>The ancient Greek astronomers knew about parallax;
|
||||
because they could not observe an annual parallax in the positions of
|
||||
stars, they concluded that the Earth could not be in motion around
|
||||
the Sun. What they did not realize was that the stars are millions of
|
||||
times further away than the Sun, so the parallax effect is impossible
|
||||
to see with the unaided eye.</para></footnote>.
|
||||
</para>
|
||||
<para>
|
||||
Modern telescopes allow astronomers to use the annual parallax to
|
||||
measure the distance to nearby stars, using triangulation. The
|
||||
astronomer carefully measures the position of the star on two dates,
|
||||
spaced six months apart. The nearer the star is to the Sun, the
|
||||
larger
|
||||
the apparent shift in its position will be between the two dates.
|
||||
</para>
|
||||
<para>
|
||||
Over the six-month period, the Earth has moved through half its orbit
|
||||
around the Sun; in this time its position has changed by 2
|
||||
<firstterm>Astronomical Units</firstterm> (abbreviated AU; 1 AU is
|
||||
the distance from the Earth to the Sun, or about 150 million
|
||||
kilometers). This sounds like a really long distance, but even the
|
||||
nearest star to the Sun (alpha Centauri) is about 40
|
||||
<emphasis>trillion</emphasis> kilometers away. Therefore, the annual
|
||||
parallax is very small, typically smaller than one
|
||||
<firstterm>arcsecond</firstterm>, which is only 1/3600 of one degree.
|
||||
A convenient distance unit for nearby stars is the
|
||||
<firstterm>parsec</firstterm>, which is short for "parallax
|
||||
arcsecond". One parsec is the distance a star would have if its
|
||||
observed parallax angle was one arcsecond. It is equal to 3.26
|
||||
light-years, or 31 trillion kilometers<footnote><para>Astronomers
|
||||
like this unit so much that they now use <quote>kiloparsecs</quote> to measure
|
||||
galaxy-scale distances, and <quote>Megaparsecs</quote> to measure intergalactic
|
||||
distances, even though these distances are much too large to have an
|
||||
actual, observable parallax. Other methods are required to determine
|
||||
these distances</para></footnote>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 18 KiB |
@ -0,0 +1,54 @@
|
||||
<sect1 id="ai-precession">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Precession</title>
|
||||
<indexterm><primary>Precession</primary>
|
||||
</indexterm>
|
||||
<para>
|
||||
<firstterm>Precession</firstterm> is the gradual change in the direction of the
|
||||
Earth's spin axis. The spin axis traces a cone, completing a full circuit in
|
||||
26,000 years. If you have ever spun a top or a dreidel, the
|
||||
<quote>wobbling</quote> rotation of the top as it spins is precession.
|
||||
</para><para>
|
||||
Because the direction of the Earth's spin axis changes, so does the location of
|
||||
the <link linkend="ai-cpoles">Celestial Poles</link>.
|
||||
</para><para>
|
||||
The reason for the Earth's precession is complicated. The Earth is not a
|
||||
perfect sphere, it is a bit flattened, meaning the
|
||||
<link linkend="ai-greatcircle">Great Circle</link> of the equator is longer
|
||||
than a <quote>meridonal</quote> great circle that
|
||||
passes through the poles. Also, the Moon and Sun lie outside the Earth's
|
||||
Equatorial plane. As a result, the gravitational pull of the Moon and Sun on
|
||||
the oblate Earth induces a slight <emphasis>torque</emphasis> in addition to a
|
||||
linear force. This torque on the spinning body of the Earth leads to the
|
||||
precessional motion.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
Precession is easiest to see by observing the <link
|
||||
linkend="ai-cpoles">Celestial Pole</link>. To find the pole, first switch to
|
||||
Equatorial Coordinates in the <guilabel>Configure &kstars;</guilabel> window, and
|
||||
then hold down the <keycap>Up arrow</keycap> key until the display stops
|
||||
scrolling. The declination displayed in the center of the
|
||||
<guilabel>Info Panel</guilabel> should be +90 degrees, and the bright star
|
||||
Polaris should be nearly at the center of the screen. Try slewing with the left
|
||||
and right arrow keys. Notice that the sky appears to rotate around the Pole.
|
||||
</para><para>
|
||||
We will now demonstrate Precession by changing the Date to a very remote year,
|
||||
and observing that the location of the Celestial Pole is no longer near Polaris.
|
||||
Open the <guilabel>Set Time</guilabel> window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo>), and set the date
|
||||
to the year 8000 (currently, &kstars; cannot handle dates much more remote than
|
||||
this, but this date is sufficient for our purposes). Notice that the sky
|
||||
display is now centered at a point between the constellations Cygnus and
|
||||
Cepheus. Verify that this is actually the pole by slewing left and right: the
|
||||
sky rotates about this point; in the year 8000, the North celestial pole will no
|
||||
longer be near Polaris.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,376 @@
|
||||
<chapter id="using-kstars">
|
||||
<title>A Quick Tour of &kstars;</title>
|
||||
|
||||
<para>
|
||||
This chapter presents a guided tour of &kstars;, introducing
|
||||
many of its important features.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
Here is a screenshot of the &kstars; main window:
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="screen1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Main Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The above screenshot shows a typical view of the KStars program. You
|
||||
can see the sky display centered on Betelgeuse, the brightest star in
|
||||
the constellation Orion. Orion has just risen above the eastern horizon.
|
||||
Stars are displayed with <link linkend="ai-colorandtemp">realistic
|
||||
colors</link> and relative brightnesses. If you look closely, you can
|
||||
also see the Moon near the left edge of the window. In three corners
|
||||
of the sky display, there are on-screen text labels displaying data on
|
||||
the current time (<quote>LT: 16:41:39 22 Jan 2005</quote>), the current
|
||||
Geographic Location (<quote>Tucson, Arizona, USA</quote>), and the
|
||||
current object in the center of the display (<quote>Focused on: Betelgeuse
|
||||
(alpha Orionis)</quote>). Above the sky display, there are two toolbars.
|
||||
The main toolbar contains shortcuts for
|
||||
<link linkend="kstars-menus">menu functions</link>, as well as a
|
||||
time-step widget which controls how fast the simulation clock runs.
|
||||
The view toolbar contains buttons that toggle the display of different
|
||||
kinds of objects in the sky. At the bottom of the window, there is a
|
||||
status bar which displays the name of any object you click on, and the
|
||||
<link linkend="ai-skycoords">sky coordinates</link> (both
|
||||
Right Ascension/Declination and Azimuth/Altitude) of the mouse cursor.
|
||||
</para>
|
||||
|
||||
<sect1 id="startwizard">
|
||||
<title>The Setup Wizard</title>
|
||||
<para>
|
||||
<indexterm><primary>Setup Wizard</primary></indexterm>
|
||||
The first time you run KStars, you will be presented with a Setup Wizard,
|
||||
which allows you to easily set your geographic location and download some
|
||||
extra data files. You can press the <guilabel>Finish</guilabel> button
|
||||
at any time to exit the Setup Wizard.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The first page of the Setup Wizard allows you to choose the starting
|
||||
geographic location, by selecting from the list of the 2500+ known
|
||||
locations on the right side of the window. The list of locations can be
|
||||
filtered to match the text you enter in the <guilabel>City</guilabel>,
|
||||
<guilabel>Province</guilabel>, and <guilabel>Country</guilabel> edit
|
||||
boxes. If your desired location is not present in the list, you can
|
||||
select a nearby city instead for now. Later on, you can add your
|
||||
precise location manually using the <link linkend="setgeo">Set Geographic
|
||||
Location tool</link>. Once you have selected a starting location, press
|
||||
the <guilabel>Next</guilabel> button.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The second page of the Setup Wizard allows you to download extra data
|
||||
that are not included with the standard distribution of &kstars;.
|
||||
Simply press the <guilabel>Download Extra Data</guilabel> button to open
|
||||
the <guilabel>Get New Stuff</guilabel> tool. When you are all done,
|
||||
press the <guilabel>Finish</guilabel> button in the Setup Wizard to
|
||||
start exploring &kstars;.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
The Download Extra Data tool is only available if you have KDE 3.3.x
|
||||
installed.
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="lookaround">
|
||||
<title>Have a Look Around</title>
|
||||
<para>
|
||||
<indexterm><primary>Navigation Controls</primary>
|
||||
<secondary>Basics</secondary></indexterm>
|
||||
Now that we have the time and location set, let us have a look around.
|
||||
You can pan the display using the arrow keys. If you hold down the
|
||||
&Shift; key before panning, the scrolling speed is increased. The
|
||||
display can also be panned by clicking and dragging with the mouse.
|
||||
Note that while the display is scrolling, not all objects are
|
||||
displayed. This is done to cut down on the <acronym>CPU</acronym> load
|
||||
of recomputing object positions, which makes the scrolling smoother
|
||||
(you can configure what gets hidden while scrolling in the <link
|
||||
linkend="config">Configure &kstars;</link> window).
|
||||
|
||||
There are seven ways to change the magnification (or
|
||||
<firstterm>Zoom level</firstterm>) of the display:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Use the <keycap>+</keycap> and
|
||||
<keycap>-</keycap> keys</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Press the Zoom In/Zoom Out buttons in the toolbar</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Select
|
||||
<guimenuitem>Zoom In</guimenuitem>/<guimenuitem>Zoom Out</guimenuitem>
|
||||
from the <guimenu>View</guimenu> menu</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Select <guimenuitem>Zoom to Angular Size...</guimenuitem> from
|
||||
the <guimenu>View</guimenu> menu. This allows you to specify the
|
||||
the field-of-view angle for the display, in degrees.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Use the scroll wheel on your mouse</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Drag the mouse up and down with the &MMB; pressed.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Hold down &Ctrl; while dragging the mouse. This
|
||||
will allow you to define a rectangle in the map. When you release the mouse
|
||||
button, the display will zoom to match the rectangle.</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>Notice that as you zoom in, you can see fainter stars than at
|
||||
lower zoom settings.</para>
|
||||
|
||||
<para>
|
||||
Zoom out until you can see a green curve; this represents your local
|
||||
<link linkend="ai-horizon">horizon</link>. If you have not adjusted
|
||||
the default &kstars; configuration, the display will be solid green
|
||||
below the horizon, representing the solid ground of the Earth. There
|
||||
is also a white curve, which represents the <link
|
||||
linkend="ai-cequator">celestial equator</link>, and a tan curve, which
|
||||
represents the <link linkend="ai-ecliptic">Ecliptic</link>, the path
|
||||
that the Sun appears to follow across the sky over the course of a
|
||||
year. The Sun is always found somewhere along the Ecliptic, and the
|
||||
planets are never far from it.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="skyobjects">
|
||||
<title>Objects in the Sky</title>
|
||||
<para>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Overview</secondary></indexterm>
|
||||
&kstars; displays thousands of celestial objects: stars, planets,
|
||||
comets, asteroids, clusters, nebulae and galaxies. You can interact
|
||||
with displayed objects to perform actions on them or obtain more
|
||||
information about them. Clicking on an object will identify it in the
|
||||
status bar, and simply hovering the mouse cursor on an object will label
|
||||
it temporarily in the map. Double-clicking will recenter the display on
|
||||
the object and begin tracking it (so that it will remain centered as
|
||||
time passes). <mousebutton>Right</mousebutton> clicking an object opens
|
||||
the object's popup menu, which provides more options.
|
||||
</para>
|
||||
|
||||
<sect2 id="popupquick">
|
||||
<title>The Popup Menu</title>
|
||||
<indexterm><primary>Popup Menu</primary><secondary>Example</secondary></indexterm>
|
||||
|
||||
<para>
|
||||
Here is an example of the <mousebutton>right</mousebutton> click popup
|
||||
menu, for the Orion Nebula:
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Popup Menu for M 42</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="popup.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Popup Menu for M 42</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The appearance of the popup menu depends somewhat on the kind of
|
||||
object you <mousebutton>right</mousebutton>-click on, but the basic
|
||||
structure is listed below. You can get
|
||||
<link linkend="popup-menu">more detailed information about the popup
|
||||
menu</link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The top section contains information labels (which are not selectable).
|
||||
The top one to three labels display the object's name(s) and object
|
||||
type. The next three labels show the object's rise, transit, and
|
||||
set times. If the rise and set times say "circumpolar", it means that
|
||||
the object is always above the horizon for the present location.
|
||||
</para>
|
||||
<para>
|
||||
The middle section contains items for performing actions on the
|
||||
object, such as <guimenuitem>Center and Track</guimenuitem>,
|
||||
<guimenuitem>Details...</guimenuitem>, and
|
||||
<guimenuitem>Attach Label</guimenuitem>. See the <link
|
||||
linkend="popup-menu">popup menu description</link> for a full list
|
||||
and description of each action.
|
||||
</para>
|
||||
<para>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Internet Links</secondary>
|
||||
<seealso>Popup Menu</seealso></indexterm>
|
||||
The bottom section contains links to images and/or informative webpages
|
||||
about the selected object. If you know of an additional &URL; with
|
||||
information or an image of the object, you can add a custom link to the
|
||||
object's popup menu using the <guimenuitem>Add Link...</guimenuitem>
|
||||
item.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="findobjects">
|
||||
<title>Finding Objects</title>
|
||||
<indexterm><primary>Find Object Tool</primary></indexterm>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Finding by Name</secondary></indexterm>
|
||||
<para>
|
||||
You can search for named objects using the <guilabel>Find
|
||||
Object</guilabel> tool, which can be opened by clicking on the
|
||||
<guiicon>search</guiicon> icon in the toolbar, by selecting
|
||||
<guimenuitem>Find Object...</guimenuitem> from the
|
||||
<guimenu>Pointing</guimenu> menu, or by pressing
|
||||
<keycombo action="simul">&Ctrl;<keycap>F</keycap></keycombo>.
|
||||
The <guilabel>Find Object</guilabel> window is shown below:
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Find Object Window</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="find.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Find Object Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The window contains a list of all the named objects that &kstars; is
|
||||
aware of. Many of the objects only have a numeric catalog name (for
|
||||
example, NGC 3077), but some objects have a common name as well (for
|
||||
example, Whirlpool Galaxy). You can filter the list by name and
|
||||
by object type. To filter by name, enter a string in the edit box
|
||||
at the top of the window; the list will then only contain names
|
||||
which start with that string. To filter by type, select a type
|
||||
from the combo box at the bottom of the window.
|
||||
</para><para>
|
||||
To center the display on an object, highlight the desired object in
|
||||
the list, and press <guibutton>Ok</guibutton>. Note that if the
|
||||
object is below the horizon, the program will warn you that you may
|
||||
not see anything except the ground (you can make the ground invisible
|
||||
in the <guilabel>Display Options</guilabel> window, or by pressing the
|
||||
<guiicon>Ground</guiicon> button in the View toolbar).
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="centertrack">
|
||||
<title>Centering and Tracking</title>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Tracking</secondary></indexterm>
|
||||
<para>
|
||||
&kstars; will automatically begin tracking on an object whenever one
|
||||
is centered in the display, either by using the <guilabel>Find
|
||||
Object</guilabel> window, by double-clicking on it, or by
|
||||
selecting <guimenuitem>Center and Track</guimenuitem> from its
|
||||
<mousebutton>right</mousebutton>-click popup menu. You can disengage
|
||||
tracking by panning the display, pressing the <guiicon>Lock</guiicon>
|
||||
icon in the Main toolbar, or selecting <guimenuitem>Track
|
||||
Object</guimenuitem> from the <guimenu>Pointing</guimenu> menu.
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
<indexterm><primary>Orbit Trails</primary>
|
||||
<secondary>Attached to centered object</secondary>
|
||||
</indexterm>
|
||||
When tracking on a Solar System body, &kstars; will automatically
|
||||
attach an <quote>orbit trail</quote>, showing the path of the body
|
||||
across the sky. You will likely need to change the clock's timestep
|
||||
to a large value (such as <quote>1 day</quote>) to see the trail.
|
||||
</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="objectactions">
|
||||
<title>Keyboard Actions</title>
|
||||
<indexterm><primary>Objects in the Sky</primary>
|
||||
<secondary>Keyboard Actions</secondary></indexterm>
|
||||
<para>
|
||||
|
||||
When you click on an object in the map, it becomes the
|
||||
<firstterm>selected object</firstterm>, and its name is identified in
|
||||
the statusbar. There are a number of quick key commands available
|
||||
which act on the selected object:
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><keycap>C</keycap></term>
|
||||
<listitem>
|
||||
<para>Center and Track on the selected object</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><keycap>D</keycap></term>
|
||||
<listitem>
|
||||
<para>Show the <link linkend="tool-details">Details window</link>
|
||||
for the selected object</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><keycap>L</keycap></term>
|
||||
<listitem>
|
||||
<para>Toggle a visible name label on the selected object</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><keycap>O</keycap></term>
|
||||
<listitem>
|
||||
<para>Add the selected object to the
|
||||
<link linkend="tool-observinglist">Observing List</link></para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><keycap>T</keycap></term>
|
||||
<listitem>
|
||||
<para>Toggle a visible curve on the sky, showing the path of the
|
||||
object across the sky (only applicable to Solar System bodies)
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
</para>
|
||||
|
||||
<note>
|
||||
<para>
|
||||
By holding down the <keycap>Alt</keycap> key, you can perform
|
||||
these actions on the centered object, rather than the selected
|
||||
object.
|
||||
</para>
|
||||
</note>
|
||||
</sect2> <!--object actions-->
|
||||
</sect1> <!--objects in the sky-->
|
||||
|
||||
<sect1 id="endtour">
|
||||
<title>End of the Tour</title>
|
||||
<para>
|
||||
This concludes the tour of &kstars;, although we have only scratched
|
||||
the surface of the available features. &kstars; includes many useful
|
||||
<link linkend="tools">astronomy tools</link>, it can directly
|
||||
<link linkend="indi">control your telescope</link>, and it offers a
|
||||
wide variety of <link linkend="config">configuration and
|
||||
customization options</link>. In addition, this Handbook includes the
|
||||
<link linkend="astroinfo">AstroInfo Project</link>, a series of short,
|
||||
interlinked articles explaining some of the celestial and astrophysical
|
||||
concepts behind &kstars;.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,44 @@
|
||||
<sect1 id="ai-retrograde">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>John</firstname>
|
||||
<surname>Cirillo</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Retrograde Motion</title>
|
||||
<indexterm><primary>Retrograde Motion</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
<firstterm>Retrograde Motion</firstterm> is the orbital motion of a body in a
|
||||
direction opposite that which is normal to spatial bodies within a given system.
|
||||
</para><para>
|
||||
When we observe the sky, we expect most objects to appear to move in a
|
||||
particular direction with the passing of time. The apparent motion of
|
||||
most bodies in the sky is from east to west. However it is possible to
|
||||
observe a body moving west to east, such as an artificial satellite or
|
||||
space shuttle that is orbiting eastward. This orbit is
|
||||
considered Retrograde Motion.
|
||||
</para><para>
|
||||
Retrograde Motion is most often used in reference to the
|
||||
motion of the outer planets (Mars, Jupiter, Saturn, and so forth).
|
||||
Though these planets appear to move from east to west on a nightly
|
||||
basis in response to the spin of the Earth, they are actually drifting
|
||||
slowly eastward with respect to the stationary stars, which can be
|
||||
observed by noting the position of these planets for several nights in a
|
||||
row. This motion is normal for these planets, however, and not
|
||||
considered Retrograde Motion. However, since the Earth completes its
|
||||
orbit in a shorter period of time than these outer planets, we
|
||||
occasionally overtake an outer planet, like a faster car on a
|
||||
multiple-lane highway. When this occurs, the planet we are passing will
|
||||
first appear to stop its eastward drift, and it will then
|
||||
appear to drift back toward the west. This is Retrograde Motion, since
|
||||
it is in a direction opposite that which is typical for planets. Finally,
|
||||
as the Earth swings past the the planet in its orbit, they appear to
|
||||
resume their normal west-to-east drift on successive nights.
|
||||
</para><para>
|
||||
This Retrograde Motion of the planets puzzled ancient Greek
|
||||
astronomers, and was one reason why they named these bodies <quote>planets</quote>
|
||||
which in Greek means <quote>wanderers</quote>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 122 KiB |
@ -0,0 +1,300 @@
|
||||
<sect1 id="tool-scriptbuilder">
|
||||
<title>The Script Builder Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Script Builder</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
KDE applications can be controlled externally from another program,
|
||||
from a console prompt, or from a shell script using the Desktop
|
||||
COmmunication Protocol (<abbrev>DCOP</abbrev>). KStars takes
|
||||
advantage of this feature to allow rather complex behaviors to be
|
||||
scripted and played back at any time. This can be used, for example,
|
||||
to create a classroom demo to illustrate an astronomical concept.
|
||||
</para>
|
||||
<para>
|
||||
The problem with DCOP scripts is, writing them is a bit like
|
||||
programming, and can seem a daunting task to those who do not have
|
||||
programming experience. The Script Builder Tool provides a
|
||||
<abbrev>GUI</abbrev> point-and-click interface for constructing
|
||||
KStars DCOP scripts, making it very easy to create complex scripts.
|
||||
</para>
|
||||
|
||||
<sect2 id="sb-intro">
|
||||
<title>Introduction to the Script Builder</title>
|
||||
|
||||
<para>
|
||||
Before explaining how to use the Script Builder, I provide a very
|
||||
brief introduction to all of the <abbrev>GUI</abbrev> components;
|
||||
for more infomation, use the "What's This?" function.
|
||||
</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Script Builder Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="scriptbuilder.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Script Builder Tool</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The Script Builder is shown in the above screenshot. The box on the
|
||||
left is the <firstterm>Current Script box</firstterm>; it shows the
|
||||
list of commands that comprise the current working script. The box
|
||||
on the right is the <firstterm>Function Browser</firstterm>; it
|
||||
displays the list of all available script functions. Below the
|
||||
Function Browser, there is a small panel which will display short
|
||||
documentation about the script function highlighted in the Function
|
||||
Browser. The panel below the Current Script box is the
|
||||
<firstterm>Function Arguments panel</firstterm>; when a function is
|
||||
highlighted in the Current Script box, this panel will contain items
|
||||
for specifying values for any arguments that the highlighted function
|
||||
requires.
|
||||
</para><para>
|
||||
Along the top of the window, there is a row of buttons which operate
|
||||
on the script as a whole. From left to right, they are:
|
||||
<guibutton>New Script</guibutton>, <guibutton>Open Script</guibutton>,
|
||||
<guibutton>Save Script</guibutton>, <guibutton>Save Script
|
||||
As...</guibutton>, and <guibutton>Test Script</guibutton>. The
|
||||
function of these buttons should be obvious, except perhaps the last
|
||||
button. Pressing <guibutton>Test Script</guibutton> will attempt to
|
||||
run the current script in the main KStars window. You should move
|
||||
the Script Builder window out of the way before pressing this, so you
|
||||
can see the results.
|
||||
</para><para>
|
||||
In the center of the window, there is a column of buttons which operate
|
||||
on individual script functions. From top to bottom, they are:
|
||||
<guibutton>Add Function</guibutton>, <guibutton>Remove
|
||||
Function</guibutton>, <guibutton>Copy Function</guibutton>,
|
||||
<guibutton>Move Up</guibutton>, and <guibutton>Move Down</guibutton>.
|
||||
<guibutton>Add Function</guibutton> adds the currently-highlighted
|
||||
function in the Function Browser to the Current Script box (you can
|
||||
also add a function by double-clicking on it). The rest of the
|
||||
buttons operate on the function highlighted in the Current Script box,
|
||||
either removing it, duplicating it, or changing its position in the
|
||||
current script.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="sb-using">
|
||||
<title>Using the Script Builder</title>
|
||||
<para>
|
||||
In order to illustrate using the Script Builder, we present a small
|
||||
tutorial example where we make a script that tracks the Moon while
|
||||
the clock runs at an accelerated rate.
|
||||
</para><para>
|
||||
If we are going to track the Moon, we will need to point the display
|
||||
at it first. The <firstterm>lookToward</firstterm> function
|
||||
is used to do this. Highlight this function in the Function Browser,
|
||||
and note the documentation displayed in the panel below the Browser.
|
||||
Press the <guibutton>Add Function</guibutton> button to add this
|
||||
function to the Current Script box. The Function Arguments panel
|
||||
will now contain a combobox labeled <quote>dir</quote>, short for
|
||||
direction. This is the direction in which the display should
|
||||
be pointed. The combobox contains only the cardinal compass points,
|
||||
not the Moon or any other objects. You can either enter
|
||||
<quote>Moon</quote> in the box manually, or press the
|
||||
<guibutton>Object</guibutton> button to use the <guilabel>Find
|
||||
Object</guilabel> window to select the Moon from the list of named
|
||||
objects. Note that, as usual, centering on an object automatically
|
||||
engages object-tracking mode, so there is no need to add the
|
||||
<firstterm>setTracking</firstterm> function after lookToward.
|
||||
</para><para>
|
||||
Now that we have taken care of pointing at the Moon, we next want to
|
||||
make time pass at an accelerated rate. Use the
|
||||
<firstterm>setClockScale</firstterm> function for this. Add it to
|
||||
the script by double-clicking on it in the Function Browser. The
|
||||
Function Arguments panel contains a timestep spinbox for setting the
|
||||
desired time step for the simulation clock. Change the timestep to
|
||||
3 hours.
|
||||
</para><para>
|
||||
OK, we have pointed at the Moon and accelerated the clock. Now we just
|
||||
want the script to wait for several seconds while the display tracks
|
||||
on the Moon. Add the <firstterm>waitFor</firstterm> function to the
|
||||
script, and use the Function Arguments panel to specify that it should
|
||||
wait for 20 seconds before continuing.
|
||||
</para><para>
|
||||
To finish up, let us reset the clock's timestep to the normal value
|
||||
of 1 second. Add another instance of setClockScale, and set its value
|
||||
to 1 sec.
|
||||
</para><para>
|
||||
Actually, we are not quite done yet. We should probably make sure that
|
||||
the display is using Equatorial coordinates before the script tracks
|
||||
the Moon with an accelerated time step. Otherwise, if the display is
|
||||
using Horizontal coordinates, it will rotate very quickly through
|
||||
large angles as the Moon rises and sets. This can be very confusing,
|
||||
and is avoided by setting the View Option
|
||||
<firstterm>UseAltAz</firstterm> to <quote>false</quote>. To change
|
||||
any View Option, use the <firstterm>changeViewOption</firstterm>
|
||||
function. Add this function to the script, and examine the Function
|
||||
Arguments panel. There is a combobox which contains the list of all
|
||||
options which can be adjusted by changeViewOption. Since we know
|
||||
we want the UseAltAz option, we could simply select it from the
|
||||
combobox. However, the list is quite long, and there is no
|
||||
explanation of what each item is for. It therefore may be easier to
|
||||
press the <guibutton>Browse Tree</guibutton> button, which will open
|
||||
a window containing a tree view of the available options, organized by
|
||||
topic. In addition, each item has a short explanation of what the
|
||||
option does, and the data type of the option's value. We find
|
||||
UseAltAz under the <guilabel>Skymap options</guilabel> category.
|
||||
Just highlight this item and press <guibutton>OK</guibutton>, and it
|
||||
will be selected in the combobox of the Function Arguments panel.
|
||||
Finally, make its value <quote>false</quote> or <quote>0</quote>.
|
||||
</para><para>
|
||||
One more step: changing UseAltAz at the end of the script does us no
|
||||
good; we need this to be changed before anything else happens. So,
|
||||
make sure this function is highlighted in the Current Script box,
|
||||
and press the <guibutton>Move Up</guibutton> button until it is the
|
||||
first function.
|
||||
</para><para>
|
||||
Now that we have finished the script, we should save it to disk.
|
||||
Press the <guibutton>Save Script</guibutton> button. This will first
|
||||
open a window in which you can provide a name for the script, and fill
|
||||
in your name as the author. Enter <quote>Tracking the Moon</quote>
|
||||
for a name, and your name as the author, and press
|
||||
<guibutton>OK</guibutton>. Next, you will see the standard &kde; Save
|
||||
File dialog. Specify a filename for the script and press
|
||||
<guibutton>OK</guibutton> to save the script. Note that if your
|
||||
filename does not end with <quote>.kstars</quote>, this suffix
|
||||
will be automatically attached. If you are curious, you can examine the
|
||||
script file with any text editor.
|
||||
</para><para>
|
||||
Now that we have a completed script, we can run it in a couple of ways.
|
||||
From a console prompt, you can simply execute the script as long as an
|
||||
instance of KStars is currently running. Alternatively, you can execute
|
||||
the script from within KStars using the <guimenuitem>Run
|
||||
Script</guimenuitem> item in the <guimenu>File</guimenu> menu.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="sb-indi">
|
||||
<title>Device Automation with INDI</title>
|
||||
<para>
|
||||
Device scheduling and automation is supported for all <link linkend="what-is-indi">INDI</link>-compliant devices. You can coordinate any number of devices to perform complex operations using &kstars; <link linkend="sb-intro">Script Builder</link>. This can be accomplished by using &kstars; INDI DCOP interface, which provides different classes of functions to suit your tasks. The INDI DCOP functions can be decomposed into five different classes. The following is a review of the functions and their arguments as supported in KStars. It it highly recommended to read the <link linkend="indi-concepts">INDI Concepts</link> section as we will employ key INDI concepts throughout this tutorial.</para>
|
||||
<orderedlist>
|
||||
<listitem><para>Generic Device Functions: Functions to establish/shutdown devices..etc.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><function>startINDI (QString deviceName, bool useLocal)</function> : Establish an INDI service either as local or server.</para></listitem>
|
||||
<listitem><para><function>shutdownINDI (QString deviceName)</function> : Shutdown the INDI service.</para></listitem>
|
||||
<listitem><para><function>switchINDI(QString deviceName, bool turnOn)</function> : Connect or Disconnect an INDI device.</para></listitem>
|
||||
<listitem><para><function>setINDIPort(QString deviceName, QString port)</function> : Set the device's connection port.</para></listitem>
|
||||
<listitem><para><function>setINDIAction(QString deviceName, QString action)</function> : Activate an INDI action. The action can be any <emphasis>element</emphasis> of a <emphasis>switch property</emphasis></para></listitem>
|
||||
<listitem><para><function>waitForINDIAction(QString deviceName, QString action)</function> : Pause script execution until the specified action <emphasis>property</emphasis> returns with OK status.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Telescope Functions: Functions to control the telescope motion and status.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><function>setINDIScopeAction(QString deviceName, QString action)</function> : Set the telescope mode or action. Available options are SLEW, TRACK, SYNC, PARK, and ABORT.</para></listitem>
|
||||
<listitem><para><function>setINDITargetCoord(QString deviceName, double RA, double DEC)</function> : Set the telescope JNow target coordinates to <emphasis>RA</emphasis> and <emphasis>DEC</emphasis>.</para></listitem>
|
||||
<listitem><para><function>setINDITargetName(QString deviceName, QString objectName)</function> : Set the telescope JNow target coordinates to the coordinates of <emphasis>objectName</emphasis>. KStars will lookup the object name in its database and will fetch RA and Dec once found.</para></listitem>
|
||||
<listitem><para><function>setINDIGeoLocation(QString deviceName, double
|
||||
longitude, double latitude)</function> : Set the telescope geographical
|
||||
location to the longitude and latitude as specified. The longitude is measured
|
||||
from Greenwich, UK, to the East. However, while it is common to use negative
|
||||
longitudes for the Western hemisphere, INDI requires longitude values between
|
||||
0 and 360 degrees. So if you have a negative longitude, simply add 360
|
||||
degrees to get the value that INDI expects. For example, Calgary, Canada
|
||||
coordinates in &kstars; are longitude: -114 04 58; latitude: 51 02 58. So
|
||||
INDI's would need longitude = 360 - 114.083 = 245.917
|
||||
degrees.</para></listitem>
|
||||
<listitem><para><function>setINDIUTC(QString ddeviceName, QString UTCDateTime)</function> : Set the telescope UTC Date and Time in ISO 8601 format. The format is YYYY-MM-DDTHH:MM:SS (e.g. 2004-07-12T22:05:32).</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Camera/CCD Functions: Functions to control the camera/CCD properties and status.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><function>setINDICCDTemp(QString deviceName, int temp)</function> : Set the CCD chip target temperature in degrees celsius.</para></listitem>
|
||||
<listitem><para><function>setINDIFrameType(QString deviceName, QString type)</function> : Set the CCD frame type. Available options are FRAME_LIGHT, FRAME_BIAS, FRAME_DARK, and FRAME_FLAT.</para></listitem>
|
||||
<listitem><para><function>startINDIExposure(QString deviceName, int timeout)</function> : Start the CCD/Camera exposure for the duration specified by <emphasis>timeout</emphasis> in seconds.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Focuser Functions: Functions to control the focuser motion and status.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><function>setINDIFocusSpeed(QString deviceName, QString action)</function> : Set the focuser speed. Available options are FOCUS_HALT, FOCUS_SLOW, FOCUS_MEDIUM, and FOCUS_FAST.</para></listitem>
|
||||
<listitem><para><function>setINDIFocusTimeout(QString deviceName, int timeout)</function> : Set the duration in seconds for any subsequent startINDIFocus operations.</para></listitem>
|
||||
<listitem><para><function>startINDIFocus(QString deviceName, int focusDir)</function> : Move the focuser either inward (focusDir = 0) or outward (focusDir = 1). The speed and duration of this operation is set by the <function>setINDIFocusSpeed()</function> and <function>setINDIFocusTimeout()</function> functions.</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
<listitem><para>Filter Functions: Functions to control the filter position.</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><function>setINDIFilterNum(QString deviceName, int filter_num)</function> : Change the filter position to <varname>filter_num</varname>. The user can assign aliases to filter numbers in the <guimenuitem>Configure INDI</guimenuitem> dialog box under the <guimenu>Devices</guimenu> menu (e.g. Filter 1 = Red, Filter 2 = Green..etc).</para></listitem>
|
||||
</itemizedlist>
|
||||
</listitem>
|
||||
|
||||
</orderedlist>
|
||||
|
||||
<para>
|
||||
Note that the device name is the first argument of all INDI functions. This permits different commands that are sent to different INDI devices to be intermixed together in one script. The Script Builder tool provides two options to facilitate the creation and editing of INDI scripts:</para>
|
||||
<itemizedlist>
|
||||
<listitem><para><option>Append waitForINDIAction after any INDI action</option> : When checked, the Script Builder tool will automatically add <function>waitForINDIAction()</function> after any action it recognizes. For example, If you add <function>switchINDI()</function> function to the script and this option was checked, the Script Builder will add "waitForINDIAction CONNECTION" in the script file just after <function>switchINDI()</function>. This will cause the script to pause after it issues <function>switchINDI()</function> until <function>switchINDI()</function> returns with OK status (&ie; device connection was successful). It is critically important to know that the Script Builder cannot automatically add <function>waitForINDIAction()</function> for generic actions added using the <function>setINDIAction()</function> function. This is because KStars cannot determine the parent property of generic actions. Therefore, you must manually add <function>waitForINDIAction()</function> after generic actions when desired.</para>
|
||||
</listitem>
|
||||
<listitem><para><option>Reuse INDI device name</option> : When checked, the device name field of all subsequent functions is automatically filled with the last device name. The last device name is set every time <function>startINDI()</function> function is added to the current script. When working with multiple devices, it is recommended to have this option off.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Now we are ready to create a demo script that controls LX200 GPS telescope, in addition to Finger Lakes CCD camera. Our task is simple. We will ask the telescope to slew and track Mars, then we will ask the camera to take three shots 10 seconds each separated by 20 seconds.</para>
|
||||
<important><para>Since there is no direct feedback from the INDI DCOP interface about the progress, value, or status of the device operations and parameters (except for <function>waitForINDIAction()</function>), device automation in KStars is similar to an open-loop control system. In such a system, there is usually no direct feedback to measure the progress of the system and to correct for errors. Consequently, you must design your device automation scripts with careful consideration. All automation scripts must be subjected to rigorous testing before deployment.</para></important>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Script Builder Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="indiscript.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Script Builder Tool</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The demo script is shown in the above screenshot. Note that we checked <option>"Append waitForINDIAction after any INDI action"</option> and unchecked <option>"Reuse INDI device name"</option>. The first function to add is <function>startINDI()</function> as shown above. We want to run our devices as local, so we will not change the service mode provided in the function arguments window. We type in our device name, starting with the telescope "LX200 GPS". We repeat the same operation again for "FLI CCD". There is a <function>waitFor()</function> function after that. It is generally recommended to use <function>waitFor()</function> function immediately after <function>startINDI()</function> to pause the script for 1-5 seconds. This will ensure that all properties are built and are ready to receive command. It is also useful for controlling remote devices because retrieving and building properties might take some time. In the next function, <function>switchINDI()</function>, we connect to each device.</para>
|
||||
|
||||
<para>Since <option>"Append waitForINDIAction after any INDI action"</option> is checked, we do not need to add <function>waitForINDIAction()</function> after <function>switchINDI()</function> to insure that we only continue executing the script after we successfully connect. This is because the Script Builder tool will do this automatically for us when we save the script. Now let us set the telescope mode to tracking, click on the <function>setINDIScopeAction()</function> function and select TRACK. Note that we need to set the telescope to tracking <emphasis>before</emphasis> issuing the coordinates it needs to track. The <function>setINDIScopeAction()</function> function is provided for convenience; since in this example, it simply issues a generic <function>setINDIAction()</function> function followed by the keyword TRACK. However, the benefit of using <function>setINDIScopeAction()</function> is that KStars can automatically append <function>waitForINDIAction()</function> after it when required. This facility is not automatically available to generic actions as we discussed before.</para>
|
||||
|
||||
<para>Next we use the <function>setINDITargetName()</function> function and set it to Mars. Finally, the last few steps involve capturing an image for 10 seconds which can be done by using <function>startINDIExposure()</function> function, and waiting for 20 seconds in between which can be done by using <function>waitFor()</function> function with a value of 20.</para>
|
||||
|
||||
<para>We can now save our script and execute it at any time. The saved script will be similar to this:</para>
|
||||
<blockquote><programlisting>
|
||||
#!/bin/bash
|
||||
#KStars DCOP script: Demo Script
|
||||
#by Jasem Mutlaq
|
||||
#last modified: Thu Jan 6 2005 09:58:26
|
||||
#
|
||||
KSTARS=`dcopfind -a 'kstars*'`
|
||||
MAIN=KStarsInterface
|
||||
CLOCK=clock#1
|
||||
dcop $KSTARS $MAIN startINDI "LX200 GPS" true
|
||||
dcop $KSTARS $MAIN startINDI "FLI CCD" true
|
||||
dcop $KSTARS $MAIN waitFor 3
|
||||
dcop $KSTARS $MAIN switchINDI "LX200 GPS" true
|
||||
dcop $KSTARS $MAIN waitForINDIAction "LX200 GPS" CONNECTION
|
||||
dcop $KSTARS $MAIN switchINDI "FLI CCD" true
|
||||
dcop $KSTARS $MAIN waitForINDIAction "FLI CCD" CONNECTION
|
||||
dcop $KSTARS $MAIN setINDIScopeAction "LX200 GPS" TRACK
|
||||
dcop $KSTARS $MAIN waitForINDIAction "LX200 GPS" ON_COORD_SET
|
||||
dcop $KSTARS $MAIN setINDITargetName "LX200 GPS" Mars
|
||||
dcop $KSTARS $MAIN waitForINDIAction "LX200 GPS" EQUATORIAL_EOD_COORD
|
||||
dcop $KSTARS $MAIN startINDIExposure "FLI CCD" 10
|
||||
dcop $KSTARS $MAIN waitForINDIAction "FLI CCD" EXPOSE_DURATION
|
||||
dcop $KSTARS $MAIN waitFor 20
|
||||
dcop $KSTARS $MAIN startINDIExposure "FLI CCD" 10
|
||||
dcop $KSTARS $MAIN waitForINDIAction "FLI CCD" EXPOSE_DURATION
|
||||
dcop $KSTARS $MAIN waitFor 20
|
||||
dcop $KSTARS $MAIN startINDIExposure "FLI CCD" 10
|
||||
dcop $KSTARS $MAIN waitForINDIAction "FLI CCD" EXPOSE_DURATION
|
||||
</programlisting>
|
||||
</blockquote>
|
||||
|
||||
<note>
|
||||
<para>The INDI Library provides robust scripting tools that enable developers to orchestrate very complex scripts. For more details, refer to the <ulink url="http://indi.sourceforge.net/manual/book1.html">INDI Developer Manual</ulink>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
After Width: | Height: | Size: 92 KiB |
@ -0,0 +1,80 @@
|
||||
<sect1 id="ai-sidereal">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Sidereal Time</title>
|
||||
<indexterm><primary>Sidereal Time</primary>
|
||||
<seealso>Hour Angle</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
<firstterm>Sidereal Time</firstterm> literally means <quote>star time</quote>.
|
||||
The time we are used to using in our everyday lives is Solar Time. The
|
||||
fundamental unit of Solar Time is a <firstterm>Day</firstterm>: the time it
|
||||
takes the Sun to travel 360 degrees around the sky, due to the rotation of the
|
||||
Earth. Smaller units of Solar Time are just divisions of a Day:
|
||||
</para><para>
|
||||
<itemizedlist>
|
||||
<listitem><para>1/24 Day = 1 Hour</para></listitem>
|
||||
<listitem><para>1/60 Hour = 1 Minute</para></listitem>
|
||||
<listitem><para>1/60 Minute = 1 Second</para></listitem>
|
||||
</itemizedlist>
|
||||
</para><para>
|
||||
However, there is a problem with Solar Time. The Earth does not actually
|
||||
spin around 360 degrees in one Solar Day. The Earth is in orbit around the
|
||||
Sun, and over the course of one day, it moves about one Degree along its
|
||||
orbit (360 degrees/365.25 Days for a full orbit = about one Degree per
|
||||
Day). So, in 24 hours, the direction toward the Sun changes by about a
|
||||
Degree. Therefore, the Earth has to spin 361 degrees to make
|
||||
the Sun look like it has traveled 360 degrees around the Sky.
|
||||
</para><para>
|
||||
In astronomy, we are concerned with how long it takes the Earth to spin
|
||||
with respect to the <quote>fixed</quote> stars, not the Sun. So, we would like a
|
||||
timescale that removes the complication of Earth's orbit around the Sun,
|
||||
and just focuses on how long it takes the Earth to spin 360 degrees with
|
||||
respect to the stars. This rotational period is called a <firstterm>Sidereal
|
||||
Day</firstterm>. On average, it is 4 minutes shorter than a Solar Day, because
|
||||
of the extra 1 degree the Earth spins in a Solar Day.
|
||||
Rather than defining a Sidereal Day to be 23 hours, 56 minutes, we define
|
||||
Sidereal Hours, Minutes and Seconds that are the same fraction of a Day as
|
||||
their Solar counterparts. Therefore, one Solar Second = 1.00278 Sidereal
|
||||
Seconds.
|
||||
</para><para>
|
||||
The Sidereal Time is useful for determining where the stars are at any
|
||||
given time. Sidereal Time divides one full spin of the Earth into 24
|
||||
Sidereal Hours; similarly, the map of the sky is divided into 24 Hours
|
||||
of <firstterm>Right Ascension</firstterm>. This is no
|
||||
coincidence; Local Sidereal Time (<acronym>LST</acronym>) indicates the Right
|
||||
Ascension on the sky that is currently crossing the <link
|
||||
linkend="ai-meridian">Local Meridian</link>. So, if a star has a Right
|
||||
Ascension of 05h 32m 24s, it will be on your meridian at LST=05:32:24. More
|
||||
generally, the difference between an object's <acronym>RA</acronym> and the Local
|
||||
Sidereal Time tells you how far from the Meridian the object is. For example,
|
||||
the same object at LST=06:32:24 (one Sidereal Hour later), will be one Hour of
|
||||
Right Ascension west of your meridian, which is 15 degrees. This angular
|
||||
distance from the meridian is called the object's <link
|
||||
linkend="ai-hourangle">Hour Angle</link>.
|
||||
</para>
|
||||
<tip>
|
||||
<para>
|
||||
The Local Sidereal Time is displayed by &kstars; in the <guilabel>Time Info
|
||||
Box</guilabel>, with the label <quote>ST</quote> (you have to
|
||||
<quote>unshade</quote> the box by double-clicking it in order to see the
|
||||
sidereal time). Note that the changing sidereal seconds are not synchronized
|
||||
with the changing Local Time and Universal Time seconds. In fact, if you watch
|
||||
the clocks for a while, you will notice that the Sidereal seconds really are
|
||||
slightly shorter than the LT and UT seconds.
|
||||
</para><para>
|
||||
Point to the <link linkend="ai-zenith">Zenith</link> (press <keycap>Z</keycap>
|
||||
or select <guimenuitem>Zenith</guimenuitem> from the
|
||||
<guimenu>Pointing</guimenu>
|
||||
menu). The Zenith is the point on the sky where you are looking <quote>straight
|
||||
up</quote> from the ground, and it is a point on your <link
|
||||
linkend="ai-meridian">Local Meridian</link>. Note the Right Ascension of the
|
||||
Zenith: it is exactly the same as your Local Sidereal Time.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
|
||||
@ -0,0 +1,152 @@
|
||||
<sect1 id="ai-skycoords">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Celestial Coordinate Systems</title>
|
||||
<para>
|
||||
<indexterm><primary>Celestial Coordinate Systems</primary>
|
||||
<secondary>Overview</secondary></indexterm>
|
||||
A basic requirement for studying the heavens is determining where in the
|
||||
sky things are. To specify sky positions, astronomers have developed
|
||||
several <firstterm>coordinate systems</firstterm>. Each uses a coordinate grid
|
||||
projected on the <link linkend="ai-csphere">Celestial Sphere</link>, in
|
||||
analogy to the <link linkend="ai-geocoords">Geographic coordinate
|
||||
system</link> used on the surface of the Earth. The coordinate systems
|
||||
differ only in their choice of the <firstterm>fundamental plane</firstterm>,
|
||||
which divides the sky into two equal hemispheres along a <link
|
||||
linkend="ai-greatcircle">great circle</link>. (the fundamental plane of the
|
||||
geographic system is the Earth's equator). Each coordinate system is named for
|
||||
its choice of fundamental plane.
|
||||
</para>
|
||||
|
||||
<sect2 id="equatorial">
|
||||
<title>The Equatorial Coordinate System</title>
|
||||
<indexterm><primary>Celestial Coordinate Systems</primary>
|
||||
<secondary>Equatorial Coordinates</secondary>
|
||||
<seealso>Celestial Equator</seealso>
|
||||
<seealso>Celestial Poles</seealso>
|
||||
<seealso>Geographic Coordinate System</seealso>
|
||||
</indexterm>
|
||||
<indexterm><primary>Right Ascension</primary><see>Equatorial Coordinates</see></indexterm>
|
||||
<indexterm><primary>Declination</primary><see>Equatorial Coordinates</see></indexterm>
|
||||
|
||||
<para>
|
||||
The <firstterm>Equatorial coordinate system</firstterm> is probably the most
|
||||
widely used celestial coordinate system. It is also the most closely related
|
||||
to the <link linkend="ai-geocoords">Geographic coordinate system</link>, because
|
||||
they use the same fundamental plane, and the same poles. The projection of the
|
||||
Earth's equator onto the celestial sphere is called the
|
||||
<link linkend="ai-cequator">Celestial Equator</link>.
|
||||
Similarly, projecting the geographic Poles onto the celestial sphere defines the
|
||||
North and South <link linkend="ai-cpoles">Celestial Poles</link>.
|
||||
</para><para>
|
||||
However, there is an important difference between the equatorial and
|
||||
geographic coordinate systems: the geographic system is fixed to the
|
||||
Earth; it rotates as the Earth does. The Equatorial system is
|
||||
fixed to the stars<footnote id="fn-precess"><para>actually, the equatorial
|
||||
coordinates are not quite fixed to the stars. See <link
|
||||
linkend="ai-precession">precession</link>. Also, if <link
|
||||
linkend="ai-hourangle">Hour Angle</link> is used in place of Right
|
||||
Ascension, then the Equatorial system is fixed to the Earth, not to the
|
||||
stars.</para></footnote>, so it appears to rotate across the sky with the stars,
|
||||
but of course it is really the Earth rotating under the fixed sky.
|
||||
</para><para>
|
||||
The <firstterm>latitudinal</firstterm> (latitude-like) angle of the Equatorial
|
||||
system is called <firstterm>Declination</firstterm> (Dec for short). It
|
||||
measures the angle of an object above or below the Celestial Equator. The
|
||||
<firstterm>longitudinal</firstterm> angle is called the <firstterm>Right
|
||||
Ascension</firstterm> (<acronym>RA</acronym> for short). It measures the angle of an object East
|
||||
of the <link linkend="ai-equinox">Vernal Equinox</link>. Unlike longitude,
|
||||
Right Ascension is usually measured in hours instead of degrees, because the
|
||||
apparent rotation of the Equatorial coordinate system is closely related to
|
||||
<link linkend="ai-sidereal">Sidereal Time</link> and <link
|
||||
linkend="ai-hourangle">Hour Angle</link>. Since a full rotation of the sky
|
||||
takes 24 hours to complete, there are (360 degrees / 24 hours) = 15 degrees in
|
||||
one Hour of Right Ascension.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="horizontal">
|
||||
<title>The Horizontal Coordinate System</title>
|
||||
|
||||
<indexterm><primary>Celestial Coordinate Systems</primary>
|
||||
<secondary>Horizontal Coordinates</secondary>
|
||||
<seealso>Horizon</seealso>
|
||||
<seealso>Zenith</seealso>
|
||||
</indexterm>
|
||||
<indexterm><primary>Azimuth</primary><see>Horizontal Coordinates</see></indexterm>
|
||||
<indexterm><primary>Altitude</primary><see>Horizontal Coordinates</see></indexterm>
|
||||
<para>
|
||||
The Horizontal coordinate system uses the observer's local <link
|
||||
linkend="ai-horizon">horizon</link> as the Fundamental Plane. This conveniently
|
||||
divides the sky into the upper hemisphere that you can see, and the lower
|
||||
hemisphere that you can't (because the Earth is in the way). The pole of the
|
||||
upper hemisphere is called the <link linkend="ai-zenith">Zenith</link>. The
|
||||
pole of the lower hemisphere is called the <firstterm>nadir</firstterm>. The
|
||||
angle of an object above or below the horizon is called the
|
||||
<firstterm>Altitude</firstterm> (Alt for short). The angle of an object around
|
||||
the horizon (measured from the North point, toward the East) is called the
|
||||
<firstterm>Azimuth</firstterm>. The Horizontal Coordinate System is sometimes
|
||||
also called the Alt/Az Coordinate System.
|
||||
</para><para>
|
||||
The Horizontal Coordinate System is fixed to the Earth, not the Stars.
|
||||
Therefore, the Altitude and Azimuth of an object changes with time, as the
|
||||
object appears to drift across the sky. In addition, because the Horizontal
|
||||
system is defined by your local horizon, the same object viewed from different
|
||||
locations on Earth at the same time will have different values of Altitude and
|
||||
Azimuth.
|
||||
</para><para>
|
||||
Horizontal coordinates are very useful for determining the Rise and Set times of
|
||||
an object in the sky. When an object has Altitude=0 degrees, it is either
|
||||
Rising (if its Azimuth is < 180 degrees) or Setting (if its Azimuth is >
|
||||
180 degrees).
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="ecliptic">
|
||||
<title>The Ecliptic Coordinate System</title>
|
||||
|
||||
<indexterm><primary>Celestial Coordinate Systems</primary>
|
||||
<secondary>Ecliptic Coordinates</secondary>
|
||||
<seealso>Ecliptic</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The Ecliptic coordinate system uses the <link
|
||||
linkend="ai-ecliptic">Ecliptic</link> for its Fundamental Plane. The
|
||||
Ecliptic is the path that the Sun appears to follow across the sky over
|
||||
the course of a year. It is also the projection of the Earth's
|
||||
orbital plane onto the Celestial Sphere. The latitudinal angle is
|
||||
called the <firstterm>Ecliptic Latitude</firstterm>, and the longitudinal angle
|
||||
is called the <firstterm>Ecliptic Longitude</firstterm>. Like Right Ascension
|
||||
in the Equatorial system, the zeropoint of the Ecliptic Longitude is the <link
|
||||
linkend="ai-equinox">Vernal Equinox</link>.
|
||||
</para><para>
|
||||
What do you think such a coordinate system would be useful for? If you
|
||||
guessed charting solar system objects, you are right! Each of the
|
||||
planets (except Pluto) orbits the Sun in roughly the same plane, so they always
|
||||
appear to be somewhere near the Ecliptic (&ie;, they always have small ecliptic
|
||||
latitudes).
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="galactic">
|
||||
<title>The Galactic Coordinate System</title>
|
||||
|
||||
<indexterm><primary>Celestial Coordinate Systems</primary>
|
||||
<secondary>Galactic Coordinates</secondary>
|
||||
</indexterm>
|
||||
<para>
|
||||
<indexterm><primary>Milky Way</primary></indexterm>
|
||||
The Galactic coordinate system uses the <firstterm>Milky Way</firstterm> as its
|
||||
Fundamental Plane. The latitudinal angle is called the <firstterm>Galactic
|
||||
Latitude</firstterm>, and the longitudinal angle is called the
|
||||
<firstterm>Galactic Longitude</firstterm>. This coordinate system is useful for
|
||||
studying the Galaxy itself. For example, you might want to know how the density
|
||||
of stars changes as a function of Galactic Latitude, to how much the disk of the
|
||||
Milky Way is flattened.
|
||||
</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 24 KiB |
@ -0,0 +1,53 @@
|
||||
<sect1 id="tool-solarsys">
|
||||
<title>Solar System Viewer</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>Solar System Viewer</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The Solar System Viewer
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="solarsystem.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Solar System Viewer</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
This tool displays a model of our solar system as seen from
|
||||
above. The Sun is drawn as a yellow dot in the center of the
|
||||
plot, and the orbits of the planets are drawn as ellipses with
|
||||
the correct shapes and orientations. The current position
|
||||
of each planet along its orbit is drawn as a colored dot, along
|
||||
with a name label. The display can be zoomed in and out with
|
||||
the <keycap>+</keycap> and <keycap>-</keycap> keys, and the
|
||||
display can be recentered with the arrow keys, or by
|
||||
double-clicking anywhere in the window with the mouse. You can
|
||||
also center on a planet with the <keycap>0–9</keycap> keys
|
||||
(<keycap>0</keycap> is the Sun; <keycap>9</keycap> is Pluto).
|
||||
If you center on a planet, it will be tracked as time passes in
|
||||
the tool.
|
||||
</para>
|
||||
<para>
|
||||
The Solar System Viewer has its own clock, independent of the
|
||||
clock in the main &kstars; window. There is a timestep control
|
||||
widget here, similar to the one in the main window's toolbar.
|
||||
However, this control defaults to a timestep of 1 day (so that
|
||||
the motions of the planets can be seen), and it starts out with
|
||||
the clock paused when the tool is opened.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
The current model used for Pluto's orbit is only good for dates
|
||||
within about 100 years of the present date. If you let the Solar
|
||||
System clock advance beyond this range, you will see Pluto behave
|
||||
very strangely! We are aware of this issue, and will try to
|
||||
improve Pluto's orbit model soon.
|
||||
</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 34 KiB |
@ -0,0 +1,91 @@
|
||||
<sect1 id="ai-spiralgal">
|
||||
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Mike</firstname>
|
||||
<surname>Choatie</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
|
||||
<title>Spiral Galaxies</title>
|
||||
<indexterm><primary>Spiral Galaxies</primary>
|
||||
</indexterm>
|
||||
|
||||
<para>
|
||||
Spiral galaxies are huge collections of billions of stars, most of
|
||||
which are flattened into a disk shape, with a bright, spherical bulge
|
||||
of stars at its center. Within the disk, there are
|
||||
typically bright arms where the youngest, brightest stars are
|
||||
found. These arms wind out from the center in a spiral pattern, giving
|
||||
the galaxies their name. Spiral galaxies look a bit like hurricanes,
|
||||
or like water flowing down a drain. They are some of the most beautiful
|
||||
objects in the sky.
|
||||
</para>
|
||||
<para>
|
||||
Galaxies are classified using a <quote>tuning fork diagram</quote>.
|
||||
The end of the fork classifies <link linkend="ai-ellipgal">elliptical
|
||||
galaxies</link> on a scale from the roundest, which is an E0, to
|
||||
those that appear most flattened, which is rated as E7. The
|
||||
<quote>tines</quote> of the tuning fork are where the two types of
|
||||
spiral galaxies are classified: normal spirals, and
|
||||
<quote>barred</quote> spirals. A barred spiral is one whose nuclear
|
||||
bulge is stretched out into a line, so it literally looks like it has
|
||||
a <quote>bar</quote> of stars in its center.
|
||||
</para><para>
|
||||
Both types of spiral galaxies are sub-classified according to the
|
||||
prominence of their central <quote>bulge</quote> of stars, their overall
|
||||
surface brightness, and how tightly their spiral arms are wound. These
|
||||
characteristics are related, so that an Sa galaxy has a large central bulge,
|
||||
a high surface brightness, and tightly-wound spiral arms. An Sb galaxy
|
||||
has a smaller bulge, a dimmer disk, and looser arms than an Sa, and so on
|
||||
through Sc and Sd. Barred galaxies use the same classification scheme,
|
||||
indicated by types SBa, SBb, SBc, and SBd.
|
||||
</para><para>
|
||||
There is another class of galaxy called S0, which is morphologically a
|
||||
transitional type between true spirals and ellipticals. Its spiral arms are
|
||||
so tightly wound as to be indistinguishable; S0 galaxies have disks with a
|
||||
uniform brightness. They also have an extremely dominant bulge.
|
||||
</para><para>
|
||||
The Milky Way galaxy, which is home to earth and all of the stars in our
|
||||
sky, is a Spiral Galaxy, and is believed to be a barred spiral. The name
|
||||
<quote>Milky Way</quote> refers to a band of very faint stars in the sky.
|
||||
This band is the result of looking in the plane of our galaxy's disk from
|
||||
our perspective inside it.
|
||||
</para><para>
|
||||
Spiral galaxies are very dynamic entities. They are hotbeds of star
|
||||
formation, and contain many young stars in their disks. Their central
|
||||
bulges tend to be made of older stars, and their diffuse halos are
|
||||
made of the very oldest stars in the Universe. Star formation is active
|
||||
in the disks because that is where the gas and dust are most concentrated;
|
||||
gas and dust are the building blocks of star formation.
|
||||
</para><para>
|
||||
Modern telescopes have revealed that many Spiral galaxies harbor
|
||||
supermassive black holes at their centers, with masses that can exceed
|
||||
that of a billion Suns. Both elliptical and spiral galaxies are known
|
||||
to contain these exotic objects; in fact many astronomers now believe
|
||||
that <emphasis>all</emphasis> large galaxies contain a supermassive
|
||||
black hole in their nucleus. Our own Milky Way is known to harbor
|
||||
a black hole in its core with a mass millions of times bigger than a
|
||||
star's mass.
|
||||
</para>
|
||||
|
||||
<tip>
|
||||
<para>
|
||||
There are many fine examples of spiral galaxies to be found in
|
||||
&kstars;, and many have beautiful images available in their
|
||||
<link linkend="popup-menu">popup menu</link>. You can find them
|
||||
by using the <link linkend="findobjects">Find Object</link> window.
|
||||
Here is a list of some spiral galaxies with nice images available:
|
||||
<itemizedlist>
|
||||
<listitem><para>M 64, the Black-Eye Galaxy (type Sa)</para></listitem>
|
||||
<listitem><para>M 31, the Andromeda Galaxy (type Sb)</para></listitem>
|
||||
<listitem><para>M 81, Bode's Galaxy (type Sb)</para></listitem>
|
||||
<listitem><para>M 51, the Whirlpool Galaxy (type Sc)</para></listitem>
|
||||
<listitem><para>NGC 300 (type Sd) [use DSS image link]</para></listitem>
|
||||
<listitem><para>M 83 (type SBa)</para></listitem>
|
||||
<listitem><para>NGC 1530 (type SBb)</para></listitem>
|
||||
<listitem><para>NGC 1073 (type SBc)</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 117 KiB |
@ -0,0 +1,134 @@
|
||||
<sect1 id="ai-stars">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname> <surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Stars: An Introductory <acronym>FAQ</acronym></title>
|
||||
<indexterm><primary>Stars</primary></indexterm>
|
||||
|
||||
<qandaset id="stars-faq">
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What are the stars?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
<firstterm>Stars</firstterm> are gigantic, self-gravitating spheres
|
||||
of (mostly) Hydrogen gas. Stars are also thermonuclear engines;
|
||||
nuclear fusion takes place deep in the cores of stars, where the
|
||||
density is extreme and the temperature reaches tens of millions
|
||||
of degrees Celsius.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Is the Sun a star?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Yes, the Sun is a star. It is the dominant centerpiece of our
|
||||
solar system. Compared to other stars, our Sun is rather ordinary;
|
||||
it appears to be so much bigger and brighter to us
|
||||
because it is millions of times closer than any other star.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Why do stars shine?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The short answer is: star shine because they are very hot. It is
|
||||
really no more complicated than that. Any object heated to
|
||||
thousands of degrees will radiate light, just like stars do.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>The obvious next question is: why are stars so hot?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
This is a tougher question. The usual answer is that stars get
|
||||
their heat from the thermonuclear fusion reactions in their cores.
|
||||
However, this cannot be the ultimate cause for the stars' heat,
|
||||
because a star must be hot in the first place for nuclear fusion to be
|
||||
triggered. Fusion can only sustain the hot temperature; it cannot
|
||||
make a star hot. A more correct answer is that stars are hot because
|
||||
they have collapsed. Stars form from diffuse gaseous nebulae; as the
|
||||
nebulous gas condenses to form a star, the gravitational potential
|
||||
energy of the material is released, first as kinetic energy, and
|
||||
ultimately as heat as the density increases.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>Are stars all the same?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
Stars have many things in common: they are all collapsed spheres of
|
||||
hot, dense gas (mostly Hydrogen), and nuclear fusion reactions are
|
||||
occurring at or near the centers of every star in the sky.
|
||||
</para><para>
|
||||
However, stars also show a great diversity in some properties.
|
||||
The brightest stars shine almost 100 million times as brightly as the
|
||||
faintest stars. Stars range in surface temperature from only a few
|
||||
thousand degrees to almost 50,000 degrees Celsius. These differences
|
||||
are largely due to differences in mass: massive stars are both hotter
|
||||
and brighter than lower-mass stars. The temperature and Luminosity
|
||||
also
|
||||
depend on the <emphasis>evolutionary state</emphasis>
|
||||
of the star.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>What is the Main Sequence?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para><indexterm><primary>Main sequence</primary></indexterm>
|
||||
The main sequence is the evolutionary state of a star when it is
|
||||
fusing Hydrogen in its core. This is the first (and longest) stage
|
||||
of a star's life (not including protostar phases). What happens to a
|
||||
star after it runs out of core Hydrogen is addressed in the stellar
|
||||
evolution article (coming soon).
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>How long do stars last?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>
|
||||
The lifetime of a star depends very much on its mass. More massive
|
||||
stars are hotter and shine much more brightly, causing them to
|
||||
consume their nuclear fuel much more rapidly. The largest
|
||||
stars (roughly 100 times as massive as the Sun), will run out of
|
||||
fuel in only a few million years; while the smallest stars (roughly
|
||||
ten percent the mass of the Sun), with their much more frugal
|
||||
consumption rate, will shine on (albeit dimly) for
|
||||
<emphasis>trillions</emphasis> of years. Note that this is much
|
||||
longer than the Universe has yet been in existence.
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
</qandaset>
|
||||
</sect1>
|
||||
|
||||
|
||||
@ -0,0 +1,44 @@
|
||||
<sect1 id="ai-timezones">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Time Zones</title>
|
||||
<indexterm><primary>Time Zones</primary>
|
||||
</indexterm>
|
||||
<para>
|
||||
The Earth is round, and it is always half-illuminated by the Sun. However,
|
||||
because the Earth is spinning, the half that is illuminated is always changing.
|
||||
We experience this as the passing of days wherever we are on the Earth's
|
||||
surface. At any given instant, there are places on the Earth passing from the
|
||||
dark half into the illuminated half (which is seen as <emphasis>dawn</emphasis>
|
||||
on the surface). At the same instant, on the opposite side of the Earth, points
|
||||
are passing from the illuminated half into darkness (which is seen as
|
||||
<emphasis>dusk</emphasis> at those locations). So, at any given time, different
|
||||
places on Earth are experiencing different parts of the day. Thus, Solar time
|
||||
is defined locally, so that the clock time at any location describes the part of
|
||||
the day consistently.
|
||||
</para><para>
|
||||
This localization of time is accomplished by dividing the globe into 24 vertical
|
||||
slices called <firstterm>Time Zones</firstterm>. The Local Time is the same
|
||||
within any given zone, but the time in each zone is one Hour
|
||||
<emphasis>earlier</emphasis> than the time in the neighboring Zone to the East.
|
||||
Actually, this is a idealized simplification; real Time Zone boundaries are not
|
||||
straight vertical lines, because they often follow national boundaries and other
|
||||
political considerations.
|
||||
</para><para>
|
||||
Note that because the Local Time always increases by an hour when moving between
|
||||
Zones to the East, by the time you move through all 24 Time Zones, you are a
|
||||
full day ahead of where you started. We deal with this paradox by defining the
|
||||
<firstterm>International Date Line</firstterm>, which is a Time Zone boundary in
|
||||
the Pacific Ocean, between Asia and North America. Points just to the East of
|
||||
this line are 24 hours behind the points just to the West of the line. This
|
||||
leads to some interesting phenomena. A direct flight from Australia to
|
||||
California arrives before it departs. Also, the islands of Fiji straddle the
|
||||
International Date Line, so if you have a bad day on the West side of Fiji, you
|
||||
can go over to the East side of Fiji and have a chance to live the same day all
|
||||
over again.
|
||||
</para>
|
||||
</sect1>
|
||||
@ -0,0 +1,33 @@
|
||||
<chapter id="tools">
|
||||
<title>KStars Tools</title>
|
||||
<para>
|
||||
<indexterm><primary>Tools</primary></indexterm>
|
||||
&kstars; comes with a number of tools that allow you to explore
|
||||
some more advanced aspects of astronomy and the night sky.
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem><para><link linkend="tool-details">Object Details</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-calculator">Astrocalculator</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-aavso">AAVSO Lightcurves</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-altvstime">Altitude vs. Time Plotter</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-whatsup">What's Up Tonight?</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-scriptbuilder">Script Builder</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-solarsys">Solar System Viewer</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-jmoons">Jupiter Moons Tool</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-observinglist">Observing List Tool</link></para></listitem>
|
||||
<listitem><para><link linkend="tool-fitsviewer">FITS Viewer</link></para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
&tool-details;
|
||||
&tool-calculator;
|
||||
&tool-aavso;
|
||||
&tool-altvstime;
|
||||
&tool-whatsup;
|
||||
&tool-scriptbuilder;
|
||||
&tool-solarsys;
|
||||
&tool-jmoons;
|
||||
&tool-observinglist;
|
||||
&tool-fitsviewer;
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,49 @@
|
||||
<sect1 id="ai-utime">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>Universal Time</title>
|
||||
<indexterm><primary>Universal Time</primary>
|
||||
<seealso>Time Zones</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The time on our clocks is essentially a measurement of the current position of
|
||||
the Sun in the sky, which is different for places at different Longitudes
|
||||
because the Earth is round (see <link linkend="ai-timezones">Time Zones</link>).
|
||||
</para><para>
|
||||
However, it is sometimes necessary to define a global time, one that is the same
|
||||
for all places on Earth. One way to do this is to pick a place on the Earth,
|
||||
and adopt the Local Time at that place as the <firstterm>Universal
|
||||
Time</firstterm>, abbreviated <abbrev>UT</abbrev>. (The name is a bit of a
|
||||
misnomer, since Universal Time has little to do with the Universe. It would
|
||||
perhaps be better to think of it as <emphasis>global time</emphasis>).
|
||||
</para><para>
|
||||
The geographic location chosen to represent Universal Time is Greenwich,
|
||||
England. The choice is arbitrary and historical. Universal Time became an
|
||||
important concept when European ships began to sail the wide open seas, far from
|
||||
any known landmarks. A navigator could reckon the ship's longitude by comparing
|
||||
the Local Time (as measured from the Sun's position) to the time back at the
|
||||
home port (as kept by an accurate clock on board the ship). Greenwich was home
|
||||
to England's Royal Observatory, which was charged with keeping time
|
||||
very accurately, so that ships in port could re-calibrate their clocks before
|
||||
setting sail.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
Set the geographic location to <quote>Greenwich, England</quote> using the
|
||||
<guilabel>Set Location</guilabel> window
|
||||
(<keycombo action="simul">&Ctrl;<keycap>G</keycap></keycombo>). Note that the
|
||||
Local Time (<abbrev>LT</abbrev>)and the Universal Time (<abbrev>UT</abbrev>) are
|
||||
now the same.
|
||||
</para><para>
|
||||
Further Reading: The history behind the construction of the first clock
|
||||
that was accurate and stable enough to be used on ships to keep Universal Time
|
||||
is a fascinating tale, and one told expertly in the book
|
||||
<quote>Longitude</quote>, by Dava Sobel.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
|
After Width: | Height: | Size: 64 KiB |
@ -0,0 +1,58 @@
|
||||
<sect1 id="tool-whatsup">
|
||||
<title>What's Up Tonight? Tool</title>
|
||||
<indexterm><primary>Tools</primary>
|
||||
<secondary>What's Up Tonight? Tool</secondary>
|
||||
</indexterm>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>
|
||||
The What's Up Tonight Tool
|
||||
</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="wut.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>What's Up Tonight?</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
The <quote>What's Up Tonight?</quote> (WUT) tool displays a list of
|
||||
objects that will be visible at night from any location, on any date.
|
||||
By default, the Date and Location are taken from the current settings
|
||||
in the main window, but you can change either value using the
|
||||
<guibutton>Change Date</guibutton> and <guibutton>Change
|
||||
Location</guibutton> buttons at the top of the WUT window.
|
||||
</para>
|
||||
<para>
|
||||
The WUT tool also displays a short almanac of data for the selected
|
||||
date: the rise and set times for the Sun and moon, the duration of
|
||||
the night, and the Moon's illumination fraction.
|
||||
</para>
|
||||
<para>
|
||||
Below the almanac is where the object information is displayed. The
|
||||
objects are organized into type categories. Select an object type
|
||||
in the box labeled <guilabel>Choose a Category</guilabel>, and all
|
||||
objects of that type which are above the horizon on the selected
|
||||
night will be displayed in the box labeled <guilabel>Matching
|
||||
Objects</guilabel>. For example, in the screenshot, the
|
||||
<guilabel>Planets</guilabel> category has been selected, and four
|
||||
planets which are up on the selected night are displayed (Mars,
|
||||
Neptune, Pluto, and Uranus). When an object in the list is selected,
|
||||
its rise, set and transit times are displayed in the lower-right
|
||||
panel. In addition, you can press the <guibutton>Object
|
||||
Details...</guibutton> button to open the <link
|
||||
linkend="tool-details">Object Details window</link> for that
|
||||
object.
|
||||
</para>
|
||||
<para>
|
||||
By default, the WUT will display objects which are above the horizon
|
||||
between sunset and midnight (i.e., <quote>in the evening</quote>).
|
||||
You can choose to show objects which are up between midnight and dawn
|
||||
(<quote>in the morning</quote>), or between dusk and dawn (<quote>any
|
||||
time tonight</quote>) using the combobox near the top of the window.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
|
After Width: | Height: | Size: 51 KiB |
@ -0,0 +1,31 @@
|
||||
<sect1 id="ai-zenith">
|
||||
<sect1info>
|
||||
<author>
|
||||
<firstname>Jason</firstname>
|
||||
<surname>Harris</surname>
|
||||
</author>
|
||||
</sect1info>
|
||||
<title>The Zenith</title>
|
||||
<indexterm><primary>Zenith</primary>
|
||||
<seealso>Horizontal Coordinates</seealso>
|
||||
</indexterm>
|
||||
<para>
|
||||
The Zenith is the point in the sky where you are looking when you look
|
||||
<quote>straight up</quote> from the ground. More precisely, it is the point on
|
||||
the sky with an <firstterm>Altitude</firstterm> of +90 Degrees; it is the Pole
|
||||
of the <link linkend="horizontal">Horizontal Coordinate
|
||||
System</link>. Geometrically, it is the point on the <link
|
||||
linkend="ai-csphere">Celestial Sphere</link> intersected by a line drawn from
|
||||
the center of the Earth through your location on the Earth's surface.
|
||||
</para><para>
|
||||
The Zenith is, by definition, a point along the <link
|
||||
linkend="ai-meridian">Local Meridian</link>.
|
||||
</para>
|
||||
<tip>
|
||||
<para>Exercise:</para>
|
||||
<para>
|
||||
You can point to the Zenith by pressing <keycap>Z</keycap> or by selecting
|
||||
<guimenuitem>Zenith</guimenuitem> from the <guimenu>Pointing</guimenu> menu.
|
||||
</para>
|
||||
</tip>
|
||||
</sect1>
|
||||
@ -0,0 +1,5 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 37 KiB |
@ -0,0 +1,910 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY ktouch "<application>KTouch</application>">
|
||||
<!ENTITY kappname "&ktouch;"><!-- replace kapp here -->
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &ktouch; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Håvard</firstname><surname>Frøiland</surname>
|
||||
<affiliation>
|
||||
<address><email>&Haavard.Froeiland.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
|
||||
<author>
|
||||
<firstname>Andreas</firstname><surname>Nicolai</surname>
|
||||
<affiliation>
|
||||
<address><email>Andreas.nicolai@gmx.net</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>1999-2005</year>
|
||||
<holder>Håvard Frøiland, Andreas Nicolai</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-06-19</date>
|
||||
<releaseinfo>1.5</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>&ktouch; is a program for learning to touch type. &ktouch;
|
||||
provides you with text to train on and adjusts to different levels
|
||||
depending on how good you are. It displays which key to press next
|
||||
and the correct finger to use.</para>
|
||||
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>touchwriting</keyword>
|
||||
<keyword>touchtyping</keyword>
|
||||
<keyword>typing</keyword>
|
||||
<keyword>typewriting</keyword>
|
||||
<keyword>education</keyword>
|
||||
<keyword>ktouch</keyword>
|
||||
<keyword>touch</keyword>
|
||||
<keyword>type</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="using_ktouch">
|
||||
<title>Using &ktouch;</title>
|
||||
|
||||
<sect1 id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<sect2>
|
||||
<title>What is &ktouch;?</title>
|
||||
<para>&ktouch; is a program for learning to touch type.</para>
|
||||
<para>&ktouch; provides you with text to train on and adjusts to
|
||||
different levels depending on how good you are. It shows your keyboard
|
||||
and indicates which key to press next and the correct finger to use.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>The main screen of &ktouch;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="main_screen_default_color.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>The main screen of &ktouch;</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>&ktouch; is an excellent touch typing tutor. You learn typing
|
||||
with all fingers, step by step, without having to look down
|
||||
at the keyboard all the time to find your keys (which slows you down a lot).
|
||||
It is convenient for all ages
|
||||
and the perfect typing tutor for schools, universities and individuals.
|
||||
It is free and licensed under the &GNU; Public License, so you will
|
||||
never have to pay anything for the program or any update.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Features </title>
|
||||
|
||||
<para>In its current version, &ktouch; 1.5 has quite a number of helpful
|
||||
features, such as:</para>
|
||||
<itemizedlist>
|
||||
<listitem><simpara>Support for many different training lectures in many
|
||||
languages including language specific text fonts and a comfortable lecture
|
||||
editor</simpara></listitem>
|
||||
<listitem><simpara>Support for different keyboard layouts with the ability to
|
||||
use user-defined layouts</simpara></listitem>
|
||||
<listitem><simpara>During your training session comprehensive statistical
|
||||
information is obtained to help you (or your teacher) analyse your
|
||||
progress</simpara></listitem>
|
||||
</itemizedlist>
|
||||
<para>
|
||||
Many other features are included and will be discussed in the appropriate
|
||||
chapters of this manual.
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="learning">
|
||||
<title>Learning touch typing with &ktouch;</title>
|
||||
|
||||
<para>Here's another screenshot of &ktouch; in action, this time with a german
|
||||
keyboard and training lecture:</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Main screen of &ktouch;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="main_window_german.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Main screen of &ktouch;</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Even though learning touch typing with &ktouch; and using the program
|
||||
should be very simple we will look a bit closer@&ktouch; in the following
|
||||
sections.</para>
|
||||
|
||||
<sect2 id="getting_started">
|
||||
<title>Getting started</title>
|
||||
|
||||
<para>When you start &ktouch; you can see the screen shown above. The main
|
||||
program window shows three main sections:
|
||||
</para>
|
||||
<orderedlist>
|
||||
<listitem><simpara>Some typing statistics in info boxes@the
|
||||
top</simpara></listitem>
|
||||
<listitem><simpara>The text you need to type (in the teacher's line) and the
|
||||
text that you have typed so far (in the student's line)</simpara></listitem>
|
||||
<listitem><simpara>The keyboard (that hopefully looks like
|
||||
yours)</simpara></listitem>
|
||||
</orderedlist>
|
||||
<para>We look@these sections later again.</para>
|
||||
<para>
|
||||
Ok, the first time you start &ktouch; it will open a default lecture and
|
||||
select a default keyboard layout. Before you start typing you should adjust
|
||||
the keyboard layout so that it matches yours. Go to
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Keyboard
|
||||
Layouts...</guimenuitem></menuchoice> and select the country you're in (or
|
||||
some country which uses the same keyboard layout as you). If your keyboard is
|
||||
not included, you can always define your own keyboard (see <link
|
||||
linkend="create_keyboards">Creating your own keyboard</link>).
|
||||
</para>
|
||||
<para>
|
||||
Once you have your keyboard selected, choose your training lecture. The first
|
||||
line in your corrent lecture and level is shown in the teacher's line. You can
|
||||
select any of the default lectures via
|
||||
<menuchoice><guimenu>Training</guimenu><guimenuitem>Default
|
||||
Lectures...</guimenuitem></menuchoice> or open a user defined lecture file
|
||||
(⪚ if your teacher gives you a special lecture to practice on) with
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Open
|
||||
Lecture...</guimenuitem></menuchoice>. You may even create your own lecture
|
||||
(see <link linkend="create_lectures">Creating your own lecture</link>). When
|
||||
you have selected keyboard and lecture you can start typing.
|
||||
</para>
|
||||
<para>
|
||||
Place your hand on the keyboard as indicated by the 8 marked finger keys
|
||||
(thumbs over the space bar) and start typing the text shown in the teacher's
|
||||
line. Each key you need to press is highlighted on the keyboard and if you
|
||||
need to move a finger from its resting position the target key and the
|
||||
appropriate finger key is highlighted. Try to move your hands as little as
|
||||
possible and after you typed a character always try to return your fingers to
|
||||
their resting positions.
|
||||
</para>
|
||||
<tip><para>The key colors indicate which finger needs to press which
|
||||
key.</para></tip>
|
||||
<para>
|
||||
While you type you may make mistakes and hit the wrong key. In that case the
|
||||
student's line will change its color (per default to red) and you have to hit
|
||||
Backspace to erase the wrong character (or characters) again.
|
||||
</para>
|
||||
<para>
|
||||
When you have successfully completed a line of text you need to press the
|
||||
Enter key to advance to the next line.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="lectures_and_levels">
|
||||
<title>Lectures and levels</title>
|
||||
<para>
|
||||
As already mentioned above you need to select a training lecture which
|
||||
contains all the text you want to practice. Usually the difficulty of the text
|
||||
is gradually increasing and so most lectures contain various difficulty
|
||||
levels. However, some lectures may just contain a single level and text (⪚
|
||||
a newspaper article to test your skills).
|
||||
</para>
|
||||
<para>
|
||||
In the info boxes@top of the &ktouch; main window you see the current
|
||||
level@the left. The small buttons to the right allow you to manually switch
|
||||
levels. Normally this happens automatically (more about this in the section
|
||||
<link linkend="training_options">Training Options</link>). The right info box
|
||||
shows a brief information text about the level. Usually it gives you a list of
|
||||
characters that are new in this level. The middle two info boxes show your
|
||||
current typing speed (in characters per minute) and your correctness. These
|
||||
values are Level Statistics and whenever you start a new level these values
|
||||
are resetted. However, the program still remembers your previous statistics
|
||||
(see section <link linkend="statistics">Statistics in &ktouch;</link>).
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="starting_stopping">
|
||||
<title>Starting and stopping a training session</title>
|
||||
<para>
|
||||
While you type the text of a training lecture you are in a practice session.
|
||||
You can start a new practice session using
|
||||
<menuchoice><guimenu>Training</guimenu><guimenuitem>Start New
|
||||
Session</guimenuitem></menuchoice> or the appropriate button in the toolbar.
|
||||
Level changes (automatic or manual) do not change your training session. You
|
||||
stay in this training session until you start a new training session, select a
|
||||
new lecture (which automatically starts a new training session) or quit the
|
||||
program.
|
||||
</para>
|
||||
<para>
|
||||
If you open any dialog in &ktouch; while you are in a training session the
|
||||
training is paused and the timer is stopped until you hit the next key. You
|
||||
can manually pause the session using
|
||||
<menuchoice><guimenu>Training</guimenu><guimenuitem>Pause
|
||||
Session</guimenuitem></menuchoice> or the appropriate button in the toolbar.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="statistics">
|
||||
<title>Statistics in &ktouch;</title>
|
||||
<para>&ktouch; remembers you! Basically whatever you type is recorded and some
|
||||
useful (and sometimes just interesting) statistics are created. &ktouch;
|
||||
stores statistical data based on the lecture file you use for training. For
|
||||
every lecture file a separate history is kept. &ktouch; also distinguishes
|
||||
between level and practice session statistics. This is important to prevent
|
||||
cheating :-).
|
||||
</para>
|
||||
|
||||
<sect2>
|
||||
<title>Training Session Statistics</title>
|
||||
<screenshot>
|
||||
<screeninfo>Current Training Statistics</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="statistics_dialog.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>Current Training Statistics</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>Whenever you start a new training session a new statistics record is
|
||||
started. &ktouch; remembers several things to assess your skill and to help
|
||||
you identify problem keys:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem><simpara>How many keys were pressed in total?</simpara></listitem>
|
||||
<listitem><simpara>How many were correctly pressed?</simpara></listitem>
|
||||
<listitem><simpara>Which keys where missed and how often?</simpara></listitem>
|
||||
<listitem><simpara>How many correct words did you type?</simpara></listitem>
|
||||
<listitem><simpara>How much time did you need?</simpara></listitem>
|
||||
</itemizedlist>
|
||||
<para>Using training session statistics you and &ktouch; can evaluate your
|
||||
overall performance and skill in a certain training lecture.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Level Statistics</title>
|
||||
<para>For each level in your training session (&ie; all levels you typed text
|
||||
in) the same statistics as for the training session are obtained. Using level
|
||||
statistics data you can investigate your progress in each level of a training
|
||||
lecture (and you will notice how your skill increases level by level and you
|
||||
can concentrate on the levels which still cause problems).
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The Statistics Dialog</title>
|
||||
<para><menuchoice><guimenu>Training</guimenu><guimenuitem>Lecture
|
||||
Statistics</guimenuitem></menuchoice> or the statistics button in the toolbar
|
||||
opens the statistics dialog. It displays your current training and level
|
||||
statistics and shows a graphical history of previous training sessions.
|
||||
</para>
|
||||
<para>
|
||||
When you open the statistics dialog you can select a Session Statistics Page
|
||||
and a Level Statistics Page. The first page gives you a summary about
|
||||
everything you typed so far. The Level Statistics Page only contains the stats
|
||||
for the current level. This is useful to distinguish between overall
|
||||
performance and skill in certain levels.
|
||||
</para>
|
||||
<para>
|
||||
The third statistics page gives you a graphical overview of your typing skill
|
||||
by offering several choices. A note about the time scaling option. Whenever a
|
||||
session or level statistic is obtained, also the date is stored. So you can
|
||||
also see how your skill dropped in long training breaks and when you last
|
||||
practiced a certain lecture or level.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>Training Statistics Chart</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="statistics_dialog_chart.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>Training Statistics Chart</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="ui_guide">
|
||||
<title>The &ktouch; main menu and program dialogs</title>
|
||||
<para>In this chapter we look@some of the details in the program.
|
||||
<tip><para>You can use the <quote>What's this?</quote> feature (the little
|
||||
question mark besides the minimize/maximize window buttons) in many dialogs of
|
||||
the program.</para></tip>
|
||||
</para>
|
||||
|
||||
<sect1 id="main_menu">
|
||||
<title>The menu of &ktouch;</title>
|
||||
<para>Pretty much everything in the &ktouch; menu should be self-explanatory.
|
||||
The file menu contains options to load a user defined lecture and edit
|
||||
lectures. The training menu contains training options and the settings menu
|
||||
contains options to setup the program. The various options in the
|
||||
configuration dialog are explained in the next section.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="program_settings">
|
||||
<title>Configuration options for &ktouch;</title>
|
||||
<para>You can customize &ktouch; quite a bit. The settings are always stored
|
||||
for the current user of the program. Open the configuration dialog via
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &ktouch;
|
||||
...</guimenuitem></menuchoice>.</para>
|
||||
|
||||
<sect2 id="general_options">
|
||||
<title>General Options</title>
|
||||
<para>In this dialog you can change general options that control the behaviour
|
||||
of &ktouch;.
|
||||
</para>
|
||||
<screenshot>
|
||||
<screeninfo>General options</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="general_options.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>General options</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>First of all you can switch the sound on or off (might be useful in
|
||||
class rooms). You can also set the sliding speed of the teacher's and
|
||||
student's line.
|
||||
</para>
|
||||
<para>Most important, however, might be the selection of the lecture font.
|
||||
When showing the teacher's text &ktouch; will normally use the font specified
|
||||
in the lecture file. But if this font doesn't exist on your system or none has
|
||||
been specified, &ktouch; uses a default system font. What if this font does
|
||||
not contain all characters needed for your lecture? In such cases you can
|
||||
override the choice of the font and specify any font you like.
|
||||
<note><para>&ktouch; distinguishes between lecture and keyboard fonts.
|
||||
Overriding the lecture font does not automatically adjust the keyboard font as
|
||||
well. Use the appropriate option in the Keyboard Options configuration
|
||||
page.</para></note>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="training_options">
|
||||
<title>Training Options</title>
|
||||
<para>In this dialog you can select the options that control how &ktouch;
|
||||
changes difficulty levels based on the user's skill.</para>
|
||||
<screenshot>
|
||||
<screeninfo>Training options</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="training_options.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>Training options</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>If <guibutton>Automatic level adjustment</guibutton> is enabled,
|
||||
&ktouch; checks the given limits@the end of each level and decides whether to
|
||||
increase or decrease the level or stay in the level for another run. Level
|
||||
changes occur always@the end of a level (&ie; when the user has finished the
|
||||
last line of a level). If the typing speed (in characters per seconds) and
|
||||
accuracy (correctness) are <emphasis>both</emphasis> above or equal to the
|
||||
<quote>Limits to increase level</quote> &ktouch; will jump to the next higher
|
||||
level. If <emphasis>either</emphasis> typing speed or accuracy falls below the
|
||||
<quote>Limits to decrease level</quote> &ktouch; will jump back to the
|
||||
previous lower level.
|
||||
</para>
|
||||
<para>
|
||||
On this configuration page you can also select that the program remembers your
|
||||
current level when you quit the program and jumps back to it when you restart
|
||||
&ktouch;.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="keyboard_options">
|
||||
<title>Keyboard Options</title>
|
||||
<para>In this dialog you can select keyboard specific options.</para>
|
||||
<screenshot>
|
||||
<screeninfo>Keyboard options</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="keyboard_options.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>Keyboard options</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
This dialog controls the appearance and functionality of the keyboard. Similar
|
||||
to the <quote>Override lecture font</quote> option in the general settings
|
||||
configuration page, you can here specify your own keyboard font. The option
|
||||
<quote>Highlight keys on keyboard</quote> can be used to increase the
|
||||
difficulty of the training. <tip><para>Once you are familiar with the keyboard
|
||||
you may want to turn keyboard highlighting off so it won't distract you when
|
||||
you concentrate on the teacher's text.</para></tip>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="color_options">
|
||||
<title>Color Options</title>
|
||||
<para>In this dialog you can tweak the appearance of &ktouch;.</para>
|
||||
<screenshot>
|
||||
<screeninfo>Color options</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject><imagedata fileref="color_options.png"
|
||||
format="PNG"/></imageobject>
|
||||
<textobject><phrase>Color options</phrase></textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
<para>
|
||||
This configuration page does not need much explaination. You can choose among
|
||||
four predefined color schemes for the keyboard. Alternatively you can switch
|
||||
the color schemes <quote>on the fly</quote> using the menu option
|
||||
<menuchoice><guimenu>Settings</guimenu><guimenuitem>Keyboard Color
|
||||
Schemes</guimenuitem></menuchoice>.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
||||
<chapter id="extending">
|
||||
<title>Extending &ktouch;</title>
|
||||
|
||||
<sect1 id="create_lectures">
|
||||
<title>Creating your own lecture</title>
|
||||
<para>You can easily create your own training lecture using the built-in
|
||||
&ktouch; lecture editor. When you select
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Edit
|
||||
Lecture...</guimenuitem></menuchoice> the <quote>Open Request Dialog</quote>
|
||||
will open and ask you to select a lecture. You can choose either edit the
|
||||
current lecture, any of the predefined lectures (if you have write access to
|
||||
the installation directoy) or create an empty lecture from scratch.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Creating a lecture</title>
|
||||
<para>
|
||||
Let's assume you want to create a new lecture. There are a few guidelines you
|
||||
may want to consider:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
|
||||
|
||||
<listitem><para>
|
||||
For the first 20 keys or so, only add 2 keys@a time to a new level. Let the
|
||||
user practice the keys alone first in different combinations and then use the
|
||||
new keys in words and mixed with already known words.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>Add@least a few levels to the lecture in order to allow the
|
||||
user to see some progress while training</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
Don't make the levels too long.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
Try to increase the difficulty of the text gradually and test your text
|
||||
yourself.
|
||||
</para></listitem>
|
||||
|
||||
<listitem><para>
|
||||
After the first keys have been learned include a recap lecture.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Things to know about lectures</title>
|
||||
<para>
|
||||
The lecture title is important for the quick-select menu entry in the training
|
||||
menu and for the statistics. The comment should be used to include information
|
||||
about the lecture author and source of lecture data if any.
|
||||
</para>
|
||||
<para>
|
||||
For each level you can specify the new characters/keys in the lecture. The
|
||||
text you enter there will be shown as level information text in the top right
|
||||
info box of the &ktouch; main window.
|
||||
</para>
|
||||
<para>You can also specify a default font for the lecture which will be used
|
||||
in the teacher's and student's line and of course in the edit lecture dialog
|
||||
using the <guibutton>Change Font...</guibutton> button.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="create_keyboards">
|
||||
<title>Creating your own keyboard</title>
|
||||
<para>You can create your own keyboards by creating keyboard files. Currently
|
||||
&ktouch; doesn't have a keyboard editor but it is still pretty easy to define
|
||||
your own keyboard. It doesn't require much more than a little math to work out
|
||||
the geometry and some time. Best is to start with an existing keyboard file,
|
||||
create a copy for your keyboard layout and simply adjust the lines.</para>
|
||||
<para>
|
||||
Currently keyboard files are plain UTF-8 encoded text files. In one of the
|
||||
next version of &ktouch; keyboard data will be stored in &XML; files, too.
|
||||
Therefore I'll only briefly explain the structure of a keyboard file.
|
||||
</para>
|
||||
<para>A keyboard file usually starts with a header including some information
|
||||
about the author and type of the keyboard.</para>
|
||||
<programlisting>
|
||||
####################################################
|
||||
# KTouch
|
||||
# Keybord layout file for german keybord layout
|
||||
# Code=UTF-8
|
||||
####################################################
|
||||
</programlisting>
|
||||
<para>
|
||||
All lines starting with a hash character '#' are considered comments. After
|
||||
the header section a block of so called <quote>finger keys</quote> follows,
|
||||
indicating the resting positions for all 8 fingers.
|
||||
</para>
|
||||
<programlisting>
|
||||
#
|
||||
# Unicode KeyChar x y
|
||||
#
|
||||
FingerKey 97 A 18 20
|
||||
FingerKey 115 S 28 20
|
||||
FingerKey 100 D 38 20
|
||||
FingerKey 102 F 48 20
|
||||
FingerKey 106 J 78 20
|
||||
FingerKey 107 K 88 20
|
||||
FingerKey 108 L 98 20
|
||||
FingerKey 246 Ö 108 20
|
||||
</programlisting>
|
||||
<para>Keys have the default dimensions of 8 units, so using a grid of 10 units
|
||||
gives a normal looking keyboard. The first number is the unicode character
|
||||
code as decimal number. The KeyText is the text printed on the key encoded as
|
||||
UTF-8 (automatic under newer &Linux; versions, just make sure your editor saves
|
||||
files as UTF-8 format).</para>
|
||||
<para>The next section contains special keys, which are - apart from BackSpace
|
||||
and Enter - just decorative.</para>
|
||||
<programlisting>
|
||||
#
|
||||
# Unicode KeyText x y Width Height
|
||||
#
|
||||
ControlKey 260 Tab 0 10 15 10
|
||||
ControlKey 13 Enter 138 20 12 10
|
||||
ControlKey 258 Shift 123 30 27 10
|
||||
ControlKey 264 AltGr 120 40 15 10
|
||||
ControlKey 265 Ctrl 135 40 15 10
|
||||
ControlKey 263 Alt 15 40 15 10
|
||||
ControlKey 262 Strg 0 40 15 10
|
||||
ControlKey 32 Leertaste 30 40 90 10
|
||||
ControlKey 257 Shift 0 30 13 10
|
||||
ControlKey 259 CapsLock 0 20 18 10
|
||||
ControlKey 8 BackSpace 130 0 20 10
|
||||
</programlisting>
|
||||
<para>
|
||||
The text you specify for the key is printed completely on the keyboard.
|
||||
However, for the keytexts <quote>Shift</quote>, <quote>CapsLock</quote>,
|
||||
<quote>Tab</quote>, <quote>BackSpace</quote> and <quote>Enter</quote> &ktouch;
|
||||
draws the appropriate symbols. Hence you can use these keytexts regardless of
|
||||
the language. The other keytexts like Ctrl or Alt need to be translated
|
||||
though. The geometry of the control keys can be any rectangle, defined by
|
||||
upper left x and y coordinates and width and height.</para>
|
||||
<para>The next section contains all characters on the keyboard (except the
|
||||
already defined finger keys) that can be typed <emphasis>without</emphasis>
|
||||
pressing shift.</para>
|
||||
<programlisting>
|
||||
#
|
||||
# Unicode KeyChar x y FingerKeyUnicode
|
||||
#
|
||||
NormalKey 94 ^ 0 0 97
|
||||
NormalKey 49 1 10 0 97
|
||||
NormalKey 50 2 20 0 115
|
||||
NormalKey 51 3 30 0 100
|
||||
NormalKey 52 4 40 0 102
|
||||
NormalKey 53 5 50 0 102
|
||||
NormalKey 54 6 60 0 102
|
||||
.
|
||||
.
|
||||
.
|
||||
NormalKey 46 . 103 30 108
|
||||
NormalKey 45 - 113 30 246
|
||||
</programlisting>
|
||||
<para>The definition of these primary keys or chars is pretty much the same as
|
||||
for the finger keys, but they include an additional property. The last unicode
|
||||
character code identifies the associated finger key. Basically which finger
|
||||
has to be used to press this key.</para>
|
||||
<para>
|
||||
The next and last section in a keyboard layout defines all keys that are
|
||||
pressed by using a modifier key such as the shift key.
|
||||
</para>
|
||||
<programlisting>
|
||||
#
|
||||
# Unicode TargetUnicode FingerUnicode ControllUnicode
|
||||
Comment
|
||||
#
|
||||
HiddenKey 65 97 97 258 #A
|
||||
HiddenKey 66 98 102 258 #B
|
||||
HiddenKey 67 99 100 258 #C
|
||||
HiddenKey 68 100 100 258 #D
|
||||
.
|
||||
.
|
||||
.
|
||||
HiddenKey 124 60 97 264 #|
|
||||
HiddenKey 64 113 97 264 #@
|
||||
</programlisting>
|
||||
<para>The <quote>hidden keys</quote> are really controlling what should happen
|
||||
on the keyboard when you type a certain character. The first unicode number is
|
||||
the character code of the character you define. The second number is the
|
||||
character code of the key on the keyboard (one of the already defined normal
|
||||
keys). The third number indicates a finger key (where does the finger rest
|
||||
that is needed to type the key) and the last number indicates the modifier key
|
||||
you need to press to get this character.
|
||||
</para>
|
||||
<para>Let's look@an example:</para>
|
||||
<para>You want to define the uppercase 'R' character. It has the unicode 82.
|
||||
The character obtained when the 'R' key is pressed without modifier is the
|
||||
small 'r' with the unicode 114. The finger for the 'R' rests over the 'f' key
|
||||
which has the unicode 102. And in order to get the 'R' you need to press the
|
||||
right (or left) shift key which has the code 264 (this is actually not a
|
||||
unicode but the code obtained from a keypress event of QT). Note that the
|
||||
identification of controll keys will likely change in the next version of
|
||||
&ktouch;. But for now you can use the codes used in other keyboard files.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="ktouch-mainwindow">
|
||||
<title>Menus and shortcut keys</title>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Lecture...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Open</action> a new training lecture
|
||||
file</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Edit Lecture...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Open</action> the lecture editor to allow you to
|
||||
change the current training file </para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quit</action> &ktouch;</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Training</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Training</guimenu>
|
||||
<guimenuitem>Start New Session</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Start</action> a new typing session and ask you if you
|
||||
want to start@the same level</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Training</guimenu>
|
||||
<guimenuitem>Pause Session</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Pause</action> the current session: statistics are on
|
||||
hold</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Training</guimenu>
|
||||
<guimenuitem>Lecture Statistics</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Open</action> the current session statistics
|
||||
dialog</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Training</guimenu>
|
||||
<guisubmenu>Default Lectures</guisubmenu>
|
||||
<guimenuitem>English (auto-generated)</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> what languagee you want to learn touch
|
||||
typing in</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show /HideToolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the Toolbar</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Keyboard Layouts</guisubmenu>
|
||||
<guimenuitem>number.keyboard</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the keyboard layout you want to use,
|
||||
here the number keyboard</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Keyboard Color Schemes</guisubmenu>
|
||||
<guimenuitem>Black'n White</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the keyboard color layout in black in
|
||||
white: all keys are white and the one you should type is
|
||||
black</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Keyboard Color Schemes</guisubmenu>
|
||||
<guimenuitem>Classic</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the classic keyboard color layout:
|
||||
each column of keys has a different color</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Keyboard Color Schemes</guisubmenu>
|
||||
<guimenuitem>Deep Blue</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the deep blue keyboard color layout:
|
||||
each column of keys has a different color in a shade of blue</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Keyboard Color Schemes</guisubmenu>
|
||||
<guimenuitem>Stripy</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Choose</action> the stripy keyboard color layout: in
|
||||
blue and grey</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Shortcuts...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> the shortcuts you want to associate
|
||||
with some actions
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure Toolbars...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Configure</action> the items you want to put in the
|
||||
toolbar
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &ktouch;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Display</action> the &ktouch; settings dialog
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
&help.menu.documentation;
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
<para>&ktouch;</para>
|
||||
<para>
|
||||
&ktouch;, Copyright 1999-2005 by</para>
|
||||
<itemizedlist>
|
||||
<listitem><simpara>Håvard Frøiland <email>haavard@users.sourceforge DOT
|
||||
net</email></simpara></listitem>
|
||||
<listitem><simpara>Andreas Nicolai <email>andreas.nicolai@gmx DOT
|
||||
net</email></simpara></listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para> Contributors:</para>
|
||||
<itemizedlist>
|
||||
<listitem><simpara>Frank Quotschalla, German keyboard and german training file and
|
||||
translation.</simpara></listitem>
|
||||
<listitem><simpara>Ernesto Hernández-Novich, Latinamerican
|
||||
keyboard</simpara></listitem>
|
||||
<listitem><simpara>João Miguel Neves, Portuguese keyboard</simpara></listitem>
|
||||
<listitem><simpara>Henri Girard, Frence keyboard</simpara></listitem>
|
||||
</itemizedlist>
|
||||
<para><emphasis>Special thanks to all the other (here not mentioned) contributors of keyboard and lecture files.</emphasis>
|
||||
</para>
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL; <!-- FDL: do not remove -->
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>How to obtain and install &ktouch;</title>
|
||||
|
||||
<para>&ktouch; has its own home page <ulink
|
||||
url="http://ktouch.sourceforge.net">http://ktouch.sourceforge.net</ulink>. Please refer to the instructions on the home page since they will contain up-to-date information about how to obtain &ktouch;.
|
||||
</para>
|
||||
<para>&ktouch; can also be found
|
||||
on <ulink url="http://edu.kde.org/ktouch">The &kde; Edutainment - &ktouch; home page</ulink>
|
||||
and is part of the &kde;-Edutainment project. </para>
|
||||
|
||||
</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:
|
||||
|
||||
// vim:ts=2:sw=2:tw=78:noet
|
||||
-->
|
||||
|
After Width: | Height: | Size: 32 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 25 KiB |
@ -0,0 +1,79 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<title>KDE User's Manual</title>
|
||||
<author><personname>
|
||||
<firstname>Ben</firstname>
|
||||
<surname>Burton</surname>
|
||||
</personname>
|
||||
<email>bab@debian.org</email></author>
|
||||
<date>30 May, 2005</date>
|
||||
<productname>K Desktop Environment</productname>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>ktouch</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>ktouch</command></refname>
|
||||
<refpurpose>a typing tutor for KDE</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>ktouch</command>
|
||||
<group choice="opt"><option>URL</option></group>
|
||||
<arg choice="opt">KDE Generic Options</arg>
|
||||
<arg choice="opt">Qt Generic Options</arg>
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
<para>&ktouch; is a program for learning touch typing. It helps you learn
|
||||
to type on a keyboard quickly and correctly. Every finger has it's place on
|
||||
the keyboard with associated keys to press.</para>
|
||||
<para>&ktouch; helps you learn to touch type by providing you with text to
|
||||
train on, and adjusts to different levels depending on how good you are. It
|
||||
can display which key to press next, and correct finger to use.</para>
|
||||
<para>This application is part of the official &kde; edutainment
|
||||
module.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Options</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><option>URL</option></term>
|
||||
<listitem><para>The training file to open</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
<para>More detailed user documentation is available from <ulink
|
||||
url="help:/ktouch">help:/ktouch</ulink>
|
||||
(either enter this <acronym>URL</acronym> into &konqueror;, or run
|
||||
<userinput><command>khelpcenter</command>
|
||||
<parameter>help:/ktouch</parameter></userinput>).</para>
|
||||
|
||||
<para>There is also further information available at the <ulink
|
||||
url="http://edu.kde.org/ktouch/">&kde; edutainment website</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
<para>KTouch was written by <personname><firstname>Haavard</firstname><surname>Froeiland</surname></personname> <email>haavard@users.sourceforge.net</email> and <personname><firstname>Andreas</firstname><surname>Nicolai</surname></personname> <email>Andreas.Nicolai@gmx.net</email>.This manual page based on the one prepared for Debian by <personname>
|
||||
<firstname>Ben</firstname><surname>Burton</surname></personname>
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 39 KiB |
|
After Width: | Height: | Size: 37 KiB |
|
After Width: | Height: | Size: 38 KiB |
@ -0,0 +1,3 @@
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 17 KiB |
@ -0,0 +1,147 @@
|
||||
<!--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application
|
||||
Thanks a lot in advance.-->
|
||||
<chapter id="getting-started">
|
||||
<title>Getting Started</title>
|
||||
<para>When you start &kturtle; you will see something like this:
|
||||
<screenshot>
|
||||
<screeninfo>Here is a screenshot of &kturtle; when you start it for the first time</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="mainwindow.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kturtle; Main window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
In this Getting Started guide we assume that the language of the &logo; commands is English. You can change this language in <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kturtle;...</guimenuitem></menuchoice> in the <guilabel>Language</guilabel> section. Be aware that the language you set here for &kturtle; is the one you use to type the &logo; commands.</para>
|
||||
|
||||
<sect1 id="first-steps">
|
||||
<title>First steps with &logo;: meet the Turtle!</title>
|
||||
<para>You must have noticed the turtle in the middle of the canvas: you are just about to learn how to control it using commands in the code editor.</para>
|
||||
|
||||
<sect2 id="the-turtle-moves">
|
||||
<title>The Turtle Moves</title>
|
||||
<para>Let us start by getting the turtle moving. Our turtle can do 3 types of moves, (1) it can go forwards and backwards, (2) it can turn left and right and (3) it can go directly to a position on the screen. Try this for example:</para>
|
||||
<para>
|
||||
<screen>
|
||||
forward 100
|
||||
turnleft 90
|
||||
</screen>
|
||||
Type or copy-paste the code to the code editor and execute it (using <link linkend="file-execute"><menuchoice><guimenu>File</guimenu><guimenuitem>Execute Commands</guimenuitem></menuchoice></link>) to see the result.</para>
|
||||
|
||||
<para>When you typed and executed the commands like above in the code editor you might have noticed one or more of the following things:</para>
|
||||
<orderedlist>
|
||||
<listitem><para>That — after executing the commands — the turtle moves up, draws a line, and then turns a quarter turn to the left. This because you have used the <link linkend="forward"><userinput>forward</userinput></link> and the <link linkend="turnleft"><userinput>turnleft</userinput></link> commands.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>That the color of the code changed while you where typing it: this feature is called <emphasis>intuitive highlighting</emphasis> — different types of commands are highlighted differently. This makes reading large blocks of code more easy.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>That the turtle draws a thin black line.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Maybe you got an error message. This could simply mean two things: you could have made a mistake while copying the commands, or you should still set the correct language for the &logo; commands (you can do that by choosing <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kturtle;...</guimenuitem></menuchoice>, in the <guilabel>Language</guilabel> section).</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>You will likely understand that <userinput>forward 100</userinput> commanded the turtle to move forward leaving a line, and that <userinput>turnleft 90</userinput> commanded the turtle to turn 90 <glossterm linkend="degrees">degrees</glossterm> to the left.</para>
|
||||
|
||||
<para>Please see the following links to the reference manual for a complete explanation of the new commands: <userinput>forward</userinput>, <userinput>backward</userinput>, <userinput>turnleft</userinput>, and <userinput>turnright</userinput>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="more-examples">
|
||||
<title>More examples</title>
|
||||
<para>The first example was very simple, so let us go on!</para>
|
||||
|
||||
<para>
|
||||
<!--translators: if it's not already there, you can copy/paste the translated code below and save it in arrow.logo in your examples folder: kde-i18n/language-code/data/kdeedu/kturtle/ -->
|
||||
<screen>
|
||||
canvassize 200,200
|
||||
canvascolor 0,0,0
|
||||
pencolor 255,0,0
|
||||
penwidth 5
|
||||
clear
|
||||
|
||||
go 20,20
|
||||
direction 135
|
||||
|
||||
forward 200
|
||||
turnleft 135
|
||||
forward 100
|
||||
turnleft 135
|
||||
forward 141
|
||||
turnleft 135
|
||||
forward 100
|
||||
turnleft 45
|
||||
|
||||
go 40, 100
|
||||
</screen>
|
||||
Again you can type or copy-paste the code to the code editor or open the <filename>arrow.logo</filename> file in the <guimenu>Open Examples</guimenu> folder and execute it (using <link linkend="file-execute"><menuchoice><guimenu>File</guimenu><guimenuitem>Execute Commands</guimenuitem></menuchoice></link>) to see the result. In the next examples you are expected to know the drill.</para>
|
||||
|
||||
<para>You might have noticed that this second example uses a lot more code. You have also seen a couple of new commands. Here a short explanation of all the new commands:</para>
|
||||
|
||||
<para><userinput>canvassize 200,200</userinput> sets the canvas width and height to 200 <glossterm linkend="pixels">pixels</glossterm>. The width and the height are equal, so the canvas will be a square.</para>
|
||||
|
||||
<para><userinput>canvascolor 0,0,0</userinput> makes the canvas black. <userinput>0,0,0</userinput> is a <glossterm linkend="rgb">RGB-combination</glossterm> where all values are set to <userinput>0</userinput>, which results in black.</para>
|
||||
|
||||
<para><userinput>pencolor 255,0,0</userinput> sets the color of the pen to red. <userinput>255,0,0</userinput> is a <glossterm linkend="rgb">RGB-combination</glossterm> where only the red value is set to <userinput>255</userinput> (fully on) while the others (green and blue) are set to <userinput>0</userinput> (fully off). This results in a bright shade of red.</para>
|
||||
|
||||
<para>If you do not understand the color values, be sure to read the glossary on <glossterm linkend="rgb">RGB-combination</glossterm>s</para>
|
||||
|
||||
<para><userinput>penwidth 5</userinput> sets the width (the size) of the pen to <userinput>5</userinput> <glossterm linkend="pixels">pixels</glossterm>. From now on every line the turtle draw will have a thickness of <userinput>5</userinput>, until we change the <userinput>penwidth</userinput> to something else.</para>
|
||||
|
||||
<para><userinput>clear</userinput> clear the canvas, that is all it does.</para>
|
||||
|
||||
<para><userinput>go 20,20</userinput> commands the turtle to go to a certain place on the canvas. Counted from the upper left corner, this place is 20 <glossterm linkend="pixels">pixels</glossterm> across from the left, and 20 <glossterm linkend="pixels">pixels</glossterm> down from the top of the canvas. Note that using the <userinput>go</userinput> command the turtle will not draw a line.</para>
|
||||
|
||||
<para><userinput>direction 135</userinput> set the turtle's direction. The <userinput>turnleft</userinput> and <userinput>turnright</userinput> commands change the turtle's angle starting from its current direction. The <userinput>direction</userinput> command changes the turtle's angle from zero, and thus is not relative to the turtle previous direction.</para>
|
||||
|
||||
<para>After the <userinput>direction</userinput> command a lot of <userinput>forward</userinput> and <userinput>turnleft</userinput> commands follow. These command do the actual drawing.</para>
|
||||
|
||||
<para>At last another <userinput>go</userinput> command is used to move the turtle aside.</para>
|
||||
|
||||
<para>Make sure you follow the links to the reference. The reference explains each command more thoroughly.</para>
|
||||
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
||||
|
||||
<!-- EXTRA SECTIONS CAN BE ADDED TO THE "GETTING STARTED"
|
||||
|
||||
<sect1 id="calculations">
|
||||
<title>Simple Calculations</title>
|
||||
<para>
|
||||
Not yet written
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="using_variables">
|
||||
<title>Using Variables: creating 'number containers'</title>
|
||||
<para>
|
||||
Not yet written
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="using_strings">
|
||||
<title>Using strings: creating 'text containers'</title>
|
||||
<para>
|
||||
Not yet written
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="logic">
|
||||
<title>Logic: asking the computer simple questions</title>
|
||||
<para>
|
||||
Not yet written
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="recursion">
|
||||
<title>Recursion: the Turtle is using itself</title>
|
||||
<para>
|
||||
Draw a maze for example
|
||||
</para>
|
||||
</sect1>
|
||||
-->
|
||||
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,173 @@
|
||||
<!--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application
|
||||
Thanks a lot in advance.-->
|
||||
<chapter id="Glossary">
|
||||
<title>Glossary</title>
|
||||
|
||||
<para>In this chapter you will find an explanation of most of the <quote>uncommon</quote> words that are used in the handbook.</para>
|
||||
|
||||
<glosslist>
|
||||
<glossentry id="degrees">
|
||||
<glossterm>degrees</glossterm>
|
||||
<glossdef><para>Degrees are units to measure angles or turns. A full turn is 360 degrees, a half turn 180 degrees and a quarter turn 90 degrees. The commands <userinput>turnleft</userinput>, <userinput>turnright</userinput> and <userinput>direction</userinput> need an input in degrees.</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="input-output">
|
||||
<glossterm>input and output of commands</glossterm>
|
||||
<glossdef><para>Some commands take input, some commands give output, some commands take input <emphasis>and</emphasis> give output and some commands neither take input nor give output.</para>
|
||||
<para>Some examples of commands that only take input are:
|
||||
<screen>
|
||||
forward 50
|
||||
pencolor 255,0,0
|
||||
print "Hello!"
|
||||
</screen>
|
||||
The <userinput>forward</userinput> command takes <userinput>50</userinput> as input. <userinput>forward</userinput> needs this input to know how many <glossterm linkend="pixels">pixels</glossterm> it should go forward. <userinput>pencolor</userinput> takes a color as input and <userinput>print</userinput> takes a string (a piece of text) as input. Please note that the input can also be a container. The next example illustrates this:
|
||||
<screen>
|
||||
x = 50
|
||||
print x
|
||||
str = "hello!"
|
||||
print str
|
||||
</screen></para>
|
||||
|
||||
<para>Now some examples of commands that give output:
|
||||
<screen>
|
||||
x = inputwindow "Please type something and press OK... thanks!"
|
||||
r = random 1,100
|
||||
</screen>
|
||||
The <userinput>inputwindow</userinput> command takes a string as input, and outputs the number or string that is entered. As you can see, the output of <userinput>inputwindow</userinput> is stored in the container <userinput>x</userinput>. The <userinput>random</userinput> command also gives output. In this case it outputs a number between 1 and 100. The output of the random is again stored in a container, named <userinput>r</userinput>. Note that the containers <userinput>x</userinput> and <userinput>r</userinput> are not used in the example code above.</para>
|
||||
|
||||
<para>There are also commands that neither need input nor give output. Here are some examples:
|
||||
<screen>
|
||||
clear
|
||||
penup
|
||||
wrapon
|
||||
hide
|
||||
</screen>
|
||||
</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="intuitive-highlighting">
|
||||
<glossterm>intuitive highlighting</glossterm>
|
||||
<glossdef><para>This is a feature of &kturtle; that makes coding even easier. With intuitive highlighting the code that you write gets a color that indicates what type of code it is. In the next list you will find the different types of code and the color they get in <link linkend="the-code-editor">the code editor</link>.
|
||||
<table>
|
||||
<title>Different types of code and their highlight color</title>
|
||||
<tgroup cols="3">
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>regular commands</entry>
|
||||
<entry>dark green</entry>
|
||||
<entry>The regular commands are described <link linkend="commands">here</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>execution controllers</entry>
|
||||
<entry>black (bold)</entry>
|
||||
<entry>The special commands control execution, read more on them <link linkend="controlling-execution">here</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>comments</entry>
|
||||
<entry>dark yellow</entry>
|
||||
<entry>Lines that are commented start with a comment characters (#). These lines are ignored when the code is executed. Comments allow the programmer to explain a bit about his code or can be used to temporarily prevent a certain piece of code from executing.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>brackets [, ]</entry>
|
||||
<entry>light green (bold)</entry>
|
||||
<entry>Brackets are used to group portions of code. Brackets are often used together with <link linkend="controlling-execution">execution controllers</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>the <link linkend="learn">learn</link> command</entry>
|
||||
<entry>light green (bold)</entry>
|
||||
<entry>The <link linkend="learn">learn</link> command is used to create new commands.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>numbers</entry>
|
||||
<entry>blue</entry>
|
||||
<entry>Numbers, well not much to say about them.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>strings</entry>
|
||||
<entry>dark red</entry>
|
||||
<entry>Not much to say about (text) strings either, except that they always start and end with the double quotes (").</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>mathematical characters</entry>
|
||||
<entry>grey</entry>
|
||||
<entry>These are the mathematical characters: +, -, *, /, (, and ). Read more about them <link linkend="math">here</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>questions characters</entry>
|
||||
<entry>blue (bold)</entry>
|
||||
<entry>Read more about questions <link linkend="questions">here</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>question glue-words</entry>
|
||||
<entry>pink</entry>
|
||||
<entry>Read more about the question glue-words (and, or, not) <link linkend="question-glue">here</link>.</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry>regular text</entry>
|
||||
<entry>black</entry>
|
||||
<entry></entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="pixels">
|
||||
<glossterm>pixels</glossterm>
|
||||
<glossdef><para>A pixel is a dot on the screen. If you look very close you will see that the screen of your monitor uses pixels. All images on the screen are built with these pixels. A pixel is the smallest thing that can be drawn on the screen.</para>
|
||||
<para>A lot of commands need a number of pixels as input. These commands are: <userinput>forward</userinput>, <userinput>backward</userinput>, <userinput>go</userinput>, <userinput>gox</userinput>, <userinput>goy</userinput>, <userinput>canvassize</userinput> and <userinput>penwidth</userinput>.</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="rgb">
|
||||
<glossterm>RGB combinations (color codes)</glossterm>
|
||||
<glossdef><para>RGB combinations are used to describe colors. The <quote>R</quote> stand for <quote>red</quote>, the <quote>G</quote> stands for <quote>green</quote> and the <quote>B</quote> stands for <quote>blue</quote>. An example of an RGB combination is <userinput>255,0,0</userinput>: the first value (<quote>red</quote>) is 255 and the others are 0, so this represents a bright shade of red. Each value of an RGB combination has to be in the range 0 to 255. Here a small list of some often used colors:
|
||||
<table frame="none">
|
||||
<title>Often used RGB combinations</title>
|
||||
<tgroup cols="2" colsep="5" rowsep="1">
|
||||
<colspec colname="c1"/>
|
||||
<tbody>
|
||||
<row><entry><userinput>0,0,0</userinput></entry><entry>black</entry></row>
|
||||
<row><entry><userinput>255,255,255</userinput></entry><entry>white</entry></row>
|
||||
<row><entry><userinput>255,0,0</userinput></entry><entry>red</entry></row>
|
||||
<row><entry><userinput>150,0,0</userinput></entry><entry>dark red</entry></row>
|
||||
<row><entry><userinput>0,255,0</userinput></entry><entry>green</entry></row>
|
||||
<row><entry><userinput>0,0,255</userinput></entry><entry>blue</entry></row>
|
||||
<row><entry><userinput>0,255,255</userinput></entry><entry>light blue</entry></row>
|
||||
<row><entry><userinput>255,0,255</userinput></entry><entry>pink</entry></row>
|
||||
<row><entry><userinput>255,255,0</userinput></entry><entry>yellow</entry></row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
<para>To easily find the RGB combinations of a color you should try the color picker! You can open the color picker using <link linkend="tools-color-picker"><menuchoice><guimenu>Tools</guimenu><guimenuitem>Color Picker</guimenuitem></menuchoice></link>.</para>
|
||||
<para>Two commands need an RGB combination as input: these commands are <userinput>canvascolor</userinput> and <userinput>pencolor</userinput>.</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="sprite">
|
||||
<glossterm>sprite</glossterm>
|
||||
<glossdef><para>A sprite is a small picture that can be moved around the screen. Our beloved turtle, for instance, is a sprite.</para>
|
||||
<para>Note: with this version of &kturtle; the sprite cannot be changed from a turtle into something else. Future versions of &kturtle; will be able to do this.</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
<glossentry id="wrapping">
|
||||
<glossterm>wrapping</glossterm>
|
||||
<glossdef><para>Wrapping is what happens when the turtle draws something that is to big to fix in on the canvas and wrapping is set <quote>on</quote>.
|
||||
<screenshot>
|
||||
<screeninfo>This is what happens when wrapping is <quote>on</quote></screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="wrapping.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>An example of wrapping</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
When the turtle moves off a border of the canvas it is instantly taken to the opposite border so it can continue its move. This way the turtle will always stay on the screen while it moves. This happens when wrapping is on.</para>
|
||||
<para>Wrapping can be turned on and off with the <userinput>wrapon</userinput> and <userinput>wrapoff</userinput> commands. When &kturtle; starts wrapping is turned on by default.</para></glossdef>
|
||||
</glossentry>
|
||||
|
||||
</glosslist>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,243 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
|
||||
"dtd/kdex.dtd" [
|
||||
<!ENTITY kappname "&kturtle;">
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY logo "Logo">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
<!ENTITY using-kturtle SYSTEM "using-kturtle.docbook">
|
||||
<!ENTITY getting-started SYSTEM "getting-started.docbook">
|
||||
<!ENTITY programming-reference SYSTEM "programming-reference.docbook">
|
||||
<!ENTITY translator-guide SYSTEM "translator-guide.docbook">
|
||||
<!ENTITY glossary SYSTEM "glossary.docbook">
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kturtle; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Cies</firstname>
|
||||
<surname>Breijs</surname>
|
||||
<affiliation>
|
||||
<address><email>cies AT kde DOT nl</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<author>
|
||||
<firstname>Anne-Marie</firstname>
|
||||
<surname>Mahfouf</surname>
|
||||
<affiliation>
|
||||
<address><email>annma AT kde DOT org</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
|
||||
<copyright>
|
||||
<year>2004</year>
|
||||
<holder>Cies Breijs</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2005-12-10</date>
|
||||
<releaseinfo>0.6</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kturtle; is an educational programming environment using the &logo; programming language. The unique quality of LOGO is that the programming commands are translated to the language of the 'programmer' so he/she can program in his/her native language.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeedu</keyword>
|
||||
<keyword>KTurtle</keyword>
|
||||
<keyword>education</keyword>
|
||||
<keyword>language</keyword>
|
||||
<keyword>native</keyword>
|
||||
<keyword>programming</keyword>
|
||||
<keyword>code</keyword>
|
||||
<keyword>&logo;</keyword>
|
||||
<keyword>instructions</keyword>
|
||||
<keyword>turtle</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>&kturtle; is an educational programming environment using the
|
||||
<link linkend="what-is-logo">&logo;</link> programming language. The goal of &kturtle; is to make programming as easy and accessible as possible. This makes &kturtle; suitable for teaching kids the basics of math, geometry and... programming. The commands used to program are in the style of the &logo; programming language. The unique feature of the &logo; programming language is that the commands are often translated into the speaking language of the programmer.</para>
|
||||
|
||||
<para>&kturtle; is named after <quote>the turtle</quote> that plays a central role in the programming environment. The user programs the turtle, using the &logo; commands, to draw a picture on <link linkend="the-canvas">the canvas</link>.</para>
|
||||
|
||||
<sect1 id="what-is-logo">
|
||||
<title>What is &logo;?</title>
|
||||
<para>The first version &logo; programming language was created by Seymour
|
||||
Papert of MIT Artificial Intelligence Laboratory in 1967 as an offshoot of the
|
||||
LISP programming language. From then many versions of &logo; have been released.
|
||||
By 1980 &logo; was gaining momentum, with versions for MSX, Commodore, Atari,
|
||||
Apple II and IBM PC systems. These versions were mainly for educational
|
||||
purposes. LCSI released <application>&Mac;&logo;</application> in 1985 as a tool
|
||||
for professional programmers, but it never caught on. MIT is still maintaining a
|
||||
site on &logo; which can be found on <ulink
|
||||
url="http://el.media.mit.edu/logo-foundation/">http://el.media.mit.edu/logo-
|
||||
foundation/</ulink>.</para>
|
||||
|
||||
<para>Today there are several versions of &logo; around which can easily be found on <ulink url="http://el.media.mit.edu/logo-foundation/">MIT's &logo; site</ulink> and by a simple <ulink url="http://www.google.com/search?q=logo+programming+kids">Google search</ulink>. This version of &logo; (&kturtle;) is only focused on the educational qualities of the programming language and will not try to suit professional programmers' needs.</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="features-of-kturtle">
|
||||
<title>Features of &kturtle;</title>
|
||||
<para>&kturtle; has some nice features that make starting to program a breeze. See here some of the highlights of &kturtle; feature set:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
An integrated &logo; interpreter (no extra dependencies) that uses &XML; files for the command translations, supports user defined functions and dynamic type switching.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
The execution can be slown down, paused or stopped at any time.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
A powerful editor for the &logo; commands with intuitive syntax highlighting, line numbering and more.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<link linkend="the-canvas">The canvas</link> can be saved as an image or printed.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
<link linkend="the-canvas">The canvas</link> has a wrapping mode (which is on by default) so the turtle cannot get lost too easily.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Context help for all &logo; commands: Just press <keysym>F2</keysym>.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
The &logo; commands are fully translatable (at the moment of writing Brazilian Portuguese, Dutch, French, German, Italian, Slovenian, Serbian (Cyrillic and Latin), Spanish and Swedish are in &kde;).
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
An error dialog that links the error messages to the mistakes in the program.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Simplified programming terminology.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Full-screen mode.
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
Many integrated, internationalized example &logo; programs make it easy to get started.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
&using-kturtle;
|
||||
|
||||
&getting-started;
|
||||
|
||||
&programming-reference;
|
||||
|
||||
&glossary;
|
||||
|
||||
&translator-guide;
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kturtle;
|
||||
</para>
|
||||
<para>Program copyright 2003-2005 Cies Breijs <email>cies AT kde DOT nl</email></para>
|
||||
<para>
|
||||
Contributors:
|
||||
<itemizedlist>
|
||||
<listitem><para>Coding help, editor part: &Anne-Marie.Mahfouf; &Anne-Marie.Mahfouf.mail;</para>
|
||||
</listitem>
|
||||
<listitem><para>Author of <application>WSBASIC</application> (<ulink url="http://wsbasic.sourceforge.net">http://wsbasic.sourceforge.net</ulink>) which is the base for the interpreter of &kturtle;: Walter Schreppers <email>Walter DOT Schreppers AT ua DOT ac DOT be</email></para>
|
||||
</listitem>
|
||||
<listitem><para>German Data Files: Matthias Meßmer <email>bmlmessmer AT web DOT de</email></para>
|
||||
</listitem>
|
||||
<listitem><para>German Data Files: Burkhard Lück <email>lueck AT hube-lueck DOT de</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Swedish Data Files: Stefan Asserhäll <email>stefan DOT asserhal AT telia DOT com</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Slovenian Data Files: Jure Repinc <email>jlp@holodeck1.com</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Serbian (Cyrillic and Latin) Data Files: Chusslove Illich <email>caslav.ilic@gmx.net</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Italian Data Files: Pino Toscano <email>toscano.pino@tiscali.it</email></para>
|
||||
</listitem>
|
||||
<listitem><para>English GB Data Files: Andy Potter <email>A.J.Potter@rhul.ac.uk</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Spanish Data Files: Rafael Beccar <email>rafael.beccar@kdemail.net</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Brazilian Portuguese Data Files: Riverson Rios <email>riverson@ccv.ufc.br</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Norwegian Nynorsk and Bokmål Data Files: Karl Ove Hufthammer <email>karl@huftis.org</email></para>
|
||||
</listitem>
|
||||
<listitem><para>Parser Cyrillic support: Albert Astals Cid <email>astals11@terra.es</email></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Documentation copyright 2004
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
Cies Breijs <email>cies AT kde DOT nl</email>
|
||||
</para></listitem>
|
||||
<listitem><para>
|
||||
&Anne-Marie.Mahfouf; <email>annma AT kde DOT org</email>
|
||||
</para></listitem>
|
||||
<listitem><para>Some proofreading changes by &Philip.Rodrigues; &Philip.Rodrigues.mail;</para>
|
||||
</listitem>
|
||||
<listitem><para>Updated translation how-to and some proofreading changes by Andrew Coles <email>andrew_coles AT yahoo DOT co DOT uk</email></para>
|
||||
</listitem>
|
||||
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
|
||||
&underFDL;
|
||||
|
||||
&underGPL; <!-- GPL License -->
|
||||
|
||||
</chapter>
|
||||
|
||||
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kturtle">
|
||||
<title>How to obtain &kturtle;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 27 KiB |
|
After Width: | Height: | Size: 44 KiB |
|
After Width: | Height: | Size: 23 KiB |
@ -0,0 +1,822 @@
|
||||
<!--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application
|
||||
Thanks a lot in advance.-->
|
||||
<chapter id="reference">
|
||||
<title>&kturtle;'s &logo; Programming Reference</title>
|
||||
<para>This is the reference for the &kturtle;'s &logo;. In this chapter we first briefly touch all the <link linkend="different-instructions">different instruction types</link>. Then the <link linkend="commands">commands</link> are explained one by one. Then <link linkend="containers">containers</link>, <link linkend="math">math</link>, <link linkend="questions">questions</link> and <link linkend="controlling-execution">execution controllers</link> are explained. At last you are shown how to create you own commands with <link linkend="learn">learn</link>.</para>
|
||||
|
||||
<sect1 id="different-instructions">
|
||||
<title>Different Instruction Types</title>
|
||||
<para>As in any language, LOGO has different types of words and symbols. Here the differences between the types are briefly explained.</para>
|
||||
|
||||
<sect2 id="command">
|
||||
<title>Commands</title>
|
||||
<para>Using commands you tell the turtle or &kturtle; to do something. Some commands need input, some give output.
|
||||
<screen>
|
||||
# forward is a command that needs input, in this case the number 100:
|
||||
forward 100
|
||||
</screen>
|
||||
</para>
|
||||
<para>For a detailed overview of all commands that &kturtle; supports go <link linkend="commands">here</link>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="number">
|
||||
<title>Numbers</title>
|
||||
<para>Most likely you already know quite a bit about numbers. The way numbers are used in &kturtle; is not much different from spoken language, or math. </para>
|
||||
<para>We have the so called natural numbers: <userinput>0</userinput>, <userinput>1</userinput>, <userinput>2</userinput>, <userinput>3</userinput>, <userinput>4</userinput>, <userinput>5</userinput>, etc. The negative numbers: <userinput>-1</userinput>, <userinput>-2</userinput>, <userinput>-3</userinput>, etc. And the numbers with decimals, or dot-numbers, for example: <userinput>0.1</userinput>, <userinput>3.14</userinput>, <userinput>33.3333</userinput>, <userinput>-5.05</userinput>, <userinput>-1.0</userinput>.
|
||||
</para>
|
||||
<para>Numbers can be used in <link linkend="math">mathematical calculations</link> and <link linkend="questions">questions</link>. They can also be put in <link linkend="containers">containers</link>.</para>
|
||||
<para>Numbers are <glossterm>highlighted</glossterm> with blue in the <link linkend="the-code-editor">code editor</link>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="string">
|
||||
<title>Strings</title>
|
||||
<para>First an example:
|
||||
<screen>
|
||||
print "Hello, I'm a string."
|
||||
</screen>
|
||||
In this example <userinput>print</userinput> is a command where <userinput>"Hello, I'm a string."</userinput> is a string. Strings start and end with the <userinput>"</userinput> mark, by these marks &kturtle; knows it is a string.</para>
|
||||
<para>Strings can be put in <link linkend="containers">containers</link>. Yet they cannot be used in <link linkend="math">mathematical calculations</link> and <link linkend="questions">questions</link>.</para>
|
||||
<para>Strings are <glossterm>highlighted</glossterm> with dark red in the <link linkend="the-code-editor">code editor</link>.</para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="name">
|
||||
<title>Names</title>
|
||||
<para>When using the &logo; programming language you create new things. If you write a program you will often need <link linkend="containers">containers</link> and in some cases you need <link linkend="learn">learn</link> to create new commands. When making a <link linkend="containers">container</link> or a new command with <link linkend="learn">learn</link> you will have to specify a name.</para>
|
||||
<para>You can choose any name, as long as it does not already have a meaning. For instance you cannot name a container <link linkend="forward">forward</link>, since that name is already used for a command, and thus has a meaning.
|
||||
<screen>
|
||||
# here forward is used as a container, but it already has a meaning
|
||||
# so this will produce an error:
|
||||
forward = 20
|
||||
|
||||
# this works:
|
||||
forward 20
|
||||
</screen>
|
||||
Names can contain only letters, numbers and underscores (_). Yet they have to start with a letter.
|
||||
</para>
|
||||
<para>
|
||||
Please read the documentation on <link linkend="containers">containers</link> and the <link linkend="learn">learn</link> command for a better explanation and more examples.
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="assignment">
|
||||
<title>Assignments</title>
|
||||
<para>Assignment are done with the <userinput>=</userinput> symbol. In programming languages it is better to read the single <userinput>=</userinput> not as 'equals' but as 'becomes'. The word 'equals' is more appropriate for the <userinput>==</userinput> which is a <link linkend="questions">question</link>.</para>
|
||||
<para>Assignments are generally use for two reasons, (1) to add content <link linkend="containers">containers</link>, and (2) to modify the content of a container. For example:
|
||||
<screen>
|
||||
x = 10
|
||||
# the container x now contains the number 10
|
||||
W = "My age is: "
|
||||
# the container W now contains the string "My age is: "
|
||||
# this prints the content of the containers 'W' and 'x' on the canvas
|
||||
print W + x
|
||||
</screen>
|
||||
</para>
|
||||
<para>For more examples see the section that explains <link linkend="containers">containers</link>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="math-symbols">
|
||||
<title>Math Symbols</title>
|
||||
<para>&kturtle; supports all basic math symbols: add (<userinput>+</userinput>), substract (<userinput>-</userinput>), multiply (<userinput>*</userinput>), divide (<userinput>/</userinput>) and the brackets <userinput>(</userinput> and <userinput>)</userinput>.</para>
|
||||
<para>For a complete explanation and more examples see the <link linkend="math">math</link> section.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="question">
|
||||
<title>Questions</title>
|
||||
<para>We can ask simple questions on which the answer will be 'true' or 'false'.</para>
|
||||
<para>Using questions is extensively explained in the <link linkend="questions">questions</link> section.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="questions-glue">
|
||||
<title>Question Glue-Words</title>
|
||||
<para>Questions can be glued together with so called 'question glue'. The glue words are <userinput>and</userinput>, <userinput>or</userinput>, and a special glue-word: <userinput>not</userinput>.</para>
|
||||
<para>Using question-glue is explained in the <link linkend="question-glue">Question Glue</link> section.</para>
|
||||
</sect2>
|
||||
|
||||
|
||||
<sect2 id="comment">
|
||||
<title>Comments</title>
|
||||
<para>Comments are lines that start with a <userinput>#</userinput>. For example:
|
||||
<screen>
|
||||
# this is a comment!
|
||||
print "this is not a comment"
|
||||
# the previous line is not a comment, but the next line is:
|
||||
# print "this is not a comment"
|
||||
</screen>
|
||||
We can add comments to the code for ourselves or for someone else to read. Comments are used for: (1) adding a small description to the program, (2) explaining how a piece of code works if it is a bit cryptic, and (3) to 'comment-out' lines of code that should be (temporarily) ignored (see the last line of the example).</para>
|
||||
<para>Commented lines are <glossterm>highlighted</glossterm> with dark yellow in the <link linkend="the-code-editor">code editor</link>.</para>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="commands">
|
||||
<title>Commands</title>
|
||||
<para>Using commands you tell the turtle or &kturtle; to do something. Some commands need input, some give output. In this section we explain all the commands that can be used in &kturtle;. Please note that all build in commands we discuss here are <glossterm>highlighted</glossterm> with dark green in the <link linkend="the-code-editor">code editor</link>, this can help you to distinguish them.</para>
|
||||
|
||||
<sect2 id="moving-the-turtle">
|
||||
<title>Moving the turtle</title>
|
||||
<para>There are several commands to move the turtle over the screen.</para>
|
||||
|
||||
<sect3 id="forward">
|
||||
<title>forward (fw)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>forward</term>
|
||||
<listitem><para><screen>forward X</screen>
|
||||
<userinput>forward</userinput> moves the turtle forward by the amount of X pixels. When the pen is down the turtle will leave a trail. <userinput>forward</userinput> can be abbreviated to <userinput>fw</userinput></para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="backward">
|
||||
<title>backward (bw)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>backward</term>
|
||||
<listitem><para><screen>backward X</screen>
|
||||
<userinput>backward</userinput> moves the turtle backward by the amount of X pixels. When the pen is down the turtle will leave a trail. <userinput>backward</userinput> can be abbreviated to <userinput>bw</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="turnleft">
|
||||
<title>turnleft (tl)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>turnleft</term>
|
||||
<listitem><para><screen>turnleft X</screen>
|
||||
<userinput>turnleft</userinput> commands the turtle to turn an amount of X degrees to the left. <userinput>turnleft</userinput> can be abbreviated to <userinput>tl</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="turnright">
|
||||
<title>turnright (tr)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>turnright</term>
|
||||
<listitem><para><screen>turnright X</screen>
|
||||
<userinput>turnright</userinput>the turtle to turn an amount of X degrees to the right. <userinput>turnright</userinput> can be abbreviated to <userinput>tr</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="direction">
|
||||
<title>direction (dir)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>direction</term>
|
||||
<listitem><para><screen>direction X</screen>
|
||||
<userinput>direction</userinput> set the turtle's direction to an amount of X degrees counting from zero, and thus is not relative to the turtle's previous direction. <userinput>direction</userinput> can be abbreviated to <userinput>dir</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="center">
|
||||
<title>center</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>center</term>
|
||||
<listitem><para><screen>center</screen>
|
||||
<userinput>center</userinput> moves the turtle to the center on the canvas.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="go">
|
||||
<title>go</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>go</term>
|
||||
<listitem><para><screen>go X,Y</screen>
|
||||
<userinput>go</userinput> commands the turtle to go to a certain place on the canvas. This place is X <glossterm linkend="pixels">pixels</glossterm> from the left of the canvas, and Y <glossterm linkend="pixels">pixels</glossterm> form the top of the canvas. Note that using the <userinput>go</userinput> command the turtle will not draw a line.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="gox">
|
||||
<title>gox</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>gox</term>
|
||||
<listitem><para><screen>gox X</screen>
|
||||
<userinput>gox</userinput> using this command the turtle will move to X <glossterm linkend="pixels">pixels</glossterm> from the left of the canvas whilst staying at the same height.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="goy">
|
||||
<title>goy</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>goy</term>
|
||||
<listitem><para><screen>goy Y</screen>
|
||||
<userinput>gox</userinput> using this command the turtle will move to Y <glossterm linkend="pixels">pixels</glossterm> from the top of the canvas whilst staying at the same distance from the left border of the canvas.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="pen">
|
||||
<title>The turtle has a pen</title>
|
||||
<para>The turtle has a pen that draws a line when the turtle moves. There are a few commands to control the pen. In this section we explain these commands.</para>
|
||||
<sect3 id="penup">
|
||||
<title>penup (pu)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>penup</term>
|
||||
<listitem><para><screen>penup</screen>
|
||||
<userinput>penup</userinput> lifts the pen from the canvas. When the pen is <quote>up</quote> no line will be drawn when the turtle moves. See also <userinput>pendown</userinput>. <userinput>penup</userinput> can be abbreviated to <userinput>pu</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="pendown">
|
||||
<title>pendown (pd)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>pendown</term>
|
||||
<listitem><para><screen>pendown</screen>
|
||||
<userinput>pendown</userinput> presses the pen down on the canvas. When the pen is press <quote>down</quote> on the canvas a line will be drawn when the turtle moves. See also <userinput>penup</userinput>. <userinput>pendown</userinput> can be abbreviated to <userinput>pd</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="setpenwidth">
|
||||
<title>penwidth (pw)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>penwidth</term>
|
||||
<listitem><para><screen>penwidth X</screen>
|
||||
<userinput>penwidth</userinput> sets the width of the pen (the line width) to an amount of X <glossterm linkend="pixels">pixels</glossterm>. <userinput>penwidth</userinput> can be abbreviated to <userinput>pw</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="setfgcolor">
|
||||
<title>pencolor (pc)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>pencolor</term>
|
||||
<listitem><para><screen>pencolor R,G,B</screen>
|
||||
<userinput>pencolor</userinput> sets the color of the pen. <userinput>pencolor</userinput> takes an <glossterm linkend="rgb">RGB combination</glossterm> as input. <userinput>pencolor</userinput> can be abbreviated to <userinput>pc</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="canvas">
|
||||
<title>Commands to control the canvas</title>
|
||||
<para>There are several commands to control the canvas.</para>
|
||||
<sect3 id="resizecanvas">
|
||||
<title>canvassize (cs)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>canvassize</term>
|
||||
<listitem><para><screen>canvassize X,Y</screen>
|
||||
With the <userinput>canvassize</userinput> command you can set the size of the canvas. It takes X and Y as input, where X is the new canvas width in <glossterm linkend="pixels">pixels</glossterm>, and Y is the new height of the canvas in <glossterm linkend="pixels">pixels</glossterm>. <userinput>canvassize</userinput> can be abbreviated to <userinput>cs</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="setbgcolor">
|
||||
<title>canvascolor (cc)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>canvascolor</term>
|
||||
<listitem><para><screen>canvascolor R,G,B</screen>
|
||||
<userinput>canvascolor</userinput> set the color of the canvas. <userinput>canvascolor</userinput> takes an <glossterm linkend="rgb">RGB combination</glossterm> as input. <userinput>canvascolor</userinput> can be abbreviated to <userinput>cc</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="wrapon">
|
||||
<title>wrapon</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>wrapon</term>
|
||||
<listitem><para><screen>wrapon</screen>
|
||||
With the <userinput>wrapon</userinput> command you can set <glossterm linkend="wrapping">wrapping</glossterm> <quote>on</quote> for the canvas. Please see the glossary if you want to know what <glossterm linkend="wrapping">wrapping</glossterm> is.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="wrapoff">
|
||||
<title>wrapoff</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>wrapoff</term>
|
||||
<listitem><para><screen>wrapoff</screen>
|
||||
With the <userinput>wrapoff</userinput> command you can set <glossterm linkend="wrapping">wrapping</glossterm> <quote>off</quote> for the canvas: this means the turtle can move off the canvas and can get <quote>lost</quote>. Please see the glossary if you want to know what <glossterm linkend="wrapping">wrapping</glossterm> is.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="clean">
|
||||
<title>Commands to clean up</title>
|
||||
<para>There are two commands to clean up the canvas after you have made a mess.</para>
|
||||
<sect3 id="clear">
|
||||
<title>clear (cr)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>clear</term>
|
||||
<listitem><para><screen>clear</screen>
|
||||
With <userinput>clear</userinput> you can clean all drawings from the canvas. All other things remain: the position and angle of the turtle, the canvascolor, the visibility of the turtle, and the canvas size. <userinput>clear</userinput> can be abbreviated to <userinput>cr</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="reset">
|
||||
<title>reset</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>reset</term>
|
||||
<listitem><para><screen>reset</screen>
|
||||
<userinput>reset</userinput> cleans much more thoroughly than the <userinput>clear</userinput> command. After a <userinput>reset</userinput> command everything is like is was when you had just started &kturtle;. The turtle is positioned at the middle of the screen, the canvas color is white, and the turtle draws a black line on the canvas.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="sprites">
|
||||
<title>The turtle is a sprite</title>
|
||||
<para>First a brief explanation of what sprites are: sprites are small pictures that can be moved around the screen, like we often see in computer games. Our turtle is also a sprite. For more info see the glossary on <glossterm linkend="sprites">sprites</glossterm>. </para>
|
||||
<para>Next you will find a full overview on all commands to work with sprites.</para>
|
||||
<para>[The current version of &kturtle; does not yet support the use of sprites other than the turtle. With future versions you will be able to change the turtle into something of your own design]</para>
|
||||
<sect3 id="spriteshow">
|
||||
<title>show</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>show (ss)</term>
|
||||
<listitem><para><screen>show</screen>
|
||||
<userinput>show</userinput> makes the turtle visible again after it has been hidden. <userinput>show</userinput> can be abbreviated to <userinput>ss</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="spritehide">
|
||||
<title>hide (sh)</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>hide</term>
|
||||
<listitem><para><screen>hide</screen>
|
||||
<userinput>hide</userinput> hides the turtle. This can be used if the turtle does not fit in your drawing. <userinput>hide</userinput> can be abbreviated to <userinput>sh</userinput>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="writing">
|
||||
<title>Can the turtles write?</title>
|
||||
<para>The answer is: <quote>yes</quote>. The turtle can write: it writes just about everything you command it to.</para>
|
||||
<sect3 id="print">
|
||||
<title>print</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>print</term>
|
||||
<listitem><para><screen>print X</screen>
|
||||
The <userinput>print</userinput> command is used to command the turtle to write something on the canvas. <userinput>print</userinput> takes numbers and strings as input. You can <userinput>print</userinput> various numbers and strings using the <quote>+</quote> symbol. See here a small example:
|
||||
<screen>
|
||||
year = 2003
|
||||
author = "Cies"
|
||||
print author + " started the KTurtle project in " + year + " and still enjoys working on it!"
|
||||
</screen>
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="fontsize">
|
||||
<title>fontsize</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>fontsize</term>
|
||||
<listitem><para><screen>fontsize X</screen>
|
||||
<userinput>fontsize</userinput> sets the size of the font that is used by <userinput>print</userinput>. <userinput>fontsize</userinput> takes one input which should be a number. The size is set in <glossterm linkend="pixels">pixels</glossterm>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="random">
|
||||
<title>A command that rolls dice for you</title>
|
||||
<para>There is one command that rolls dice for you, it is called <userinput>random</userinput>, and it is very useful for some unexpected results.</para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>random</term>
|
||||
<listitem><para><screen>random X,Y</screen>
|
||||
<userinput>random</userinput> is a command that takes input and gives output. As input are required two numbers, the first (X) sets the minimum output, the second (Y) sets the maximum. The output is a randomly chosen number that is equal or greater then the minimum and equal or smaller than the maximum. Here a small example:
|
||||
<screen>
|
||||
repeat 500 [
|
||||
x = random 1,20
|
||||
forward x
|
||||
turnleft 10 - x
|
||||
]
|
||||
</screen>
|
||||
Using the <userinput>random</userinput> command you can add a bit of chaos to your program.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="dialogs">
|
||||
<title>Input and feedback though dialogs</title>
|
||||
<para>A dialog is a small pop-up window that provides some feedback or asks for some input. &kturtle; has two commands for dialogs, namely: <userinput>message</userinput> and <userinput>inputwindow</userinput></para>
|
||||
<sect3 id="message">
|
||||
<title>message</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>message</term>
|
||||
<listitem><para><screen>message X</screen>
|
||||
The <userinput>message</userinput> command takes a <link linkend="string">string</link> as input. It shows a pop-up dialog containing the text from the <link linkend="string">string</link>.
|
||||
<screen>
|
||||
year = 2003
|
||||
author = "Cies"
|
||||
print author + " started the KTurtle project in " + year + " and still enjoys working on it!"
|
||||
</screen>
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="inputwindow">
|
||||
<title>inputwindow</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>inputwindow</term>
|
||||
<listitem><para><screen>inputwindow X</screen>
|
||||
<userinput>inputwindow</userinput> takes a <link linkend="string">string</link> as input. It shows a pop-up dialog containing the text from the string, just like the <link linkend="message">message</link>. But in addition to it also puts an input field on the dialog. Through this input filed the user can enter a <link linkend="number">number</link> or a <link linkend="string">string</link> which can be stored in a <link linkend="containers">container</link>. For example
|
||||
<screen>
|
||||
in = inputwindow "What is you age?"
|
||||
out = 2003 - in
|
||||
print "In 2003 you where " + out + " years old at some point."
|
||||
</screen>
|
||||
When a user cancels the input dialog, or does not enter anything at all the <link linkend="containers">container</link> is emptied.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
|
||||
<sect1 id="containers">
|
||||
<title>Containers</title>
|
||||
<para>Containers are letters or words that can be used by the programmer to store a number or a text. Containers that contain a number are called <link linkend="variables">variables</link>, containers that can contain text are called <link linkend="string">string</link>.</para>
|
||||
|
||||
<para>Containers that are not used contain nothing. An example:
|
||||
<screen>
|
||||
print N
|
||||
</screen>
|
||||
This will print nothing. If we try to do <link linkend="math">math</link> with empty containers we will get errors.
|
||||
</para>
|
||||
|
||||
<sect2 id="variables">
|
||||
<title>Variables: number containers</title>
|
||||
<para>Let us start with an example:
|
||||
<screen>
|
||||
x = 3
|
||||
print x
|
||||
</screen>
|
||||
In the first line the letter <userinput>x</userinput> made into a variable (number container). As you see the value of the variable <userinput>x</userinput> is set to 3. On the second line the value is printed.</para>
|
||||
<para> Note that if we wanted to print an <quote>x</quote> that we should have written
|
||||
<screen>
|
||||
print "x"
|
||||
</screen>
|
||||
</para>
|
||||
<para>That was easy, now a bit harder example:
|
||||
<screen>
|
||||
A = 2004
|
||||
B = 25
|
||||
C = A + B
|
||||
|
||||
# the next command prints "2029"
|
||||
print C
|
||||
backward 30
|
||||
# the next command prints "2004 plus 25"
|
||||
print A + " plus " + B
|
||||
backward 30
|
||||
# the next command prints "1979"
|
||||
print A - B
|
||||
</screen>
|
||||
In the first two lines the variables <userinput>A</userinput> and <userinput>B</userinput> are set to 2004 and 25. On the third line the variable <userinput>C</userinput> is set to <userinput>A + B</userinput>, which is 2029. The rest of the example consists of 3 <userinput>print</userinput> commands with <userinput>backward 30</userinput> in between. The <userinput>backward 30</userinput> is there to make sure every output is on a new line. In this example you also see that variables can be used in <link linkend="math">mathematical calculations</link>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="strings">
|
||||
<title>Containers that contain text (strings)</title>
|
||||
<para>In programming code the regular text is usually started and ended with quotes. As we have already seen:
|
||||
<screen>
|
||||
print "Hello programmer!"
|
||||
</screen>
|
||||
The regular is delimited with quotes. These pieces of regular text we call <link linkend="strings">strings</link>.</para>
|
||||
<para>Strings can also be stored in <link linkend="containers">containers</link> just like <link linkend="number">numbers</link>
|
||||
Strings are a lot like variables. The biggest difference is that they contain text in stead of numbers. For this reason strings cannot be used in <link linkend="math">mathematical calculations</link> and <link linkend="questions">questions</link>. An example of the use of strings:
|
||||
<screen>
|
||||
x = "Hello "
|
||||
name = inputwindow "Please enter your name..."
|
||||
print x + name + ", how are you?"
|
||||
</screen>
|
||||
On the first line the string <userinput>x</userinput> is set to <quote>Hello </quote>. On the second line the string <userinput>name</userinput> is set to the output of the <userinput>inputwindow</userinput> command. On the third line the program prints a composition of three strings on the canvas.</para>
|
||||
<para>This program ask you to enter your name. When you, for instance, enter the name <quote>Paul</quote>, the program prints <quote>Hello Paul, how are you?</quote>. Please note that the plus (+) is the only math symbol that you can use with strings.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="math">
|
||||
<title>Can the Turtle do math?</title>
|
||||
<para>Yes, &kturtle; will do your math. You can add (+), substract (-), multiply (*), and divide (/). Here is an example in which we use all of them:
|
||||
<screen>
|
||||
a = 20 - 5
|
||||
b = 15 * 2
|
||||
c = 30 / 30
|
||||
d = 1 + 1
|
||||
print "a: "+a+", b: "+b+", c: "+c+", d: "+d
|
||||
</screen>
|
||||
Do you know what value a, b, c and d have? Please note the use of the <link linkend="assignment">assignment</link> symbol <userinput>=</userinput>.</para>
|
||||
<para>If you just want a simple calculation to be done you can do something like this:
|
||||
<screen>
|
||||
print 2004-12
|
||||
</screen></para>
|
||||
<para>Now an example with parentheses:
|
||||
<screen>
|
||||
print ( ( 20 - 5 ) * 2 / 30 ) + 1
|
||||
</screen>
|
||||
The expressions inside parentheses will be calculated first. In this example, 20-5 will be calculated, then multiplied by 2, divided by 30, and then 1 is added (giving 2).</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="questions">
|
||||
<title>Asking questions, getting answers...</title>
|
||||
<para><link linkend="if"><userinput>if</userinput></link> and <link linkend="while"><userinput>while</userinput></link> are <link linkend="controlling-execution">execution controllers</link> that we will discuss in the next section. In this section we use the <link linkend="if"><userinput>if</userinput></link> command to explain questions.</para>
|
||||
<sect2 id="q">
|
||||
<title>Questions</title>
|
||||
<para>A simple example of a question:
|
||||
<screen>
|
||||
x = 6
|
||||
if x > 5 [
|
||||
print "hello"
|
||||
]
|
||||
</screen>
|
||||
|
||||
In this example the question is the <userinput>x > 5</userinput> part. If the answer to this question is 'true' the code between the brackets will be executed. Questions are an important part of programming and often used together with <link linkend="controlling-execution">execution controllers</link>, like <link linkend="if"><userinput>if</userinput></link>. All numbers and <link linkend="variables">variables</link> (number containers) can be compared to each other with questions.</para>
|
||||
<para>
|
||||
Here are all possible questions:
|
||||
<table>
|
||||
<title>Types of questions</title>
|
||||
<tgroup cols="3">
|
||||
<tbody>
|
||||
<row>
|
||||
<entry><userinput>a == b</userinput></entry>
|
||||
<entry>equals</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> equals <userinput>b</userinput></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>a != b</userinput></entry>
|
||||
<entry>not-equal</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> does not equal <userinput>b</userinput></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>a > b</userinput></entry>
|
||||
<entry>greater than</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> is greater than <userinput>b</userinput></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>a < b</userinput></entry>
|
||||
<entry>smaller than</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> is smaller than <userinput>b</userinput></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>a >= b</userinput></entry>
|
||||
<entry>greater than or equals</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> is greater than or equals <userinput>b</userinput></entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>a <= b</userinput></entry>
|
||||
<entry>smaller than or equals</entry>
|
||||
<entry>answer is <quote>true</quote> if <userinput>a</userinput> is smaller than or equals <userinput>b</userinput></entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
<para>Questions are <glossterm>highlighted</glossterm> with light blue in the <link linkend="the-code-editor">code editor</link>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="question-glue">
|
||||
<title>Question Glue</title>
|
||||
<para>
|
||||
Question glue-words enable us to glue questions into one big question.
|
||||
<screen>
|
||||
a = 1
|
||||
b = 5
|
||||
if (a < 5) and (b == 5) [
|
||||
print "hello"
|
||||
]
|
||||
</screen>
|
||||
In this example the glue-word <userinput>and</userinput> is used to glue 2 questions (<userinput>a < 5</userinput>, <userinput>b == 5</userinput>) together. If one side of the <userinput>and</userinput> would answer <quote>false</quote> the whole question would answer <quote>false</quote>, because with the glue-word <userinput>and</userinput> both sides need to be <quote>true</quote> in order to answer <quote>true</quote>. Please do not forget to use the brackets around the questions!</para>
|
||||
|
||||
<para>
|
||||
Here is a schematic overview; a more detailed explanation follows below:
|
||||
<table>
|
||||
<title>Question glue-words</title>
|
||||
<tgroup cols="2">
|
||||
<tbody>
|
||||
<row>
|
||||
<entry><userinput>and</userinput></entry>
|
||||
<entry>Both sides need to be 'true' in order to answer 'true'</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>or</userinput></entry>
|
||||
<entry>If one of the sides is 'true' the answer is 'true'</entry>
|
||||
</row>
|
||||
<row>
|
||||
<entry><userinput>not</userinput></entry>
|
||||
<entry>Special case: only works on one question! Changes 'true' into 'false' and 'false' into 'true'.</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</table>
|
||||
</para>
|
||||
<para>Question glue-words are <glossterm>highlighted</glossterm> with purple in the <link linkend="the-code-editor">code editor</link>.</para>
|
||||
|
||||
<sect3 id="and">
|
||||
<title>and</title>
|
||||
<para>When two questions are glued together with <userinput>and</userinput>, both sides of the <userinput>and</userinput> have to be 'true' in order to result in 'true'. An example:
|
||||
<screen>
|
||||
a = 1
|
||||
b = 5
|
||||
if ((a < 10) and (b == 5)) and (a < b) [
|
||||
print "hello"
|
||||
]
|
||||
</screen>
|
||||
In this example you see a glued question glued onto an other question.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="or">
|
||||
<title>or</title>
|
||||
<para>If one of the two questions that are glued together with <userinput>or</userinput> is 'true' the result will be 'true'. An example:
|
||||
<screen>
|
||||
a = 1
|
||||
b = 5
|
||||
if ((a < 10) or (b == 10)) or (a == 0) [
|
||||
print "hello"
|
||||
]
|
||||
</screen>
|
||||
In this example you see a glued question glued onto an other question.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="not">
|
||||
<title>not</title>
|
||||
<para><userinput>not</userinput> is a special question glue-word because it only works for one question at the time. <userinput>not</userinput> changes 'true' into 'false' and 'false' into 'true'. An example:
|
||||
<screen>
|
||||
a = 1
|
||||
b = 5
|
||||
if not ((a < 10) and (b == 5)) [
|
||||
print "hello"
|
||||
]
|
||||
else
|
||||
[
|
||||
print "not hello ;-)"
|
||||
]
|
||||
</screen>
|
||||
In this example the glued question is 'true' yet the <userinput>not</userinput> changes it to 'false'. So in the end <userinput>"not hello ;-)"</userinput> is printed on the <link linkend="the-canvas">canvas</link>.</para>
|
||||
</sect3>
|
||||
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="controlling-execution">
|
||||
<title>Controlling execution</title>
|
||||
<para>The execution controllers enable you — as their name implies — to control execution.</para>
|
||||
<para>Execution controlling commands are <glossterm>highlighted</glossterm> with dark green in a bold font type. The square brackets are mostly used together with execution controllers and they are <glossterm>highlighted</glossterm> with light green.</para>
|
||||
|
||||
<sect2 id="wait">
|
||||
<title>Have the turtle wait</title>
|
||||
<para>If you have done some programming in &kturtle; you have might noticed that the turtle can be very quick at drawing. This command makes the turtle wait for a given amount of time.</para>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>wait</term>
|
||||
<listitem><para><screen>wait X</screen>
|
||||
<userinput>wait</userinput> makes the turtle wait for X seconds.
|
||||
<screen>
|
||||
repeat 36 [
|
||||
forward 5
|
||||
turnright 10
|
||||
wait 0.5
|
||||
]
|
||||
</screen>
|
||||
This code draws a circle, but the turtle will wait half a second
|
||||
after each step. This gives the impression of a slow-moving turtle.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="if">
|
||||
<title>Execute "if"</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>if</term>
|
||||
<listitem><para><screen>if <link linkend="questions">question</link> [ ... ]</screen>
|
||||
The code that is placed between the brackets will only be executed <userinput>if</userinput> the answer to the <link linkend="questions">question</link> is <quote>true</quote>. Please read for more information on <link linkend="questions">questions</link> in the <link linkend="questions">question section</link>.
|
||||
<screen>
|
||||
x = 6
|
||||
if x > 5 [
|
||||
print "x is greater than five!"
|
||||
]
|
||||
</screen>
|
||||
On the first line <userinput>x</userinput> is set to 6. On the second line the <link linkend="questions">question</link> <userinput>x > 5</userinput> is asked. Since the answer to this question is <quote>true</quote> the execution controller <userinput>if</userinput> will allow the code between the brackets to be executed</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="while">
|
||||
<title>The "while" loop</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>while</term>
|
||||
<listitem><para><screen>while <link linkend="questions">question</link> [ ... ]</screen>
|
||||
The execution controller <userinput>while</userinput> is a lot like <link linkend="if"><userinput>if</userinput></link>. The difference is that <userinput>while</userinput> keeps repeating (looping) the code between the brackets until the answer to the <link linkend="questions">question</link> is <quote>false</quote>.
|
||||
<screen>
|
||||
x = 1
|
||||
while x < 5 [
|
||||
forward 10
|
||||
wait 1
|
||||
x = x + 1
|
||||
]
|
||||
</screen>
|
||||
On the first line <userinput>x</userinput> is set to 1. On the second line the <link linkend="questions">question</link> <userinput>x < 5</userinput> is asked. Since the answer to this question is <quote>true</quote> the execution controller <userinput>while</userinput> starts executing the code between the brackets until the answer to the <link linkend="questions">question</link> is <quote>false</quote>. In this case the code between the brackets will be executed 4 times, because every time the fifth line is executed <userinput>x</userinput> increases by 1.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="else">
|
||||
<title>If not, in other words: "else"</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>else</term>
|
||||
<listitem><para><screen>if question [ ... ] else [ ... ]</screen>
|
||||
<userinput>else</userinput> can be used in addition to the execution controller <link linkend="if"><userinput>if</userinput></link>. The code between the brackets after <userinput>else</userinput> is only executed if the answer to the <link linkend="questions">question</link> that is asked is <quote>false</quote>.
|
||||
<screen>
|
||||
reset
|
||||
x = 4
|
||||
if x > 5 [
|
||||
print "x is greater than five!"
|
||||
]
|
||||
else
|
||||
[
|
||||
print "x is smaller than six!"
|
||||
]
|
||||
</screen>
|
||||
The <link linkend="questions">question</link> asks if <userinput>x</userinput> is greater than 5. Since <userinput>x</userinput> is set to 4 on the first line the answer to the question is <quote>false</quote>. This means the code between the brackets after <userinput>else</userinput> gets executed.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="for">
|
||||
<title>The "for" loop, a counting loop</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>for</term>
|
||||
<listitem><para><screen>for <userinput>start point</userinput> to <userinput>end point</userinput> [ ... ]</screen>
|
||||
The <userinput>for</userinput> loop is a <quote>counting loop</quote>, &ie; it keeps count for you.
|
||||
<screen>
|
||||
for x = 1 to 10 [
|
||||
print x * 7
|
||||
forward 15
|
||||
]
|
||||
</screen>
|
||||
Every time the code between the brackets is executed the <userinput>x</userinput> is increased by 1, until <userinput>x</userinput> reaches the value of 10. The code between the brackets prints the <userinput>x</userinput> multiplied by 7. After this program finishes its execution you will see the times table of 7 on the canvas.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
|
||||
<sect1 id="learn">
|
||||
<title>Create your own commands with <quote>learn</quote></title>
|
||||
<para><userinput>learn</userinput> is a very special command, because it is used to create your own commands. The command you create can take <glossterm linkend="input-output">input</glossterm> and return <glossterm linkend="input-output">output</glossterm>. Let us take a look at how a new command is created:
|
||||
<screen>
|
||||
learn circle x [
|
||||
repeat 36 [
|
||||
forward x
|
||||
turnleft 10
|
||||
]
|
||||
]
|
||||
</screen>
|
||||
The new command is called <userinput>circle</userinput>. <userinput>circle</userinput> takes one <glossterm linkend="input-output">input</glossterm>, a number, to set the size of the circle. <userinput>circle</userinput> returns no <glossterm linkend="input-output">output</glossterm>. The <userinput>circle</userinput> command can now be used like a normal command in the rest of the code. See this example:
|
||||
<screen>
|
||||
learn circle X [
|
||||
repeat 36 [
|
||||
forward X
|
||||
turnleft 10
|
||||
]
|
||||
]
|
||||
|
||||
go 30,30
|
||||
circle 20
|
||||
|
||||
go 40,40
|
||||
circle 50
|
||||
</screen>
|
||||
</para>
|
||||
<para>In the next example, a command with a return value is created.
|
||||
<screen>
|
||||
reset
|
||||
|
||||
learn multiplyBySelf n [
|
||||
r = n * 1
|
||||
r = n * n
|
||||
return r
|
||||
]
|
||||
i = inputwindow "Please enter a number and press OK"
|
||||
print i + " multiplied by itself is: " + multiplyBySelf i
|
||||
</screen>
|
||||
In this example a new command called <userinput>multiplyBySelf</userinput> is created. The input of this command is multiplied by itself and then returned, using the <anchor id="return" /><userinput>return</userinput> command. The <userinput>return</userinput> command is the way to output a value from a function you have created.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,128 @@
|
||||
<chapter id="translators">
|
||||
<title>Translator's Guide to &kturtle;</title>
|
||||
<para>As you probably already know, the unique feature of the &logo; programming language is that the &logo; commands are often translated to language of the programmer. This takes away a barrier for some learners to understand the basics of programming.
|
||||
When translating &kturtle; to a new language some more files have to be translated in addition to the usual strings and documentation. Yet most it is autogenerated by Rafael Beccar's scripts. These scripts can be found in <userinput>kdeedu/kturtle/scripts</userinput>, the files that needs translation can be found in <userinput>kdeedu/kturtle/data</userinput>, in those directories you also find README files which contains instructions for using/translating them.
|
||||
</para>
|
||||
<para>
|
||||
|
||||
</para>
|
||||
<sect1 id="make_directory">
|
||||
<title>Creating a Directory to hold the Translated Files</title>
|
||||
<para>
|
||||
First, you need to create a directory to store the translated files.
|
||||
|
||||
Create a directory called
|
||||
|
||||
<filename class="directory">kde-i18n/<replaceable>code</replaceable>/data/kdeedu/kturtle/</filename>
|
||||
|
||||
in your KDE CVS directory, where <replaceable>code</replaceable> is your country code (the 2- or 4- letter <acronym>ISO</acronym> code).
|
||||
</para>
|
||||
<para>
|
||||
Copy the <filename>Makefile.am</filename> file from <filename class="directory">kdeedu/kturtle/data/</filename> into this directory. Open it using your favorite text editor, replace all instances of <quote>en_US</quote> in the file with your country code (the one used above), and save the file.
|
||||
</para>
|
||||
</sect1>
|
||||
<sect1 id="commands_trans">
|
||||
<title>How To Translate the &logo; Keywords (commands)</title>
|
||||
<para>
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
Copy the <filename>logokeywords.en_US.xml</filename> file from <filename class="directory">kdeedu/kturtle/data/</filename> to the directory you have just created, and rename it to <filename>logokeywords.<replaceable>code</replaceable>.xml</filename>
|
||||
where <replaceable>code</replaceable> is your country code (the 2- or 4- letter <acronym>ISO</acronym> code).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>Translate the contents of the <sgmltag class="starttag">keyword</sgmltag> tag (&ie;
|
||||
the information between <sgmltag class="starttag">keyword</sgmltag>
|
||||
and <sgmltag class="endtag">keyword</sgmltag>) into your own language
|
||||
wherever possible. Also, translate the contents of the <sgmltag class="starttag">alias</sgmltag> tag, (&ie; the information between the <sgmltag class="starttag">alias</sgmltag> and <sgmltag class="endtag">alias</sgmltag>): these are used as shortcuts for the keyword.</para>
|
||||
<para>
|
||||
For example, translate <quote>while</quote> in: <sgmltag class="starttag">keyword</sgmltag>while<sgmltag class="endtag">keyword</sgmltag>
|
||||
</para>
|
||||
<para>
|
||||
Please do not translate anything else and do not translate the English words in <sgmltag class="starttag">command name="english_word"</sgmltag>: these must stay in English.
|
||||
</para>
|
||||
<para>
|
||||
Last bit: do not change the order of this file, this is needed for Rafael Beccar's automatic translation generation scripts.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>Save your file as <acronym>UTF-8</acronym> (in &kate;, use <guimenuitem>Save As...</guimenuitem> and change to <guilabel>utf8</guilabel> in the box on the right of the file name).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>Commit your file (add your filename in the <filename>Makefile.am</filename>) or send it to Anne-Marie.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>In case of any doubt, please contact Anne-Marie Mahfouf <email>annemarie.mahfouf@free.fr</email> for more information.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="examples_syntax">
|
||||
<title>How To Translate the Syntax Highlighting Files</title>
|
||||
<para>
|
||||
Translating the <filename>logohighlightstyle.en_US.xml</filename> is a breeze when using Rafael Beccar's script in <filename class="directory">kdeedu/kturtle/data/</filename>. Please make sure to read the README file in that directory.
|
||||
</para>
|
||||
<para>
|
||||
For backward compatibility with all people who do not want to the perl scripted blessing mentioned in the previous paragraph, here the old fashioned way of doing it:
|
||||
<itemizedlist>
|
||||
<listitem><para>Copy the <filename>logohighlightstyle.en_US.xml</filename> file from <filename class="directory">kdeedu/kturtle/data/</filename> to the directory you created to store the translated keywords file, and rename it to <filename>logohighlightstyle.<replaceable>code</replaceable>.xml</filename>
|
||||
where <replaceable>code</replaceable> is your country code (the 2- or 4- letter <acronym>ISO</acronym> code).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem><para>In line 4 of the file, there is
|
||||
<sgmltag class="starttag">language name="en_US"</sgmltag>...: here you change <quote>en_US</quote> to your language's <acronym>ISO</acronym> code (2 or 4 letters).
|
||||
</para></listitem>
|
||||
<listitem><para>Translate into your own language the content of the <sgmltag class="starttag">item</sgmltag> tag (&ie; the information between <sgmltag class="starttag">item</sgmltag> and <sgmltag class="endtag">item</sgmltag>). This content must match the <filename>logokeyword</filename> file.
|
||||
For example, translate <quote>while</quote> in: <sgmltag class="starttag">item</sgmltag> while <sgmltag class="endtag">item</sgmltag> and leave the spaces as they are (one at the beginning and one at the end).
|
||||
Please do not translate anything else.
|
||||
</para></listitem>
|
||||
<listitem><para>Save your file as <acronym>UTF-8</acronym> (in &kate;, use <guimenuitem>Save As...</guimenuitem> and change to <guilabel>utf8</guilabel> in the box on the right of the file name).
|
||||
</para></listitem>
|
||||
<listitem><para>Commit your file (add your filename in the <filename>Makefile.am</filename>) or send it to Anne-Marie.
|
||||
</para></listitem>
|
||||
<listitem><para>In case of any doubt, please contact Anne-Marie Mahfouf <email>annemarie.mahfouf@free.fr</email> for more information.
|
||||
</para></listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="examples_trans">
|
||||
<title>How To Translate the Examples</title>
|
||||
<para>
|
||||
Again this task is simplified a lot by Rafael Beccar's script in <filename class="directory">kdeedu/kturtle/data/</filename>. Please make sure to read the README file in that directory, since some work still has to be done after the example logo files are autotranslated.
|
||||
</para>
|
||||
<para>
|
||||
When you followed the instructions, given in the README file that you found in the scripts directory, you should now be almost ready. Please do not forget to test the translated example logo code you created, since it is very common that an error sneaks in. Also make sure the <userinput>Makefile.am</userinput> in <filename class="directory">kde-i18n/<replaceable>code</replaceable>/data/kdeedu/kturtle/</filename> is updated according to the new files. For the Dutch the <userinput>Makefile.am</userinput> should look like this:
|
||||
<screen>
|
||||
txt_DATA = advertentie.logo driehoeken.logo krullen.logo tafels.logo \
|
||||
bloem.logo driehoek.logo logohighlightstyle.nl.xml pijl.logo vierkanten.logo \
|
||||
kleuren.logo logokeywords.nl.xml randomnaam.logo vierkant.logo
|
||||
txtdir = $(kde_datadir)/kturtle/examples/nl
|
||||
|
||||
xml_DATA = logohighlightstyle.nl.xml
|
||||
xmldir = $(kde_datadir)/katepart/syntax
|
||||
|
||||
keywords_DATA = logokeywords.nl.xml
|
||||
keywordsdir = $(kde_datadir)/kturtle/data
|
||||
EXTRA_DIST = $(txt_DATA) $(xml_DATA) $(keywords_DATA)
|
||||
</screen>
|
||||
</para>
|
||||
<para>
|
||||
Here a description of how to do the translation WITHOUT the use of Rafael's perl scripts:
|
||||
<itemizedlist>
|
||||
<listitem><para>Copy the English example files from <filename class="directory">kdeedu/kturtle/data/</filename> to the directory used to store the translated keyword and hilighting files. Translate the filenames of the examples in your directory: this will allow users to easily and quickly understand what the example is about.</para>
|
||||
</listitem>
|
||||
<listitem><para>Translate the keywords in the examples, using those in the <filename>logokeywords.xml</filename> for your language. The keywords file file must be done, first, before translating the examples.</para>
|
||||
</listitem>
|
||||
<listitem><para>Save your file as <acronym>UTF-8</acronym> (in &kate;, use <guimenuitem>Save As...</guimenuitem> and change to <guilabel>utf8</guilabel> in the box on the right of the file name)</para>
|
||||
</listitem>
|
||||
<listitem><para>Commit your folder (add a <filename>Makefile.am</filename> inside) or send it to Anne-Marie.</para>
|
||||
</listitem>
|
||||
<listitem><para>In case of any doubt, please contact Anne-Marie Mahfouf, <email>annemarie.mahfouf@free.fr</email> for more information.</para>
|
||||
</listitem>
|
||||
<listitem><para>Finally, if you want, you can add your own examples in this folder.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
@ -0,0 +1,590 @@
|
||||
<!--Dear translator: please NEVER translate the id or anything inside the tags as they are needed in english by the application
|
||||
Thanks a lot in advance.-->
|
||||
<chapter id="using-kturtle">
|
||||
<title>Using &kturtle;</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here is a screenshot of &kturtle; in action</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="mainwindow_flower_nrs.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>&kturtle; Main Window</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>The main window of &kturtle; has two main parts: <link linkend="the-code-editor">the code editor</link> (3) on the left where you type the &logo; commands, and <link linkend="the-canvas">the canvas</link> (4) on the right where the instructions are visualized. <link linkend="the-canvas">The canvas</link> is the turtle's playground: it is on the canvas that the turtle actually moves and draws. The three other places on the main window are: <link linkend="the-menubar">the menu bar</link> (1) from where all the actions can be reached, <link linkend="the-toolbar">the toolbar</link> (2) that allows you to quickly select the most used actions, and <link linkend="the-statusbar">the statusbar</link> (5) where you will find feedback on the state of &kturtle;.</para>
|
||||
|
||||
<sect1 id="the-code-editor">
|
||||
<title>The Code Editor</title>
|
||||
<para>In the code editor you type the &logo; commands. It has all of the features you would expect from a modern editor. Most of its features are found in the <link linkend="the-edit-menu">Edit</link> and the <link linkend="the-tools-menu">Tools</link> menus. The code editor can be docked on each border of the main window or it can be detached and placed anywhere on your desktop.</para>
|
||||
<para>
|
||||
You have several ways to get some code in the editor. The easiest way is to use an already-made example: choose <menuchoice><guimenu>File</guimenu><guimenuitem>Open Examples</guimenuitem>
|
||||
</menuchoice> in the <link linkend="the-file-menu">File menu</link> and click on a file. The filename will tell you what the example is about (⪚ <filename>square.logo</filename> will draw a square). The file you choose will be opened in the <link linkend="the-code-editor">the code editor</link>, you can then use <menuchoice><guimenu>File</guimenu><guimenuitem>Execute Commands</guimenuitem>
|
||||
</menuchoice> to run the code if you like.</para>
|
||||
<para>You can open &logo; files by choosing <menuchoice><guimenu>File</guimenu><guimenuitem>Open...</guimenuitem>
|
||||
</menuchoice>.</para>
|
||||
<para>The third way is to directly type your own code in the editor or to copy/paste some code from this user guide.
|
||||
</para>
|
||||
<para>
|
||||
The cursor position is indicated in <link linkend="the-statusbar">the statusbar</link>, on the right with the Line number and Column number.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="the-canvas">
|
||||
<title>The Canvas</title>
|
||||
<para>
|
||||
The canvas is the area where the commands are visualized, where the commands <quote>draw</quote> a picture. In other words, it is the turtle's playground. After getting some code in the <link linkend="the-code-editor">the code editor</link>, and executing it using <menuchoice><guimenu>File</guimenu><guimenuitem>Execute Commands</guimenuitem>
|
||||
</menuchoice>, two things can happen: either the code executes fine, and will you most likely see something change on the canvas; or you have made an error in your code and there will be a message telling you what error you made.</para>
|
||||
<para>This message should help you to resolve the error.</para>
|
||||
<para>The picture that is drawn can be saved as an image (using <menuchoice><guimenu>File</guimenu><guimenuitem>Save Canvas</guimenuitem>
|
||||
</menuchoice>) or printed (using <menuchoice><guimenu>File</guimenu><guimenuitem>Print...</guimenuitem>
|
||||
</menuchoice>).</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="the-menubar">
|
||||
<title>The Menubar</title>
|
||||
<para>In the menubar you find all the actions of &kturtle;. They are in the following groups: <guimenu>File</guimenu>, <guimenu>Edit</guimenu>, <guimenu>View</guimenu>, <guimenu>Tools</guimenu>, <guimenu>Settings</guimenu>, and <guimenu>Help</guimenu>. This section describes them all.</para>
|
||||
|
||||
<sect2 id="the-file-menu">
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<sect3 id="file-new">
|
||||
<title>New</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>N</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Creates a new, empty &logo; file.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-open">
|
||||
<title>Open</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>O</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Opens a &logo; file.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-open-recent">
|
||||
<title>Open Recent</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Recent</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Opens a &logo; file that has been opened recently.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-open-examples">
|
||||
<title>Open Examples</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>E</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Examples</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Show the folder with examples &logo; programs. The examples should be in your favorite language that you can choose in <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kturtle;...</guimenuitem>
|
||||
</menuchoice>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-save">
|
||||
<title>Save</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>S</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Saves the currently opened &logo; file.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-save-as">
|
||||
<title>Save As</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save As...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Saves the currently opened &logo; file on a specified location.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-save-canvas">
|
||||
<title>Save Canvas</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save Canvas</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Saves the current drawing on canvas into an image.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-speed">
|
||||
<title>Execution Speed</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Execution Speed</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Present a list of possible execution speeds, consisting of: Full Speed, Slow, Slower and Slowest. When the execution speed is set to 'Full Speed' (default) we can barely keep up with what is happening. Sometimes this behavior is wanted, but sometimes we want to keep track of the execution. In the latter case you want to set the execution speed to 'Slow', 'Slower' or 'Slowest'. When one of the slow modes is selected the current position of the executor will be shown in the editor.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-execute">
|
||||
<title>Execute</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Alt;<keysym>Return</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Execute Commands</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Starts the execution of the commands in the code editor.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-pause">
|
||||
<title>Pause</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>Pause</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Pause Execution</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Pauses the execution. This action is only enabled when the commands are actually executing.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-stop">
|
||||
<title>Stop</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>Escape</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Stop Execution</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Stops the execution. This action is only enabled when the commands are actually executing.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-print">
|
||||
<title>Print</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>P</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Print...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Prints either the current code in the editor or the current drawing on the canvas.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
<sect3 id="file-quit">
|
||||
<title>Quit</title>
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Quits &kturtle;.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="the-edit-menu">
|
||||
<title>The <guimenu>Edit</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
<anchor id="edit-undo" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>Z</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Undo</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Undoes the last change to code. &kturtle; has unlimited undos.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-redo" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;&Shift;<keycap>Z</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Redo</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Redoes an undone change to the code.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-cut" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>X</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Cut</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Cuts the selected text from the code editor to the clipboard.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-copy" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>C</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Copy</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Copies the selected text from the code editor to the clipboard.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-paste" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>V</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Paste</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Pastes the text from the clipboard to the editor.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-find" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>F</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Find...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>With this action you can find phrases in the code.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-find-next" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>F3</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Find Next</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Use this to find the next occurrence of the phrase.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="edit-replace" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>R</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Replace...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>With this action you can replace phrases in the code.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="the-view-menu">
|
||||
<title>The <guimenu>View</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
<anchor id="view-fullscreen" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;&Shift;<keycap>F</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>View</guimenu>
|
||||
<guimenuitem>Full Screen Mode</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>With this action you toggle the full screen mode.</para>
|
||||
<para>Note: When code is executed while in full screen mode everything but the canvas is hidden. This makes it possible to write <quote>full screen</quote> programs in &kturtle;.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="view-linenumbers" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>F11</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>View</guimenu>
|
||||
<guimenuitem>Show Line Numbers</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>With this action you can show the line numbers in the code editor. This can be handy for finding errors.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="the-tools-menu">
|
||||
<title>The <guimenu>Tools</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
<anchor id="tools-color-picker" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Alt;<keycap>C</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Color Picker</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action opens the color picker. Using the color picker you can easily select a <glossterm linkend="rgb">color code</glossterm> and insert it in <link linkend="the-code-editor">the code editor</link>.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-indent" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>I</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Indent</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action <quote>indents</quote> (adds white space at the beginning of) the lines that are selected. When <quote>indentation</quote> is used properly this can make code much easier to read. All examples use indentation, please check them out.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-unindent" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Unindent</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action <quote>unindents</quote> (removes the white space at the beginning of) the lines that are selected.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-clean-indent" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Clean Indentation</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action cleans <quote>indentation</quote> (removes all the white space at the beginning of) the lines that are selected.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-comment" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;<keycap>D</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Comment</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action add comment characters (#) in from of the lines that are selected. Lines that start with a comment character are ignored when the code is executed. Comments allow the programmer to explain a bit about his code or they can be used to temporarily prevent a certain piece of code from being executed.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-uncomment" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Ctrl;&Shift;<keycap>D</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Tools</guimenu>
|
||||
<guimenuitem>Uncomment</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action removes the comment characters from the selected lines.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="the-setting-menu">
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
<anchor id="toggle-toolbar" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show/Hide Toolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the Main Toolbar</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="toggle-statusbar" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show/Hide Statusbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Toggle</action> the Statusbar</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="tools-advanced" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guisubmenu>Advanced Settings</guisubmenu>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Here you can change things you normally do not need to change. The <guisubmenu>Advanced Settings</guisubmenu> submenu has three items: <guimenuitem>Configure Editor...</guimenuitem> (the standard &kate; editor settings dialog), <guimenuitem>Configure Shortcuts...</guimenuitem> (the standard &kde; shortcut settings dialog), and <guimenuitem>Configure Toolbars...</guimenuitem> (the standard &kde; toolbars setting dialog).</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="settings-configure" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Configure &kturtle;...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This is used to configure &kturtle;. Here you can change the language of the &logo; commands or set a new initial canvas size.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="the-help-menu">
|
||||
<title>The <guimenu>Help</guimenu> Menu</title>
|
||||
<variablelist>
|
||||
<anchor id="help-handbook" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>F1</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>&kturtle; Handbook</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This action shows the handbook that you are currently reading.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="help-whats-this" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo>&Shift;<keysym>F1</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>What's This?</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>After activating this action the mouse arrow will be changed into a <quote>question mark arrow</quote>. When this arrow is used to click on parts of &kturtle; main window, a description of the particular part pops-up.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="help-context-help" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo><keysym>F2</keysym></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>Help on: ...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>This is a very useful function: it provides help on the code where the cursor in the code editor is at. So, ⪚, you have used the <userinput>print</userinput> command in your code, and you want to read and to know what the handbook says on this command. You just move your cursor so it is in the <userinput>print</userinput> command and you press <keysym>F2</keysym>. The handbook will then show all info on the <userinput>print</userinput> command.</para>
|
||||
<para>This function is very important while learning programming.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="help-report-bug" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>Report Bug...</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Use this to report a problem with &kturtle; to the developers. These reports can be used to make future versions of &kturtle; even better.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="help-about-kturtle" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>About &kturtle;</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Here you find information on &kturtle;, like the authors and the license it comes with.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
<variablelist>
|
||||
<anchor id="help-about-kde" />
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Help</guimenu>
|
||||
<guimenuitem>About &kde;</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para>Here you can find information on &kde;. If you do not know yet what &kde; is, this is a place you should not miss.</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect2>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="the-toolbar">
|
||||
<title>The Toolbar</title>
|
||||
<para>Here you can quickly reach the most used actions. By default, you will find here all main useful commands ending with the <guiicon>Execute Commands</guiicon> and <guiicon>Stop Execution</guiicon> icons.</para>
|
||||
<para>You can configure the toolbar using <menuchoice><guimenu>Settings</guimenu><guimenuitem>Advanced Settings</guimenuitem><guimenuitem>Configure Toolbars...</guimenuitem></menuchoice></para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="the-statusbar">
|
||||
<title>The Statusbar</title>
|
||||
<para>On the status bar you get feedback of the state of &kturtle;. On the left side it shows the feedback on the last action. On the right side you find the current location of the cursor (line and column numbers). In the middle of the Status bar is indicated the current language used for the commands.</para>
|
||||
</sect1>
|
||||
|
||||
</chapter>
|
||||
|
After Width: | Height: | Size: 31 KiB |
@ -0,0 +1,4 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
|
After Width: | Height: | Size: 1.1 KiB |
|
After Width: | Height: | Size: 947 B |
|
After Width: | Height: | Size: 995 B |
|
After Width: | Height: | Size: 907 B |
|
After Width: | Height: | Size: 1.1 KiB |
|
After Width: | Height: | Size: 1.1 KiB |
|
After Width: | Height: | Size: 986 B |
@ -0,0 +1,954 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY package "kdeedu">
|
||||
<!ENTITY kappname "&kverbos;">
|
||||
<!ENTITY % addindex "IGNORE">
|
||||
<!ENTITY % English "INCLUDE"><!-- change language only here -->
|
||||
]>
|
||||
|
||||
<book lang="&language;">
|
||||
|
||||
<bookinfo>
|
||||
<title>The &kverbos; Handbook</title>
|
||||
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Arnold</firstname>
|
||||
<surname>Kraschinski</surname>
|
||||
<affiliation>
|
||||
<address><email>&Arnold.Kraschinski.mail;</email></address>
|
||||
</affiliation>
|
||||
</author>
|
||||
<!-- TRANS:ROLES_OF_TRANSLATORS -->
|
||||
</authorgroup>
|
||||
|
||||
<copyright>
|
||||
<year>2001</year>
|
||||
<year>2002</year>
|
||||
<holder>&Arnold.Kraschinski;</holder>
|
||||
</copyright>
|
||||
|
||||
<legalnotice>&FDLNotice;</legalnotice>
|
||||
|
||||
<date>2002-05-23</date>
|
||||
<releaseinfo>3.0.8</releaseinfo>
|
||||
|
||||
<abstract>
|
||||
<para>
|
||||
&kverbos; is an application specially designed to study Spanish verbforms.
|
||||
</para>
|
||||
</abstract>
|
||||
|
||||
<keywordset>
|
||||
<keyword>KDE</keyword>
|
||||
<keyword>kdeutils</keyword>
|
||||
<keyword>Kapp</keyword>
|
||||
<keyword>verb</keyword>
|
||||
<keyword>spanish</keyword>
|
||||
</keywordset>
|
||||
|
||||
</bookinfo>
|
||||
|
||||
|
||||
|
||||
<chapter id="introduction">
|
||||
<title>Introduction</title>
|
||||
|
||||
<para>With &kverbos; the user can learn the forms of Spanish verbs. The
|
||||
program suggests a verb and a time and the user enters the different
|
||||
forms. The program corrects the user input an gives a feedback. The
|
||||
user can edit the list of the verbs that can be studied. The program
|
||||
can built regular verb forms by itself. Irregular verb forms have to
|
||||
be entered by the user. If a form of a verb is uncertain then the
|
||||
internet offers good sources:
|
||||
<ulink url="http://csgrs6k1.uwaterloo.ca/~dmg/lando/verbos/con-jugador.html">
|
||||
http://csgrs6k1.uwaterloo.ca/~dmg/lando/verbos/con-jugador.html</ulink>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The most interesting feature in the recent release is the use of
|
||||
&kfeeder;. This is a separate program that
|
||||
the user has to install separately if he wants to use it. If it is
|
||||
installed then the learning progress will be shown in the &kfeeder;
|
||||
application. A dog is running around and will be fed with bones if
|
||||
you are a good learner. Otherwise he will be lying around most of the
|
||||
time.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="using-kverbos">
|
||||
<title>Using &kverbos;</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kverbos;</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="mainscreen-leer.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>This window can be seen when the user starts the program.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>When the user starts the program he can see this window. This is
|
||||
the main window of the application where the user can train verb
|
||||
forms. At the moment no verb file is loaded. So the program cannot
|
||||
suggest a verb. First the user has to open a file either with the menu
|
||||
<menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice>
|
||||
or with the menubar or he has to enter some verbs with
|
||||
<menuchoice><guimenu>Edit</guimenu>
|
||||
<guimenuitem>Enter</guimenuitem></menuchoice>new verb.</para>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kverbos; with a loaded verb
|
||||
file</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="mainscreen1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you see the main window with a loaded verb file.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>Once the user has opened a file with verbs the program suggests
|
||||
one of them and a time. The user can type the solution into the textboxes.
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="limpiar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>This button wipes out all user input.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="corregir.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>The user can test his input with this
|
||||
button. Incorrect forms will be underlined. Then the user has the
|
||||
chance to do it better and correct the forms another time. If one of
|
||||
the forms wasn't correct the verb cannot be counted as correct
|
||||
anymore. </para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="solucion.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>If the user wants to see the solution he can use <guiicon>show
|
||||
solution</guiicon>. Then the correct solution is displayed in the editboxes. If
|
||||
the user uses this button the verb cannot be counted as correct
|
||||
anymore.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="continuar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>The last button in this row can have two functions.</para>
|
||||
|
||||
<para>If the user presses this button and the verb forms haven't been
|
||||
corrected yet the button behaves like the 'corregir' button. The verb
|
||||
forms are corrected and the user can see if his input was correct. If
|
||||
the user wants to go on he has to press the button again.</para>
|
||||
|
||||
<para>If the button is pressed and the verbs already have been
|
||||
corrected the program goes on to the next verb. That means another
|
||||
verb is selected and presented to the user.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>A second line of buttons <inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="letters.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject>
|
||||
allows the user enter special spanish characters which probably cannot be entered by keyboard.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
In the status bar of the program the user gets information about his
|
||||
work. He can see how many verbs he has trained and how many of them
|
||||
have been correct. He can see how many verbs are stored in the opened
|
||||
file and which username has been entered, too.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The progress bar is another feedback for the user. He can see his
|
||||
correct answers as a percentage of trained verbs.
|
||||
</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="commands">
|
||||
<title>Command Reference</title>
|
||||
|
||||
<sect1 id="kverbos-mainwindow">
|
||||
<title>The main &kverbos; window</title>
|
||||
<para>
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of &kverbos; with a loaded verb file</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="mainscreen1.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you see the main window with a loaded verb file.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
|
||||
<!-- The File Menu ................................................................ -->
|
||||
<sect2>
|
||||
<title>The <guimenu>File</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<!-- File->New -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>N</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Creates a new document. That means that the verbs
|
||||
in the actual list are deleted. The number of verbs is set to 0.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Open -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>O</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a verb file.</action> The file dialog opens and
|
||||
the user can select one of the verb files. The user has to make sure,
|
||||
that it is a verb file. There isn't a default verb file that comes
|
||||
with the program. The user has to enter his own verbs or he has to
|
||||
download a verb file from the &kverbos; website.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Open Standard Verb File -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Open Standard Verb File</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a verb file</action> that is delivered
|
||||
with &kverbos;. The user can use this file if he doesn't want to enter
|
||||
his own verbs.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Save -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>S</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Saves the document.</action> The file name
|
||||
dialog opens and the user can choose a name for the verb file. If the
|
||||
file name end with <literal role="extension">.htm</literal> or
|
||||
<literal role="extension">.html</literal> the verb list is saved as a
|
||||
&HTML; file.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Save As -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Save As</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Saves the document.</action> The file name
|
||||
dialog opens and the user can choose a name for the verb file. If the
|
||||
file name end with <literal role="extension">.htm</literal> or
|
||||
<literal role="extension">.html</literal> the verb list is saved as a
|
||||
&HTML; file.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Close -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>W</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Close</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Terminates the program.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->New Window -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>New Window</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Starts a new instance of the program.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- File->Quit -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<shortcut>
|
||||
<keycombo action="simul">&Ctrl;<keycap>Q</keycap></keycombo>
|
||||
</shortcut>
|
||||
<guimenu>File</guimenu>
|
||||
<guimenuitem>Quit</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Quits</action> &kverbos;</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- The Edit Menu ................................................................ -->
|
||||
<sect2>
|
||||
<title>The <guimenu>Edit</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<!-- Edit->Enter new verb -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Enter new verb</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens the dialog new verbs where you can add
|
||||
new verbs to the verb list. This dialog is described in another
|
||||
chapter of this documentation. </action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- Edit->Edit verblist -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Edit</guimenu>
|
||||
<guimenuitem>Edit verblist</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a dialog with a list of all the verbs that are in the actual
|
||||
verb list. You can edit this verb list. This dialog is described in another chapter of this
|
||||
documentation.</action></para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- The User Menu ................................................................ -->
|
||||
<sect2>
|
||||
<title>The <guimenu>User</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<!-- User->username -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>User</guimenu>
|
||||
<guimenuitem>username</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a small dialog where you can enter your username.
|
||||
</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- User->results -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>User</guimenu>
|
||||
<guimenuitem>results</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a dialog where a user can see the number of training
|
||||
sessions he has done with the program and the latest ten results.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- The settings menu -->
|
||||
<sect2>
|
||||
<title>The <guimenu>Settings</guimenu> Menu</title>
|
||||
|
||||
<variablelist>
|
||||
|
||||
<!-- Settings->Show toolbar -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show toolbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>The user can decide whether he wants to see the toolbar or not.
|
||||
He can set it here.</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- Settings->Show status bar -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>Show statusbar</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>The user can decide whether he wants to see the status bar or not.
|
||||
In the status bar are shown information like the number of trained verbs and the user name.
|
||||
</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<!-- Settings->options -->
|
||||
<varlistentry>
|
||||
<term><menuchoice>
|
||||
<guimenu>Settings</guimenu>
|
||||
<guimenuitem>options</guimenuitem>
|
||||
</menuchoice></term>
|
||||
<listitem><para><action>Opens a dialog where a user can select the times he wants to train
|
||||
and the correction mode. More details see the chapter about this dialog.
|
||||
</action></para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
</variablelist>
|
||||
|
||||
</sect2>
|
||||
|
||||
<!-- The Help Menu ................................................................ -->
|
||||
<sect2>
|
||||
<title>The Help Menu</title>
|
||||
|
||||
&help.menu.documentation;
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<!-- ................................................................ -->
|
||||
<!-- The New Verb Dialog ............................................ -->
|
||||
<sect1 id="new-verb-dialog">
|
||||
<title>The New Verb Dialog</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the New Verb dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="newverb.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you can see the new verb dialog where the user can enter new verbs.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Use this dialog if you want to make your own verb list or if you want
|
||||
to append some new verbs to an existing verb list. Here you can enter
|
||||
the infinitive of the spanish verb and its meaning in a foreign
|
||||
language. Important is, that you tell the program if it is a regular
|
||||
verb or one of the spanish group verbs or an irregular one. If it is
|
||||
irregular you have to enter the irregular forms, too. Be careful with
|
||||
this dialog and the verb forms you enter because the program uses this
|
||||
data to generate forms automatically.
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="input.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>Some of the Edit boxes where you can enter the verb information.
|
||||
There are similar Edit Boxes for the gerund and participle form and all the other forms
|
||||
if needed.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="type.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>With this Combo Box you select which type of verb you have entered. Do
|
||||
this carfully because it is important information for the program to do its work properly.
|
||||
</para>
|
||||
<para>
|
||||
The Spanish language knows three types of regular conjugation. These are the conjugation
|
||||
pattern for the verbs ending on -er, -ar, and -ir. A lot of verbs are not regular in all
|
||||
forms but they aren't completely irregular. This verbs are called group verbs and can
|
||||
be divided in several groups. The program can generate the forms for the regular verbs
|
||||
and the ones for the group verbs itself. It only needs the information to which group
|
||||
the verb belongs. Other verbs are irregular and the irregular forms have to be entered.
|
||||
Select the group in the Combo Box.
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term>regular</term>
|
||||
<listitem><para>Chose this if it is a completely regular verb of one of the
|
||||
patterns -ar, -er or -ir.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>irregular</term>
|
||||
<listitem><para>Select this if the verbs doesn't belong to one of the groups
|
||||
described below. The Tab View will be activated and you can enter all the
|
||||
irregular forms.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>e > ie</term>
|
||||
<listitem><para>Chose this for stem changing verbs where the e in the stem changes to ie.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>o > ue</term>
|
||||
<listitem><para>Chose this for stem changing verbs where the o in the stem changes to ue.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>u > ue</term>
|
||||
<listitem><para>Chose this for stem changing verbs where the u in the stem changes to ue.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>e > i</term>
|
||||
<listitem><para>Chose this for stem changing verbs where the e in the stem changes to i.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>c > qu</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>c</quote> comes before an <quote>e</quote>
|
||||
the <quote>c</quote> changes to <quote>qu</quote>. Examples: colocar, atacar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>g > gu</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>g</quote> comes before an <quote>e</quote>
|
||||
the <quote>g</quote> changes to <quote>gu</quote>. Example: pagar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>z > c</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>z</quote> comes before an <quote>e</quote>
|
||||
the <quote>z</quote> changes to <quote>c</quote>. Examples: cazar, alzar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>gu > gu</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>gu</quote> comes before an <quote>e</quote>
|
||||
the <quote>gu</quote> changes to <quote>gu</quote>. Example: averiguar</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>c > z</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>c</quote> comes before an <quote>o</quote>
|
||||
or <quote>a</quote> the <quote>c</quote> changes to <quote>z</quote>. Examples: vencer, zurcir</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>g > j</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If a <quote>g</quote> comes before an <quote>o</quote>
|
||||
or <quote>a</quote> the <quote>g</quote> changes to <quote>j</quote>. Examples: coger, dirigir</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>gu > g</term>
|
||||
<listitem><para>A verb with orthografic irregularity. If <quote>gu</quote> comes before an <quote>o</quote>
|
||||
or <quote>a</quote> the <quote>gu</quote> changes to <quote>g</quote>. Example: distinguir</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>qu > c</term>
|
||||
<listitem><para>A verb with
|
||||
orthografic irregularity. If
|
||||
<quote>qu</quote> comes before an
|
||||
<quote>o</quote> or <quote>a</quote>
|
||||
the <quote>qu</quote> changes to
|
||||
<quote>c</quote>. Example:
|
||||
delinquir</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>accent like <quote>enviar</quote></term>
|
||||
<listitem><para>A verb where the accent changes in some forms. Example: enviar
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>accent like <quote>continuar</quote></term>
|
||||
<listitem><para>A verb where the accent changes in some forms. Example: continuar
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term>missing i</term>
|
||||
<listitem><para>Some verbs lose the instressed <quote>i</quote> in some forms. Examples:
|
||||
taner, grunir, bullir</para></listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="times.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>If you enter an irregular verb the tab view will be activated and
|
||||
you can select the tab with the irregular forms.</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="limpiarpagina.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>You have entered some incorrect information and want to delete them. With this
|
||||
button you can wipe out the data in the Edit box of one single tab.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="letters.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>This buttons insert the displayed spanish characters to the Edit box that has the
|
||||
focus. Often these characters cannot be entered with the keyboard.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="limpiar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>You want to wipe out all information in all Edit Boxes on all tabs. Then use this
|
||||
button.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="anterior.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>Selects the verb before the actual verb in the verb list into the dialog. You can
|
||||
read an change the information for this verb. If the actual verb is the first one then
|
||||
the last one is loaded into the dialog.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="siguiente.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>Selects the verb behind the actual verb in the verb list into the dialog. You can
|
||||
read an change the information for this verb. If the actual verb is the last one then the
|
||||
first one is loaded.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="cerrar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>Closes the dialog and returns to the main program or the Edit Verblist Dialog
|
||||
depending from where the dialog was opened.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<!-- ................................................................ -->
|
||||
<!-- The Verblist Dialog ............................................ -->
|
||||
<sect1 id="editverblist-dialog">
|
||||
<title>The Edit Verblist Dialog</title>
|
||||
<para>
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the Edit Verblist dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="verblist.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you can see the Edit verblist dialog where the user can edit the list
|
||||
of the verbs.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
</para>
|
||||
<para>
|
||||
In the list view of this dialog you can see all the verbs of the opened verb file. If there
|
||||
aren't any verbs in the file or if there isn't a file open the list view will be empty.
|
||||
You can select a verb from the list and edit this verb or you select and delete one of them.
|
||||
</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="borrar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>This button deletes the selected verb from the list of verbs.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="cancelar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>With this button you can leave the dialog. All changes that have been
|
||||
made until this moment will not affect the verb list of the main program. That means
|
||||
that the list of the main program will be unchanged.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="editar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem><para>The selected verb will be edited. The new verb dialog opens and the
|
||||
selected verb is loaded to the edit boxes. You can make your changes. If you make a
|
||||
double click on a verb this has the same effect than this button.
|
||||
</para></listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><inlinemediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="cerrar.png" format="PNG"/>
|
||||
</imageobject>
|
||||
</inlinemediaobject></term>
|
||||
<listitem>
|
||||
<para>With this button you can close the dialog. The changes that have been made are
|
||||
stored in the verb list of the main program.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</sect1>
|
||||
|
||||
<!-- ................................................................ -->
|
||||
<!-- The Username Dialog ............................................ -->
|
||||
<sect1 id="username-dialog">
|
||||
<title>The Username Dialog</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the Username Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="username.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you can see the Username Dialog where the user can enter his name.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
Enter your name here. The name is set as the new username of the program. It will be
|
||||
displayed in the programs status bar. Use the
|
||||
<guibutton>OK</guibutton> Button to confirm your input. The
|
||||
<guibutton>Cancel</guibutton> button leaves the user name unchanged.
|
||||
</para>
|
||||
<para>
|
||||
The program will store some information about your learning progress. The number of training
|
||||
sessions, the result of the last ten sessions and lists with the verbs that you entered
|
||||
right or wrong recently.
|
||||
</para>
|
||||
<para>
|
||||
You can have a look at this information in the
|
||||
<menuchoice><guimenu>User</guimenu><guimenuitem>Results</guimenuitem></menuchoice>
|
||||
dialog.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<!-- ................................................................ -->
|
||||
<!-- The User Result Dialog ......................................... -->
|
||||
<sect1 id="userresult-dialog">
|
||||
<title>The User Result Dialog</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the User Result Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="result.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you can see the User Result Dialog where the user can see his results.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
In this dialog you can see the information that the program stores about you under
|
||||
your username. On the left you can see the results of the latest ten sessions and on the
|
||||
right are lists with the word that you entered right or wrong recently. A verb remains in the
|
||||
list of the right verbs for some time then it changes to the status unlearned again. The
|
||||
verbs that are in the wrong list will appear more frequently. They stay in the list until
|
||||
you enter them correctly. Then they will return to the list of the unlearned verbs.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<!-- ................................................................ -->
|
||||
<!-- The Settings Options Dialog .................................... -->
|
||||
<sect1 id="settingsoptions-dialog">
|
||||
<title>The Settings Options Dialog</title>
|
||||
|
||||
<screenshot>
|
||||
<screeninfo>Here's a screenshot of the Settings Options Dialog</screeninfo>
|
||||
<mediaobject>
|
||||
<imageobject>
|
||||
<imagedata fileref="options.png" format="PNG"/>
|
||||
</imageobject>
|
||||
<textobject>
|
||||
<phrase>Here you can see the Settings Options Dialog where the user can change
|
||||
some options of the program.</phrase>
|
||||
</textobject>
|
||||
</mediaobject>
|
||||
</screenshot>
|
||||
|
||||
<para>
|
||||
In this dialog you can select the tenses that should be trained. So if you want to study a
|
||||
specific tense or if you haven't learned how to build the forms of a specific tense yet so
|
||||
you can select or deselect the tenses here. Your selection is stored to the properties file
|
||||
of the program.
|
||||
</para>
|
||||
<para>
|
||||
You can select a correction mode too. If you select <guilabel>correct
|
||||
strictly</guilabel> then every missing accent is regarded as an
|
||||
error. You can make it easier with <guilabel>ignore accent</guilabel>
|
||||
then a missing accent isn't an error.
|
||||
</para>
|
||||
<para>
|
||||
At last you can control the use of &kfeeder; if this application is
|
||||
installed. You can decide if the learning results will be shown with
|
||||
&kfeeder;, if the splash screen can be seen when the program is
|
||||
starting and what type of food animations are used. The last points
|
||||
needs a further explanation. &kfeeder; displays an animal that is
|
||||
running around. When you enter a correct solution your points will be
|
||||
send to &kfeeder;. The dog gets bones for each point. If you chose
|
||||
<guilabel>move food automatically</guilabel> then the bones move down
|
||||
from the ceiling and one point is one bone. Otherwise every point is
|
||||
only a move for a bone. So you will need more points until the dog can
|
||||
reach the bone. Really the option <guilabel>move food
|
||||
automatically</guilabel> is more interesting.
|
||||
</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
<chapter id="developers">
|
||||
<title>Developer's Guide to &kverbos;</title>
|
||||
|
||||
<para>
|
||||
At the moment it is not possible to program any plugins for &kverbos;.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
|
||||
<chapter id="faq">
|
||||
<title>Questions and Answers</title>
|
||||
|
||||
&reporting.bugs;
|
||||
&updating.documentation;
|
||||
|
||||
<para>Until now nobody had a question that could be answered here.</para>
|
||||
</chapter>
|
||||
|
||||
<chapter id="credits">
|
||||
|
||||
<title>Credits and License</title>
|
||||
|
||||
<para>
|
||||
&kverbos;
|
||||
</para>
|
||||
<para>
|
||||
Program Copyright 2002 &Arnold.Kraschinski; <email>&Arnold.Kraschinski.mail;</email>
|
||||
</para>
|
||||
<!--<para>
|
||||
Contributors:
|
||||
<itemizedlist>
|
||||
<listitem><para>-<email>-</email></para>
|
||||
</listitem>
|
||||
<listitem><para>-<email>-</email></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>-->
|
||||
|
||||
<para>
|
||||
Documentation Copyright 2002 &Arnold.Kraschinski; <email>&Arnold.Kraschinski.mail;</email>
|
||||
</para>
|
||||
|
||||
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
|
||||
&underFDL;
|
||||
&underGPL;
|
||||
|
||||
</chapter>
|
||||
|
||||
<appendix id="installation">
|
||||
<title>Installation</title>
|
||||
|
||||
<sect1 id="getting-kverbos">
|
||||
<title>How to obtain &kverbos;</title>
|
||||
|
||||
&install.intro.documentation;
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="requirements">
|
||||
<title>Requirements</title>
|
||||
|
||||
<para>
|
||||
In order to successfully use &kverbos;, you need &kde; 3.x.x. The program is distributed
|
||||
without a verblist file. So you have to enter the verbs yourself or you can download a
|
||||
verbfile.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
A verblist file and &kverbos; itself can be found
|
||||
on <ulink url="http://members.tripod.de/arnoldk67/computer/kverbos/kverbos.htm">
|
||||
The &kverbos; home page</ulink>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
You can find a list of changes at <ulink
|
||||
url="http://edu.kde.org/kverbos/">http://edu.kde.org/kverbos/</ulink>.
|
||||
</para>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="compilation">
|
||||
<title>Compilation and Installation</title>
|
||||
|
||||
&install.compile.documentation;
|
||||
|
||||
</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:
|
||||
-->
|
||||
|
After Width: | Height: | Size: 2.5 KiB |
|
After Width: | Height: | Size: 1.5 KiB |
|
After Width: | Height: | Size: 1.3 KiB |
|
After Width: | Height: | Size: 1.3 KiB |
|
After Width: | Height: | Size: 47 KiB |
|
After Width: | Height: | Size: 53 KiB |
|
After Width: | Height: | Size: 35 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 1.2 KiB |
|
After Width: | Height: | Size: 1.4 KiB |
|
After Width: | Height: | Size: 3.9 KiB |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 43 KiB |
@ -0,0 +1,29 @@
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
KDE_MANS = AUTO
|
||||
|
||||
check-local:
|
||||
$(MEINPROC) --check index.docbook
|
||||
|
||||
convert-local:
|
||||
$(MEINPROC) $(srcdir)/index.docbook
|
||||
|
||||
# needs pngcrush which reduces files size about 20%
|
||||
# brute-crush takes _very_ long time
|
||||
crush:
|
||||
mkdir -p crushed
|
||||
for i in *.png; do \
|
||||
pngcrush $$i crushed/$$i;\
|
||||
done
|
||||
mv *.png /tmp
|
||||
mv crushed/*.png .
|
||||
rm -r crushed
|
||||
|
||||
brute-crush:
|
||||
mkdir -p crushed
|
||||
for i in *.png; do \
|
||||
pngcrush -brute $$i crushed/$$i;\
|
||||
done
|
||||
mv *.png /tmp
|
||||
mv crushed/*.png .
|
||||
rm -r crushed
|
||||
|
After Width: | Height: | Size: 9.2 KiB |
|
After Width: | Height: | Size: 8.6 KiB |
|
After Width: | Height: | Size: 8.2 KiB |
|
After Width: | Height: | Size: 8.4 KiB |
|
After Width: | Height: | Size: 7.1 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 759 B |
|
After Width: | Height: | Size: 16 KiB |
File diff suppressed because it is too large
Load Diff
|
After Width: | Height: | Size: 11 KiB |
|
After Width: | Height: | Size: 20 KiB |
@ -0,0 +1,71 @@
|
||||
<?xml version="1.0" ?>
|
||||
<!DOCTYPE refentry PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
|
||||
<!ENTITY % English "INCLUDE">
|
||||
]>
|
||||
|
||||
<refentry lang="&language;">
|
||||
<refentryinfo>
|
||||
<author><personname><firstname>Ben</firstname><surname>Burton</surname></personname><email>bab@debian.org</email></author>
|
||||
<date>April 7, 2003</date>
|
||||
</refentryinfo>
|
||||
|
||||
<refmeta>
|
||||
<refentrytitle><command>spotlight2kvtml</command></refentrytitle>
|
||||
<manvolnum>1</manvolnum>
|
||||
</refmeta>
|
||||
|
||||
<refnamediv>
|
||||
<refname><command>spotlight2kvtml</command></refname>
|
||||
<refpurpose>Convert a Spotlight Online vocabularly list to a &kvoctrain; data file.</refpurpose>
|
||||
</refnamediv>
|
||||
|
||||
<refsynopsisdiv>
|
||||
<cmdsynopsis>
|
||||
<command>spotlight2kvtml</command>
|
||||
|
||||
<group><option><replaceable>spotfile</replaceable> <replaceable>month</replaceable> <replaceable>year</replaceable></option></group>
|
||||
<group><option>KDE Generic Options</option></group>
|
||||
<group><option>Qt Generic Options</option></group>
|
||||
|
||||
</cmdsynopsis>
|
||||
</refsynopsisdiv>
|
||||
|
||||
<refsect1>
|
||||
<title>Description</title>
|
||||
|
||||
<para><command>spotlight2kvtml</command> is used to convert a
|
||||
Spotlight Online vocabulary list to a &kvoctrain; data file (<literal
|
||||
role="extension">*.kvtml</literal>).</para>
|
||||
|
||||
<para>The given vocabulary list (spotfile) must be in plain text
|
||||
format (&ie;, you will need to convert the downloaded RTF or Word
|
||||
document into a plain text file). The name of the new &kvoctrain; data
|
||||
file will be derived from the given spotfile.</para>
|
||||
|
||||
<para>The given month and year will be used in the title and lesson
|
||||
names in the new &kvoctrain; data file.</para>
|
||||
|
||||
<para>Note that Spotlight Online changes its vocabulary list format
|
||||
from time to time, so <command>spotlight2kvtml</command> might be out
|
||||
of date and might not behave correctly.</para>
|
||||
|
||||
<para>This package is part of the official KDE edutainment module.</para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>See Also</title>
|
||||
|
||||
<para>kvoctrain(1), langen2kvtml(1)</para>
|
||||
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Authors</title>
|
||||
|
||||
<para><command>spotlight2kvtml</command> was written by &Ewald.Arnold;
|
||||
&Ewald.Arnold.mail;.</para> <para>This manual page was prepared by
|
||||
<personname><firstname>Ben</firstname><surname>Burton</surname></personname><email>bab@debian.org</email>
|
||||
</para> </refsect1>
|
||||
|
||||
</refentry>
|
||||
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 20 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 21 KiB |
|
After Width: | Height: | Size: 18 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 4.8 KiB |
|
After Width: | Height: | Size: 7.4 KiB |
|
After Width: | Height: | Size: 9.8 KiB |
|
After Width: | Height: | Size: 9.9 KiB |
|
After Width: | Height: | Size: 17 KiB |
|
After Width: | Height: | Size: 15 KiB |
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 9.2 KiB |
|
After Width: | Height: | Size: 7.1 KiB |
|
After Width: | Height: | Size: 8.1 KiB |
|
After Width: | Height: | Size: 9.0 KiB |
|
After Width: | Height: | Size: 18 KiB |
@ -0,0 +1,5 @@
|
||||
|
||||
KDE_LANG = en
|
||||
KDE_DOCS = AUTO
|
||||
|
||||
kde_docs_KDEDOCS = kwq-dlg-configure-characters.png
|
||||
File diff suppressed because it is too large
Load Diff
|
After Width: | Height: | Size: 19 KiB |
|
After Width: | Height: | Size: 24 KiB |
|
After Width: | Height: | Size: 36 KiB |
|
After Width: | Height: | Size: 22 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 9.7 KiB |
|
After Width: | Height: | Size: 9.3 KiB |
|
After Width: | Height: | Size: 5.0 KiB |
|
After Width: | Height: | Size: 16 KiB |
|
After Width: | Height: | Size: 33 KiB |
|
After Width: | Height: | Size: 10 KiB |
|
After Width: | Height: | Size: 12 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 44 KiB |
|
After Width: | Height: | Size: 56 KiB |
|
After Width: | Height: | Size: 45 KiB |
@ -0,0 +1,30 @@
|
||||
*** Changes after Kalzium Hydrogen ***
|
||||
Change:
|
||||
- Make the plot window always plot on changes of setting
|
||||
(No more having to press the Plot button.)
|
||||
|
||||
Add:
|
||||
- The spectrum dialog
|
||||
- The table now has a small gap over the rare earth
|
||||
- The isotope table provides now more data
|
||||
- halflife-periods
|
||||
- weight
|
||||
- number of neutrons
|
||||
- abundance
|
||||
- alpha-decay
|
||||
- betadecay (both plus and minus)
|
||||
- spin
|
||||
- magnetic moment
|
||||
- The documentation has been overhauled
|
||||
- The menustructure is now more consistent
|
||||
- One icon has been added
|
||||
- Make the mainwidget a QScrollView. This make sizehandling easier
|
||||
- Improved layout of the detailed information dialog
|
||||
- Added a widget which shows you a table of the isotopes
|
||||
- Added EqChem, a chemical equation solver
|
||||
- Added several glossary-items
|
||||
- Display no legend when the No Color-mode is choosen
|
||||
- The dialogboxes now have a help-button which will open the
|
||||
correct page in the help
|
||||
- The molecule parser for the weight calculator.
|
||||
- adding the abundance of an element in a crustal rock (measured in ppm)
|
||||
@ -0,0 +1,6 @@
|
||||
SUBDIRS = src
|
||||
|
||||
AUTOMAKE_OPTIONS = foreign
|
||||
|
||||
DOXYGEN_REFERENCES = kdeui kdecore kfile libkdeedu
|
||||
include ../admin/Doxyfile.am
|
||||
@ -0,0 +1,14 @@
|
||||
For full functionality (equation solver integration) Kalzium depends on Ocaml and the FaCiLe library. The FaciLe library is only used for compilation and for packagers.
|
||||
|
||||
Ocaml
|
||||
webpage: http://caml.inria.fr/about/index.en.html
|
||||
download: http://caml.inria.fr/download.en.html
|
||||
|
||||
FaCiLe
|
||||
webpage: http://www.recherche.enac.fr/opti/facile/
|
||||
download: http://www.recherche.enac.fr/opti/facile/distrib/
|
||||
|
||||
|
||||
If these 2 dependencies are not met, Kalzium will not propose the equation solver in its Tools menu.
|
||||
|
||||
The Kalzium developers
|
||||
@ -0,0 +1,70 @@
|
||||
Release plan
|
||||
============
|
||||
|
||||
Status: Under discussion
|
||||
|
||||
|
||||
Overview
|
||||
--------
|
||||
|
||||
Currently we plan for 3 releases:
|
||||
|
||||
- A standalone release of Kalzium in August
|
||||
- The release for KDE 3.5
|
||||
- The release for KDE 4.0
|
||||
|
||||
The reason for the standalone release is that we want user feedback
|
||||
for the KDE 3.5 release.
|
||||
|
||||
All details of the release plan are below the TODO items for the
|
||||
respective release.
|
||||
|
||||
Dates
|
||||
|
||||
2005-08-07 Feature freeze. All features in the TODO for
|
||||
version Helium should be done at the end of this day.
|
||||
|
||||
2005-08-26 End of bug testing and fixing period.
|
||||
|
||||
2005-08-30 Release of Kalzium Helium
|
||||
|
||||
|
||||
================================================================
|
||||
Details of the release plan
|
||||
|
||||
|
||||
* Standalone release of Kalzium
|
||||
+ After one week of testing and improving I would like to release
|
||||
Kalzium (together with libkdeedu for the plotting and the glossary)
|
||||
on the 30th of August (a tuesday). Two days later I leave to to
|
||||
aKademy in Malaga, Spain.
|
||||
|
||||
+ Release criteria, prio 1:
|
||||
- Fix all bugs on bugs.kde.org
|
||||
- *must be* Update edu.kde.org/kalzium with screenshots
|
||||
- *must be* increase the version number
|
||||
+ Release criteria, prio 2:
|
||||
- Make the release very usable:
|
||||
- Write the documentation
|
||||
These prio 2 issues will be prio 1 for KDE 3.5
|
||||
|
||||
+ Release mechanism:
|
||||
- Announcement on kde-edu@kde.org
|
||||
- Announcement on kalzium@kde.org
|
||||
- Announcement on www.kde-apps.org
|
||||
- Announcement on kde-announce@kde.org
|
||||
- I will blog about the release and it goals
|
||||
|
||||
* KDE 3.5-release
|
||||
+ Make use of the feedback we get of the standalone release
|
||||
+ The 3.5-release will probably be pretty identical with the
|
||||
standalone-release, except for bug fixes and usability issues.
|
||||
|
||||
|
||||
* KDE 4-release
|
||||
|
||||
+ Port to Qt4. We use a lot QValueList<T> and paintEvents, so I
|
||||
expect some fun :)
|
||||
+ Switch to KCanvas2 so that scaling the table is possible?
|
||||
IW: Scaling can be made possible without KCanvas2 as well.
|
||||
+ Implement the things in the TODO-file
|
||||
@ -0,0 +1,109 @@
|
||||
TODO for Kalzium 1.5
|
||||
===================
|
||||
|
||||
Bugs
|
||||
----
|
||||
|
||||
* Miscellaneous bugs:
|
||||
+ Make use of the biological symbol. ----
|
||||
CN: I lost the "translation" though, will have to look after it.
|
||||
CN: I have deactivated the drawingconde
|
||||
+ correct mass-rounding
|
||||
presumably, the arg()-funktion now rounds wrong -----
|
||||
|
||||
|
||||
================================================================
|
||||
Future versions
|
||||
|
||||
* Export to html and csv comes into my mind. Pretty easy I
|
||||
guess. Something like that was in Kalzium of KDE 3.1 I
|
||||
think. But my implementation sucked so much I removed it.
|
||||
|
||||
* Add KHotNewStuff support (xml) so that a user can define which
|
||||
dates are displayed in the timeline (see SOM)
|
||||
|
||||
* Log-scale of the gradient
|
||||
|
||||
* Plotting
|
||||
+ Add groups of elements, for example "Metals", 4th Period
|
||||
transitionmetals and so on. The user can easily select them
|
||||
and only plot the selected group
|
||||
+ More than one group should be plottable at once.
|
||||
This would enable the user to compare two or more groups,
|
||||
eg. 4th with 5th group
|
||||
|
||||
* Add more than only one mode to Kalzium, eg a mode with simplified
|
||||
user interface (less looks, easier menu structure, less information
|
||||
in the infodialog) and a full-mode where everything is enabled.
|
||||
|
||||
* There should be more data about the elements, for example which
|
||||
chemitry-nobel-prize was won in that year (+/- 5 years or so)
|
||||
|
||||
* Make use of hotnewstuff. In the detailinfodlg there should be
|
||||
a weblookup. If the user click on a button Konq will start with
|
||||
a page about the element. Of course, the user should be able
|
||||
to decide which page.
|
||||
For this we could create a simple editor and store it in xml.
|
||||
on edu.kde.org we would enable KHNS so that users can share
|
||||
their pages. Imaginge for example the different wikipedia-languages
|
||||
|
||||
* Add the weblookup also in the glossary
|
||||
|
||||
* Besides although for the "common user" is more easy to understand
|
||||
the information in "... years", it's more correct and flexible in
|
||||
scientific terms to use the scientific notation: ...x10e9 years.
|
||||
|
||||
* Add lesson-mode? The idea is that a teacher could create xml-files
|
||||
which can somehow be used as lessons. Perhaps something like
|
||||
"find out how many element boild at 200 Degree Celsius and above.
|
||||
With the information: Why is it so?"
|
||||
|
||||
* Add experiental mode: A teacher defines experiments (in xml) where
|
||||
fotos and texts are used to represent a experiment/task. Perhaps
|
||||
combined with openoffice-files (charts and so on). Like in CheExp.
|
||||
|
||||
* Add two comboboxes to the infodialog: That way the user can search
|
||||
for an element by name and number. Like in CheExp
|
||||
|
||||
* Thinking on people with some disabilities, it would be great if they can
|
||||
select the elements on the grid by using cursor keys (or just tab key).
|
||||
|
||||
* Perhaps there must be a KComboBox in the toolbar where you can select the
|
||||
different views of the PTE.
|
||||
|
||||
* There's no view of the natural occurrence of the elements. Look at
|
||||
http://en.wikipedia.org/wiki/Periodic_table_(standard) and see the notes
|
||||
about borders.
|
||||
|
||||
* Spectrum-Classes
|
||||
+ Create an editor. The user enters some wavelength and Kalzium will
|
||||
create a graphic from that data.
|
||||
|
||||
* Some websites with a lot of information:
|
||||
http://en.wikipedia.org/wiki/History_of_chemistry
|
||||
http://en.wikipedia.org/wiki/Timeline_of_chemical_element_discovery
|
||||
http://en.wikipedia.org/wiki/Nobel_Prize_in_chemistry
|
||||
http://chemipedia.org/mediawiki/index.php/Hauptseite
|
||||
http://physics.nist.gov/PhysRefData/Handbook/periodictable.htm
|
||||
|
||||
Properties listed on my periodic table:
|
||||
Page 1:
|
||||
- electronconfig [DONE]
|
||||
- Atomic radius (covalent, ionic, vdw [Semi-DONE]
|
||||
- reduction potential
|
||||
- EN [DONE, there are more values, other scales]
|
||||
- abundance [Semi-Done]
|
||||
- biological symbol [DONE]
|
||||
- IUPAC-Name [DONE]
|
||||
- number [DONE]
|
||||
- oxidation-numer(s) [DONE, need to be checked]
|
||||
- orbitals [DONE]
|
||||
|
||||
Page 2:
|
||||
- number of natural isotopes
|
||||
- massenzahlen (# of neutrons) of the most important isotopes
|
||||
- natural abundance of the isotopes
|
||||
- first IE [DONE]
|
||||
- density [DONE]
|
||||
- SP and BP [DONE]
|
||||
- Infos about the most important isotope [DONE but needs to be improved]
|
||||
@ -0,0 +1,26 @@
|
||||
if test x$eqchem_enabled = xno && test x$with_ocamlsolver != xno ; then
|
||||
cat << EOF
|
||||
|
||||
The Kalzium Chemical Equation Solver has been disabled. Possible
|
||||
reasons of that:
|
||||
|
||||
EOF
|
||||
|
||||
if test "x$ocaml_installed" = "xno"; then
|
||||
cat << EOF
|
||||
* OCaml was not found. In order to have the Solver, you have to
|
||||
install OCaml. You can get OCaml from http://pauillac.inria.fr/ocaml/.
|
||||
|
||||
EOF
|
||||
fi
|
||||
|
||||
if test "x$facile_installed" = "xno"; then
|
||||
cat << EOF
|
||||
* The FaCiLe module for OCaml was not found. In order to have the Solver,
|
||||
you have to install the FaCiLe module. You can get it from
|
||||
http://www.recherche.enac.fr/opti/facile/.
|
||||
|
||||
EOF
|
||||
fi
|
||||
|
||||
fi
|
||||
@ -0,0 +1,66 @@
|
||||
#MIN_CONFIG(3.3)
|
||||
|
||||
ocaml_installed=no
|
||||
facile_installed=no
|
||||
eqchem_enabled=no
|
||||
|
||||
AC_DEFUN([OCAML_PROG],[
|
||||
KDE_FIND_PATH(ocamlopt, OCAML, [$bindir],
|
||||
[
|
||||
OCAML=''
|
||||
])
|
||||
])
|
||||
|
||||
AC_DEFUN([FACILE_PROG],[
|
||||
AC_REQUIRE([OCAML_PROG])
|
||||
|
||||
AC_MSG_CHECKING([if the facile constraint solver is installed])
|
||||
FACILE="`ocamlopt -where`/facile"
|
||||
if test -d "$FACILE" ; then
|
||||
eqchem_enabled=yes
|
||||
AC_MSG_RESULT([yes])
|
||||
facile_installed=yes
|
||||
else
|
||||
eqchem_enabled=no
|
||||
AC_MSG_RESULT([no])
|
||||
facile_installed=no
|
||||
fi
|
||||
|
||||
AC_SUBST([FACILE])
|
||||
])
|
||||
|
||||
AC_ARG_ENABLE( ocamlsolver,
|
||||
[ --disable-ocamlsolver Disable support for the OCaml solver @<:@default=check@:>@]],
|
||||
[ with_ocamlsolver=$enableval ],
|
||||
[ with_ocamlsolver=check] )
|
||||
|
||||
if test "x$with_ocamlsolver" != xno; then
|
||||
OCAML_PROG
|
||||
if test -n "$OCAML"; then
|
||||
ocaml_installed=yes
|
||||
FACILE_PROG
|
||||
fi
|
||||
|
||||
AH_TEMPLATE(HAVE_FACILE, facile solver available?)
|
||||
|
||||
EQCHEM_SUB=
|
||||
OCAMLLIB=
|
||||
EQCHEM_LDADD=
|
||||
if test "$eqchem_enabled" = "yes"; then
|
||||
EQCHEM_SUB=solver
|
||||
OCAMLLIB=`ocamlc -where`
|
||||
FACILELIB=`ocamlc -where`/facile
|
||||
EQCHEM_LDADD="-lasmrun -lstr -lnums -lm -ldl solver.o modwrap.o"
|
||||
|
||||
AC_DEFINE(HAVE_FACILE, 1)
|
||||
fi
|
||||
|
||||
AC_SUBST(EQCHEM_SUB)
|
||||
AC_SUBST(OCAMLLIB)
|
||||
AC_SUBST(FACILELIB)
|
||||
AC_SUBST(EQCHEM_LDADD)
|
||||
|
||||
if test "$eqchem_enabled" = "yes"; then
|
||||
with_ocamlsolver=yes
|
||||
fi
|
||||
fi
|
||||
@ -0,0 +1,100 @@
|
||||
# set the include path for X, qt and KDE
|
||||
INCLUDES= -I$(srcdir)/../../libkdeedu/kdeeduplot -I$(srcdir)/../../libkdeedu/kdeeduui $(all_includes)
|
||||
|
||||
bin_PROGRAMS = kalzium
|
||||
kalzium_SOURCES = eqresult.cpp eqchemview.cpp kalzium.cpp \
|
||||
main.cpp \
|
||||
periodictableview.cpp \
|
||||
element.cpp \
|
||||
prefs.kcfgc \
|
||||
settings_colors.ui \
|
||||
settings_misc.ui \
|
||||
settings_units.ui \
|
||||
detailinfodlg.cpp \
|
||||
orbitswidget.cpp \
|
||||
plotwidget.cpp \
|
||||
elementdataviewer.cpp \
|
||||
plotsetupwidget.ui \
|
||||
detailedgraphicaloverview.cpp \
|
||||
molcalcwidgetbase.ui \
|
||||
molcalcwidget.cpp \
|
||||
timewidget.ui \
|
||||
timewidget_impl.cpp \
|
||||
somwidget.ui \
|
||||
somwidget_impl.cpp \
|
||||
kalziumtip.cpp \
|
||||
spectrum.cpp \
|
||||
isotope.cpp \
|
||||
kalziumdataobject.cpp \
|
||||
spectrumwidget.cpp \
|
||||
exporter.cpp \
|
||||
spectrumview.ui \
|
||||
spectrumviewimpl.cpp \
|
||||
kalziumutils.cpp \
|
||||
parser.cpp \
|
||||
moleculeparser.cpp \
|
||||
tempunit.cpp
|
||||
|
||||
kalzium_LDADD = ../../libkdeedu/kdeeduplot/libkdeeduplot.la ../../libkdeedu/kdeeduui/libkdeeduui.la $(LIB_KIO) $(LIB_KDEUI) $(LIB_KHTML) -L$(OCAMLLIB) -L$(FACILELIB) $(EQCHEM_LDADD)
|
||||
KDE_CXXFLAGS = -D_ISOC99_SOURCE
|
||||
|
||||
SUBDIRS = icons elementpics data $(EQCHEM_SUB)
|
||||
|
||||
EXTRA_DIST = main.cpp \
|
||||
kalzium.cpp kalzium.h \
|
||||
periodictableview.cpp periodictableview.h \
|
||||
element.cpp element.h \
|
||||
settings_colors.ui \
|
||||
settings_misc.ui \
|
||||
detailinfodlg.cpp detailinfodlg.h \
|
||||
orbitswidget.cpp orbitswidget.h \
|
||||
plotwidget.cpp plotwidget.h \
|
||||
elementdataviewer.cpp elementdataviewer.h \
|
||||
detailedgraphicaloverview.cpp detailedgraphicaloverview.h \
|
||||
molcalcwidget.cpp molcalcwidget.h \
|
||||
timewidget.ui \
|
||||
timewidget_impl.cpp timewidget_impl.h \
|
||||
somwidget.ui \
|
||||
somwidget_impl.cpp somwidget_impl.h \
|
||||
spectrum.cpp spectrum.h \
|
||||
isotope.cpp isotope.h \
|
||||
kalziumdataobject.cpp kalziumdataobject.h \
|
||||
spectrumwidget.cpp spectrumwidget.h \
|
||||
exporter.cpp exporter.h \
|
||||
spectrumview.ui \
|
||||
spectrumviewimpl.cpp spectrumviewimpl.h \
|
||||
kalziumutils.cpp kalziumutils.h \
|
||||
parser.cpp parser.h \
|
||||
moleculeparser.cpp moleculeparser.h \
|
||||
tempunit.cpp tempunit.h
|
||||
|
||||
METASOURCES = AUTO
|
||||
|
||||
xdg_apps_DATA = kalzium.desktop
|
||||
kde_kcfg_DATA = kalzium.kcfg
|
||||
|
||||
rcuidir = $(kde_datadir)/kalzium
|
||||
rcui_DATA = kalziumui.rc
|
||||
|
||||
KDE_ICON = AUTO
|
||||
|
||||
# the library search path.
|
||||
kalzium_LDFLAGS = $(all_libraries) $(KDE_RPATH)
|
||||
|
||||
#this RegExp-monster grep for <name origin=foo">bar</name> and puts the i18n() around foo and bar
|
||||
messages-old: rc.cpp
|
||||
cat data/data.xml | grep name| sed -e 's/< *name *origin *= *"\([^\"]*\)\">\([^<]*\)<\/ *name *>/I18N_NOOP(\"\1\"); I18N_NOOP(\"\2\");/;s/I18N_NOOP("");//g' | grep I18N_NOOP >> rc.cpp
|
||||
cat data/knowledge.xml | grep name| sed -e 's/< *name *>\([^<]*\)<\/ *name *>/I18N_NOOP(\"\1\");/' >> rc.cpp
|
||||
cat data/knowledge.xml | grep desc | sed -e 's/< *desc *>\([^<]*\)<\/ *desc *>/I18N_NOOP(\"\1\");/' >> rc.cpp
|
||||
cat data/knowledge.xml | grep refitem | sed -e 's/< *refitem *>\([^<]*\)<\/ *refitem *>/I18N_NOOP(\"\1\");/' >> rc.cpp
|
||||
cat data/tools.xml | grep name | sed -e 's/< *name *>\([^<]*\)<\/ *name *>/I18N_NOOP(\"\1\");/' >> rc.cpp
|
||||
cat data/tools.xml | grep desc | sed -e 's/< *desc *>\([^<]*\)<\/ *desc *>/I18N_NOOP(\"\1\");/' >> rc.cpp
|
||||
$(XGETTEXT) *.cpp -o $(podir)/kalzium.pot
|
||||
rm -f rc.cpp # for testing
|
||||
|
||||
messages: rc.cpp
|
||||
$(EXTRACTATTR) --attr=name,origin data/data.xml >> rc.cpp
|
||||
$(EXTRACTRC) --tag-group=none --tag=name data/data.xml >> rc.cpp
|
||||
$(EXTRACTRC) --tag-group=none --tag=name --tag=desc --tag=refitem data/knowledge.xml >> rc.cpp
|
||||
$(EXTRACTRC) --tag-group=none --tag=name --tag=desc data/tools.xml >> rc.cpp
|
||||
$(XGETTEXT) *.cpp -o $(podir)/kalzium.pot
|
||||
@ -0,0 +1,6 @@
|
||||
SUBDIRS = $(AUTODIRS)
|
||||
|
||||
xml_DATA = bg.jpg data.xml knowledge.xml tools.xml
|
||||
|
||||
xmldir = $(kde_datadir)/kalzium/data
|
||||
|
||||
|
After Width: | Height: | Size: 11 KiB |
@ -0,0 +1,23 @@
|
||||
<!ELEMENT kalzium (element+)>
|
||||
<!ELEMENT element (number, name, period, symbol, spectra?, mass, acidicbehaviour, block, date, biologicalmeaning?, group, electronaffinity?, electronegativity?, meltingpoint?, boilingpoint?, isotopes?, density?, ionisationenergy?, radius?, orbits?, oxydation?, family?, abundance?, crystalstructure?)>
|
||||
<!ELEMENT radius (covalent?, atomic?, vdw?, bondxx?, ionic?)>
|
||||
<!ELEMENT ionisationenergy (energy+)>
|
||||
<!ELEMENT isotopes (isotope+)>
|
||||
<!ELEMENT spectra (spectrum+)>
|
||||
<!ELEMENT name ANY>
|
||||
<!ATTLIST name
|
||||
origin CDATA #IMPLIED>
|
||||
<!ELEMENT spectrum ANY>
|
||||
<!ATTLIST spectrum
|
||||
intensity CDATA #IMPLIED
|
||||
wavelength CDATA #IMPLIED
|
||||
aki CDATA #IMPLIED
|
||||
energy1 CDATA #IMPLIED
|
||||
energy2 CDATA #IMPLIED
|
||||
electronegativity1 CDATA #IMPLIED
|
||||
electronegativity2 CDATA #IMPLIED
|
||||
term1 CDATA #IMPLIED
|
||||
term2 CDATA #IMPLIED
|
||||
J1 CDATA #IMPLIED
|
||||
J2 CDATA #IMPLIED>
|
||||
<!ENTITY deg "°">
|
||||
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,283 @@
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<wissen>
|
||||
<item>
|
||||
<name>State of matter</name>
|
||||
<desc>Form of a substance; dependant on form stability and whether it takes up a definite volume: solid, liquid or gaseous.</desc>
|
||||
<references>
|
||||
<refitem>Boiling point</refitem>
|
||||
<refitem>Melting point</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Chemical Symbol</name>
|
||||
<desc>One, two, or three letter abbreviation; set through international convention.</desc>
|
||||
<references>
|
||||
<refitem>Element</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Chromatography</name>
|
||||
<desc>Matter separation in a moving medium (mobile phase) through differentiated absorption on a static medium (stationary phase).</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Distillation</name>
|
||||
<desc>Separation of a liquid solution (homogeneous mix) into its components through evaporation and condensation. In a fractionary distillation the process is repeated several times in a column.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Element</name>
|
||||
<desc>Matter that cannot be broken down into simpler matter. Chemical elements are cornerstones of Materials. Elements consist of atoms that consist of a nucleus of positive protons, neutral neutrons, and a shell of electrons.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Emulsion</name>
|
||||
<desc>Heterogeneous mix of two liquids.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Extraction</name>
|
||||
<desc>Processing a homogeneous or heterogeneous mix to get pure matter.</desc>
|
||||
<references>
|
||||
<refitem>Mix</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Filtering</name>
|
||||
<desc>Separation of a solid matter from a liquid matter or gaseous matter with a filter (porous separation wall).</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Mix</name>
|
||||
<desc>Matter consisting of differentiated matter, combined in non-set ratios. [i]Homogeneous mixes[/i] have a coherent look, [i]heterogeneous mixes[/i] consist of multiple phases.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Accuracy</name>
|
||||
<desc>Consisting of accidental and systematic errors.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Law of Conservation of Mass</name>
|
||||
<desc>During a chemical reaction mass is neither lost nor gained. The sum mass of the material going into the reaction equals the sum of the mass of the products of the reaction.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Law of multiple proportions</name>
|
||||
<desc>An alloy always contains the same elements in the same mass ratio. Should two or more elements bind together then the mass ratio is constant.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Crystallization</name>
|
||||
<desc>Separation of solid, crystalline matter from a solution, or the liquid or gaseous phases.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Solution</name>
|
||||
<desc>Homogeneous mix of multiple pure materials</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Mass</name>
|
||||
<desc>Measurement of an amount of matter.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Matter</name>
|
||||
<desc>All that takes up space and has mass.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Phase</name>
|
||||
<desc>Through chemical composition and physical attributes, homogeneous portion of matter that separated from its environment in its expansion through a surface.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Accuracy and precision</name>
|
||||
<desc>Expressed through standard deviation: Values given over accidental errors.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Correctness</name>
|
||||
<desc>Values given over accidental errors.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>SI-Unit</name>
|
||||
<desc>Measurement unit using International Symbols.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Significant figures</name>
|
||||
<desc>The number of digits which are meaningful in a number.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Standard deviation</name>
|
||||
<desc>An amount with which the precision of a measurement can be estimates.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Suspension</name>
|
||||
<desc>Heterogeneous mix consisting of a liquid and solid matter.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Alloys</name>
|
||||
<desc>Pure matter consisting of multiple elements in a set ratio.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Alpha rays</name>
|
||||
<desc>Rays consisting of alpha particles, consisting of two protons and two neutrons that are emitted from the Atoms of certain radioactive elements.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Atom</name>
|
||||
<desc>Atoms are chemically inseparable and building blocks of matter. Atoms of one kind are called an Element.</desc>
|
||||
<references>
|
||||
<refitem>Element</refitem>
|
||||
<refitem>Electron</refitem>
|
||||
<refitem>Proton</refitem>
|
||||
<refitem>Neutron</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Atomic nucleus</name>
|
||||
<desc>The small, positively-charged center of an Atom, in which Protons and Neutrons are found.</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Atomic Mass</name>
|
||||
<desc>Mass of an atom, taken on a scale where the the mass of a carbon atom is 12u. In elements that consist of different isotopes the mid-range mass of the isotope mix is given.</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
<refitem>Mass</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Isotope</name>
|
||||
<desc>Isotopes are forms of a chemical element whose nuclei have the same atomic number, Z, but different atomic masses, A. The word isotope, meaning at the same place, comes from the fact that all isotopes of an element are located at the same place on the periodic table.</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Spin</name>
|
||||
<desc>The spin is an intrinsic angular momentum associated with microscopic particles. It is a purely quantum mechanical phenomenon without any analogy in classical mechanics. Whereas classical angular momentum arises from the rotation of an extended object, spin is not associated with any rotating internal masses, but is intrinsic to the particle itself.</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Magnetic Moment</name>
|
||||
<desc>The magnetic moment of an object is a vector relating the aligning torque in a magnetic field experienced by the object to the field vector itself. It's measured in units of the nuclear magneton μ[sub]n[/sub]=(5.0507866 ± 0.0000017) 10[sup]-27[/sup] JT[sup]-1[/sup]</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Decay Mode</name>
|
||||
<desc>The decay mode describes a particular way a particle decays. For radioactive decay (the decay of nuclides) the decay modes are:[br] -> alpha decay (emission of a Helium-4 nucleus).[br] -> β[sup]-[/sup] decay (emission of an electron)[br] -> β[sup]+[/sup] decay (emission of a positron) [br] -> electron capture (EC) [br] -> proton emission [br] -> spontaneous fission [br] Typically one decay mode predominates for a particular nuclide.</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Decay Energy</name>
|
||||
<desc>The decay energy is the energy released by a nuclear decay.</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Nuclides</name>
|
||||
<desc>[i]see isotopes[/i]</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
<refitem>Isotone</refitem>
|
||||
<refitem>Nuclear Isomer</refitem>
|
||||
<refitem>Isobars</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Isotone</name>
|
||||
<desc>Two nuclides are isotones if they have the same number N of neutrons.</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
<refitem>Nuclear Isomer</refitem>
|
||||
<refitem>Isobar</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Isobar</name>
|
||||
<desc>Isobars are nuclides having the same mass number, i.e. sum of protons plus neutrons.</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
<refitem>Isotone</refitem>
|
||||
<refitem>Nuclear Isomer</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Nuclear Isomer</name>
|
||||
<desc>A nuclear isomer is a metastable or isomeric state of an atom caused by the excitation of a proton or neutron in its nucleus so that it requires a change in spin before it can release its extra energy. They decay to lower energy states of the nuclide through two isomeric transitions:[br] -> γ- emission (emission of a high-energy photon)[br] -> internal conversion (the energy is used to ionize the atom)[br] Contrast this with the definition of a chemical isomer, the more common use of the word. Also contrast with the meaning of isotope, in which the difference is the number of neutrons in the nucleus. Metastable isomers of a particular atom are usually designated with an "m" (or, in the case of atoms with more than one isomer, 2m, 3m, and so on). This designation is usually placed after the atomic symbol and number of the atom (e.g., Co-58m), but is sometimes placed as a superscript before (e.g., [sup]m[/sup]Co-58 or [sup]58m[/sup]Co).</desc>
|
||||
<references>
|
||||
<refitem>Isotope</refitem>
|
||||
<refitem>Isobar</refitem>
|
||||
<refitem>Isotone</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Beta rays</name>
|
||||
<desc>Rays consisting of electrons that are emitted from Atoms of radioactive elements.</desc>
|
||||
</item>
|
||||
<item>
|
||||
<name>Electron</name>
|
||||
<desc>The electron is a subatomic particle with a mass of m[sub]e[/sub]=(9.1093897 ± 0.0000054)e-31 kg and a negative charge of [i]e[/i]=(1.60217733 ± 0.00000049)e-19 C
|
||||
</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Proton</name>
|
||||
<desc>The proton is a subatomic particle with a mass of m[sub]e[/sub]=(1.6726231 ± 0.0000010) 10[sup]-27[/sup] kg and a positive charge of [i]e[/i]=(1.60217733 ± 0.00000049) 10[sup]-19[/sup] C which occurs in the nucleus of an atom.</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
<refitem>Electron</refitem>
|
||||
<refitem>Neutron</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Neutron</name>
|
||||
<desc>The neutron is a subatomic particle with a mass of m[sub]e[/sub]=(1.6749286 ± 0.0000010) 10[sup]-27[/sup] kg which occurs in the nucleus of an atom.</desc>
|
||||
<references>
|
||||
<refitem>Atom</refitem>
|
||||
<refitem>Electron</refitem>
|
||||
<refitem>Proton</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Cathode Rays</name>
|
||||
<desc>Cathode rays are streams of electrons observed in vacuum tubes, i.e. evacuated glass tubes that are equipped with at least two electrodes, a cathode (negative electrode) and an anode (positive electrode) in a configuration known as a diode.</desc>
|
||||
<references>
|
||||
<refitem>Electron</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Ionic Radius</name>
|
||||
<desc>The Ionic Radius is the radius of a charged atom, a so called ion. The ion can have a positive or a negative charge. The charge of the ion which radius you see is also displayed in Kalzium. A positive ion has less electrons in its shell then the atom, a negative ion has more electrons. Therefore, a postive ion has a smaller radius than its atom and vice versa.</desc>
|
||||
<references>
|
||||
<refitem>Covalent Radius</refitem>
|
||||
<refitem>Atomic Radius</refitem>
|
||||
<refitem>Van der Waals Radius</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Van der Waals Radius</name>
|
||||
<desc>The van der Waals radius of an atom is the radius of an imaginary hard sphere which can be used to model the atom for many purposes. Van der Waals radii are determined from measurements of atomic spacing between pairs of unbonded atoms in crystals.</desc>
|
||||
<references>
|
||||
<refitem>Covalent Radius</refitem>
|
||||
<refitem>Atomic Radius</refitem>
|
||||
<refitem>Ionic Radius</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Atomic Radius</name>
|
||||
<desc>The atomic radius is the distance from the atomic nucleus to the outmost stable electron orbital in a atom that is at equilibrium.</desc>
|
||||
<references>
|
||||
<refitem>Covalent Radius</refitem>
|
||||
<refitem>Van der Waals Radius</refitem>
|
||||
<refitem>Ionic Radius</refitem>
|
||||
</references>
|
||||
</item>
|
||||
<item>
|
||||
<name>Covalent Radius</name>
|
||||
<desc>Covalent radius in chemistry corresponds to half of the distance between two identical atomic nuclei, bound by a covalent bond.</desc>
|
||||
<references>
|
||||
<refitem>Atomic Radius</refitem>
|
||||
<refitem>Ionic Radius</refitem>
|
||||
<refitem>Van der Waals Radius</refitem>
|
||||
</references>
|
||||
</item>
|
||||
</wissen>
|
||||
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,42 @@
|
||||
xml_DATA = abzug.jpg \
|
||||
becherglas.jpg \
|
||||
brechungsmesser.jpg \
|
||||
brenner.jpg \
|
||||
destillierbruecke.jpg \
|
||||
dsc.jpg \
|
||||
erlenmeyerkolben.jpg \
|
||||
exikator.jpg \
|
||||
halter.jpg \
|
||||
heizplatte.jpg \
|
||||
hplc.jpg \
|
||||
kolbenprober.png \
|
||||
korkring.jpg \
|
||||
messzylinder.jpg \
|
||||
moerser.jpg \
|
||||
phpapier.jpg \
|
||||
pileusball.jpg \
|
||||
pipette.jpg \
|
||||
rg-halter.jpg \
|
||||
rg.jpg \
|
||||
rg-staender.jpg \
|
||||
rotationsverdampfer.jpg \
|
||||
rueckflusskuehler.jpg \
|
||||
ruehrfisch.jpg \
|
||||
rundkolben.jpg \
|
||||
scheidetrichter.jpg \
|
||||
schutzbrille.jpg \
|
||||
spatel.jpg \
|
||||
spritzflasche.jpg \
|
||||
thermometer2.jpg \
|
||||
thermometer.jpg \
|
||||
tonschale.jpg \
|
||||
trichter.jpg \
|
||||
trockenrohr.jpg \
|
||||
tropftrichter.jpg \
|
||||
uhrglas.jpg \
|
||||
verteiler.jpg \
|
||||
vollpipette.jpg \
|
||||
waage.jpg \
|
||||
wasserstrahlpumpe.jpg
|
||||
|
||||
xmldir = $(kde_datadir)/kalzium/data/toolpics
|
||||
|
After Width: | Height: | Size: 30 KiB |
|
After Width: | Height: | Size: 30 KiB |
|
After Width: | Height: | Size: 44 KiB |
|
After Width: | Height: | Size: 20 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in new issue