<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.1-Based Variant V1.0//EN" "dtd/kdex.dtd" [
  <!ENTITY skylendar '<application>Skylendar</application>'>
  <!ENTITY kapp "&skylendar;"><!-- replace skylendar here -->
  <!ENTITY % addindex "IGNORE">
  <!ENTITY % English "INCLUDE"><!-- change language only here -->
  
  
  <!-- Do not define any other entities; instead, use the entities
       from kde-genent.entities and $LANG/user.entities. -->
]>
<!-- kdoctemplate v0.8 October 1 1999 
     Minor update to "Credits and Licenses" section on August 24, 2000
     Removed "Revision history" section on 22 January 2001   -->

<!--
This template was designed by: David Rugge davidrugge@mindspring.com
with lots of help from: Eric Bischoff ebisch@cybercable.tm.fr
and Frederik Fouvry fouvry@sfs.nphil.uni-tuebingen.de
of the KDE DocBook team.

You may freely use this template for writing any sort of KDE documentation.
If you have any changes or improvements, please let us know.

In the future, we may want to change from SGML-based DocBook to XML-based
DocBook. To make this change easier, please be careful :
- in XML, the case of the <tags> and attributes is relevant ;
- also, quote all attributes.

Please don't forget to remove all these comments in your final documentation,
thanks ;-).
-->

<!-- ................................................................ -->

<!-- The language must NOT be changed here. -->

<book lang="&language;">

<!-- This header contains all of the meta-information for the document such
as Authors, publish date, the abstract, and Keywords -->

<bookinfo>
<title>The Skylendar Handbook</title>

<authorgroup>
<author>
<firstname>Christophe</firstname>
<othername></othername>
<surname>Gros</surname>
<affiliation>
<address><email>skylendar@yahoo.com</email></address>
</affiliation>
</author>
</authorgroup>

<!-- TRANS:ROLES_OF_TRANSLATORS -->

<copyright>
<year>2002-2003-2004</year>
<holder></holder>
</copyright>
<!-- Translators: put here the copyright notice of the translation -->
<!-- Put here the FDL notice.  Read the explanation in fdl-notice.docbook 
     and in the FDL itself on how to use it. -->
<legalnotice>&FDLNotice;</legalnotice>

<!-- Date and version information of the documentation
Don't forget to include this last date and this last revision number, we
need them for translation coordination !
Please respect the format of the date (DD/MM/YYYY) and of the version
(V.MM.LL), it could be used by automation scripts.
Do NOT change these in the translation. -->

<date>1/10/2004</date>
<releaseinfo>1.3</releaseinfo>

<!-- Abstract about this handbook -->

<abstract>
<para>
&skylendar; is a failry portable and modern design astrology program for KDE 3.1. It includes a state of the art
interface, a powerful data/restrictions sets management, and a SQL database searching/loading/saving
interface. Even if it is portable, &skylendar; has mainly been developed for the Linux/KDE3
environment.
</para>
</abstract>

<!-- This is a set of Keywords for indexing by search engines.
Please at least include KDE, the KDE package it is in, the name
 of your application, and a few relevant keywords. -->

<keywordset>
<keyword>astrology</keyword>
<keyword>astrolog</keyword>
<keyword>kastrolog</keyword>
<keyword>Kapp</keyword>
<keyword>KDE</keyword>
<keyword>SQL</keyword>
<keyword>PostgreSQL</keyword>
<keyword>Sweph</keyword>
<keyword>Linux</keyword>
</keywordset>

</bookinfo>

<!-- The contents of the documentation begin here.  Label
each chapter so with the id attribute. This is necessary for two reasons: it
allows you to easily reference the chapter from other chapters of your
document, and if there is no ID, the name of the generated HTML filenns will vary
from time to time making it hard to manage for maintainers and for the CVS
system. Any chapter labelled (OPTIONAL) may be left out at the author's
discretion. Other chapters should not be left out in order to maintain a
consistent documentation style across all KDE apps. -->

<chapter id="introduction">
<title>Introduction</title>

<!-- 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>
&skylendar; is a fairly portable and modern design astrology program for KDE 3.1, with drag'n'drop,
multi-windowing, animation, printing and SQL database management capabilities.
&skylendar; is also the successor of the now defunct kastrolog 5.4, a KDE port of the famous W.D. Pullen's
 astrolog, an old Windows 3.1 based astrology software. For more info about astrolog, see
 <ulink url="http://www.astrolog.org"></ulink>
 </para>
 <para>
 &skylendar; is built upon the Swiss Ephemeris library (sweph), which uses precomputed ephemeris
 files. This version already provides a set of these ones for the contemporaneous epoch, but additional
 files can be found at: <ulink url="http://skylendar.kde.org/se1"></ulink>.
 </para>
 <para>
 By now, &skylendar; provides Standard Wheel chart, a Data List chart, an Aspects Scan chart, an Objects List,
 a Local Horizon chart, and a Aspects Table chart.
 </para>
 <para>
Although portable, this software has been actually developed for the Linux/KDE3 environment, and
needs the PostgreSQL 7.x RDBMS.
</para>
</chapter>

<chapter id="using-kapp">
<title>Using Skylendar</title>

<!-- This chapter should tell the user how to use your app. You should use as
many sections (Chapter, Sect1, Sect3, etc...) as is necessary to fully document
your application. -->

<sect1 id="overview">
<title>Overview</title>
<para>The &skylendar; main window is basically divided into two vertical parts: an icon tree for the data/restrictions
 sets, subchart management, and a workspace where all the graphical charts are displayed.
</para>
<para>
A data set groups together all the time and place info needed to cast a chart for a person or a
situation. Those sets can be saved into and retrieved from the <acronym>SQL</acronym> database.
</para>
<para>
All the displayed planets or aspects and their orbs, colors, etc... are contained in restrictions
sets. Those sets can be saved into or retrieved from the database like a data set.
</para>
<para>
Before running the application itself, the user must log into the database. The database name, password
and hostname will be asked, like before an ordinary KDE session.
</para>
<remark>The database user's name is not necessarily the one from the system, beware !</remark>
<para>
&skylendar; works according to the drag and drop system. Dragging a data or restrictions set icon, and
dropping it onto a displayed chart will recompute and redisplay the affected chart with respect
to the dragged data.
</para>
<para>
Each displayed chart can manage up to 4 different data and restrictions sets.
The toolbar shows 4 icons, like <guiicon><inlinemediaobject><imageobject>
<imagedata fileref="2.png" format="PNG"/></imageobject></inlinemediaobject></guiicon>,
which selects the affected data for the next drag'n'drop operation.
</para>
<para>
In addition to the data and restrictions sets, the user can manage subcharts icons, i.e. actions
performed on selected data sets in charts, such as hiding/displaying a data set or changing its
subchart type, e.g. Single, Transiting, Directed, Progressed, AddAngle and MulAngle .
</para>
<para>
The <emphasis>AddAngle</emphasis> subcharts will add an arbitrary angle to the longitude of
the available objects. Thus, you can get a <emphasis>Symbolic direction</emphasis> subchart
 if you add 1.0 degree per year, whereas for the <emphasis>MulAngle</emphasis>, this factor
is multiplied with the longitude of the available objects. Thus, you can get an
<emphasis>Harmonic</emphasis> subchart if you use integer values, such as 2.0, 3.0, 7.0, etc...
</para>
<remark>
	Double click on either <guiicon>Add Angle</guiicon> or <guiicon>Mul Angle</guiicon>
icon in order to set the suitable value
</remark>
<para>
A single subchart is the basic subchart type. A single subchart can't send aspects; it only
receives them, unless 2 single and available subcharts remain visible on a chart. Thus,
aspects can be computed between both of them. If only 2 non-single (i.e. transiting,
progressed an directed) available subcharts remains on a chart, the aspects are
naturally computed between these subcharts.
</para>
<para>
Sophisticated queries can be submitted to the database through the data sets search
dialog box. One can search a data set simply by name or by birthdate, sex, comment, type, etc.., or even by values,
i.e. all the data sets that have the planet x in sign y, or the planet x and y linked with the aspect z,
and so on.
 </para>
<para>
<!-- Note that all graphics should be in .png format. Use no gifs because of
patent issues. -->

<screenshot>
<screeninfo>Here's a screenshot of &kapp;</screeninfo>
	<mediaobject>
	  <imageobject>
	    <imagedata fileref="skylendar.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>Screenshot</phrase>
	  </textobject>
	</mediaobject>
</screenshot>
</para>
</sect1>
<sect1 id="data-edition">
<title>Data Edition</title>
<para>
This chapter will show how to create or edit a data/restrictions set.
</para>
<sect2 id="data-set-edition">
<title>Data Set Edition</title>
<para>
The Edit Data dialog box can be invoked with the <guimenu>File</guimenu>
<guimenuitem>New</guimenuitem> menu. It is made of 3 distinct
panels: the first for the general info, the second for the time info and the last one, a place editor.
</para>
<sect3 id="general-info">
<title>General Info</title>
<para>
 The user provides here some basic info such as the person's or situation name, its gender,
 male, female or neutral for a thing or situation. A standard text edition box is also provided
 on the left, so that he can edit some free text, .e.g. a comment, or even a full interpretation.
</para>
<para>
The last required info, the chart type, deserves more explanations : Skylendar proposes a way to
define the type of a chart, e.g. whether it is a birth/beginning or a death/end chart. Other chart types
are possible, and can be created according to the following procedure :
</para>
<itemizedlist>
<listitem><para>Design a 32x32 pixels .png file icon, for example <filename>marriage.png</filename>
</para></listitem>
<listitem><para>Copy this file to <filename>&lt;kdepath&gt;/share/apps/skylendar/pics</filename>,
where &lt;kdepath&gt; is your kde stuff path.</para></listitem>
<listitem><para>Perform the following command:
<prompt>%</prompt><userinput>psql -c "INSERT INTO  TypeIcons (Idx, Name, File)
VALUES(NEXTVAL('TypeIcons_Idx_Seq'), 'Marriage/Association', 'marriage.png');" skylendar skylendar</userinput></para>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="date-time-info">
<title>Date and Time</title>
<para>
This panel allows the user to easily set the person's birth date and time. In addition to these
values, The daylight time saving and time zone can be managed here.
</para>
<para>
<emphasis>The daylight time saving</emphasis> is a common issue in most european countries, where, twice a year,
the local hour is shifted forward or backward. This shift theoretically allows a power saving
for the country. This shift is usually 1 hour, but can be 2 hours, half an hour or other values.
</para>
<para>
Since all the countries don't share the same hour at the same time, <emphasis>the time zone</emphasis> gives the
time shift between GMT and the local hour. Positive values for eastward countries.
</para>
<para>
These values can be set manually when you push the <guibutton>Manually recompute</guibutton>
, or automatically if you select the <guibutton>Automatic</guibutton> radio button. In this case,
the daylight saving and time zone are extracted from the place zone info file.
The <emphasis>Daylight Time Saving</emphasis> can be set manually in hour:minute, like the time zone.
<remark>The zone info file provided with linux don't give the daylight/zone info before 1.1.1970</remark>
</para>
<para>
The longitude positions are often expressed in books as Hour:Minute:Second instead of
Degree:Minute. You can select this format by clicking on the <guibutton>H:M:S Longitude</guibutton>
radio button.
</para>
<para>
The <guibutton>Now</guibutton> obviously sets the date and time values with the current hour.
</para>
</sect3>
<sect3 id="place-info">
<title>Place Editor</title>
<para>
This panel not only allows the user to choose an existing place (.i.e. town, village), but contains
a full place editor.
</para>
<para>
First of all, search for an existing place: insert into the Place name field of the panel, a few indicating characters,
e.g. <quote>ber</quote> for all the cities names containing ber (Berlin, Bern) and press the
<guibutton>Search</guibutton> button. Then click on the wanted place, if any.
</para>
<para>
You can modify the actual values, then press the <guibutton>Modify</guibutton> button. Or delete the entry with the <guibutton>
Delete</guibutton> button. These operations will be performed into the database too.
</para>
<para>
Empty up the Place name, latitude and longitude fields with the <guibutton>Clean</guibutton>
button. Provide your own values and press the <guibutton>New</guibutton> button, and a new place
will be created and saved into the database.
</para>
</sect3>
<sect3 id="keywords-info">
<title>Keywords</title>
<para>
A new info field has been introduced since skylendar 1.4, named <emphasis>Keywords</emphasis>.
Keywords is a free format string, although I strongly recommend a comma separated list of signifiant words,
e.g. for Saddam Hussein: "Dictator, Baath, Irak, Oil, War".
</para>
<para>
Those keywords can be <emphasis>untagged</emphasis>, like above, or <emphasis>tagged</emphasis>, i.e.
 preceded by a 3 or 4 letters identifier and a '=' sign. I propose a collection of predefined tags.
</para>
<para>Those tags, except Illn, are important if you intend to manage AAF files.
(See chapter <link linkend="aaf-skif">AAF versus SKIF</link>, below)</para>
<itemizedlist>
<listitem><para>'Prof=' for the profession. (AAF's "#ATTRB:B=" field)</para></listitem>
<listitem><para>'Chln=' for the number of children. ("#ATTRB:K=" field)</para></listitem>
<listitem><para>'Illn=' for the Illnesses.</para></listitem>
<listitem><para>'Src='  for the source document of your data. ("#SRC:" field)</para></listitem>
<listitem><para>'Via='  for more info about data origin. ("#VIA:" field)</para></listitem>
<listitem><para>'Cqu='  see below . ("#QGZ:" third field)</para></listitem>
</itemizedlist>
<para>As for the "#QGZ:" second field, a quality level for the data, the Keywords group box of the data set dialog box provides
a list of possible choice.</para>
<itemizedlist>
<listitem><para>'Direct' when you directly initiate the event. (Code 0, not accepted by AAF)</para></listitem>
<listitem><para>'Register' when data extracted from an official document, birth register, hospital, etc... (Code 1*)</para></listitem>
<listitem><para>'Fambook' when data extracted from family book. (Code 1F)</para></listitem>
<listitem><para>'Astrologer' when data computed by an astrologer. (Code 1)</para></listitem>
<listitem><para>'Mother' when data provided by mother. (Code 2M)</para></listitem>
<listitem><para>'Father' when data provided by father. (Code 2F)</para></listitem>
<listitem><para>'Personal' when data provided by personal statement or autobiography. (Code 2P)</para></listitem>
<listitem><para>'Biography' when data extracted from a biography. (Code 2B)</para></listitem>
<listitem><para>'Partner' when data provided by a friend or partner. (Code 2R)</para></listitem>
<listitem><para>'Possibility' when not sure about the source of data. (Code 3)</para></listitem>
<listitem><para>'Speculative' when data is pure speculation. (Code 4)</para></listitem>
</itemizedlist>
<para>The popup menu will insert the selected item as a string prepended with 'Orig='. For example,
 Orig=Father .</para>
</sect3>
</sect2>
</sect1>
<sect1 id="search-data">
<title>Searching for a Data Set</title>
<para>
Existing data sets can be stored into the database with the <guimenu>Data</guimenu>-&gt;<guimenuitem>Save</guimenuitem>
menu. Later, the stored data sets can be retrieved with the <interface>Search for data</interface> dialog box.<guimenu>File</guimenu>-&gt;<guimenuitem>Search for data</guimenuitem>
menu.
</para>
<para>
If you press the <guibutton>Search</guibutton> button, without having filled up the search field,
all the available data sets will be displayed. Otherwise, only data sets whose the name contained the provided
indicating characters will appear.
</para>
<para>
There is even a smarter way for data sets seraching. Thie dialog box allows you to enter
partial <acronym>SQL</acronym> requests, i.e. the conditions after the WHERE statement. Select the <guibutton>
By SQL statement</guibutton> button.
</para>
<para>Here are a few examples:</para>
<itemizedlist>
<listitem><programlisting>Data.Name LIKE 'John\%'</programlisting>
<remark>(All the people whose the name begins with John)</remark>
<para>.</para>
</listitem>
<listitem><programlisting>Data.Name ~* 'john' AND Data.Gender ='M'</programlisting>
<remark>(All the guys whose the name contains 'John' or 'john')</remark>
<para>.</para>
</listitem>
<listitem>
<programlisting>Data.Name ~* 'anna' AND Data.Gender = 'F' AND EXTRACT(YEAR FROM Data.Birthday) &gt;= 1900 AND EXTRACT(YEAR FROM Data.Birthday) &lt;= 1980</programlisting>
<remark>(All the ladies whose the name contains 'anna' and born between 1900 and 1980)</remark>
<para>.</para>
</listitem>
<listitem>
<programlisting>Data.Gender ='N' AND Data.ChartType = 2 AND Data.Comment ~* 'accident'</programlisting>
<remark>(All the deadly accidents)</remark>
<para>.</para>
</listitem>
<listitem><para>
<programlisting>Data.Keywords LIKE '\%Prof=Doctor\%'</programlisting><remark>(All the doctors)</remark></para></listitem>
</itemizedlist>
<sect2 id="searching-by-values">
<title>Searching by Values</title>
<para>The <interface>Search for Data</interface> dialog box also allows the user to search by values, thank to the VDV view.
Clicking on the <guibutton>by VDV</guibutton> button, and a column of predefined operators and arguments button
become active. (See below).</para>
<para>
The <acronym>VDV</acronym> (Values Data View) manages a list of data sets associated with a table containing additional info
which permits the relationship with 2 extra tables : Obj and Asp.
</para>
<para>
Obj contains a list of planetary positions for each <acronym>VDV</acronym> row, whereas Asp contains
a list of aspects for each <acronym>VDV</acronym> row.
</para>
<para>
The Asp, Obj and VDV rows are filled when, for a given subchart, the <guiicon>Extract &amp; Save</guiicon>
icon is dropped onto the regarded chart. Since additional data is saved, the corresponding
data set is automatically saved too. Don't forget to save the actual restriction
set if not already done; otherwise the extract &amp; save doesn't start.
</para>
<para>
After having saved the data, Extract &amp; Save adds - if needed - an icon to the Data sets icons list.
When the subchart has been modified during an animation or an incremental time shift,
a new data set and icon is created, with a suggestive name, such as <emphasis>Direction xx for yy</emphasis>,
where xx is an arbitrary number and yy the parent data set.
</para>
<para>
Within the database, all those relationships are protected by PostgreSQL <emphasis>triggers</emphasis>,
e.g. you can't delete a saved subchart data set when its parent still exists.
Moreover, when a restrictions set is deleted, its references are discarded into the VDV.
</para>
<para>
In order to help you, 4 Database functions have been introduced : <emphasis>TObj(), TAsp(), TRetr()</emphasis>
 and <emphasis>THouse()</emphasis>.
</para>
<para>
<itemizedlist>
<listitem>
<para>
<function>Bool TObj(<parameter>&lt;DataIdx&gt;</parameter>, <parameter>&lt;Object&gt;</parameter>, <parameter>&lt;Sign Number&gt;</parameter>)</function>
</para>
<para> Returns <returnvalue>TRUE</returnvalue> if, for the Data set <parameter>&lt;DataIdx&gt;</parameter>, <parameter>&lt;Object&gt;</parameter>
 exists and is in sign <parameter>&lt;Sign Number&gt;</parameter>.
 Where <parameter>&lt;Object&gt;</parameter> is the object short name .e.g. 'Mar' for Mars,
and <parameter>&lt;Sign Number&gt;</parameter>, the sign number e.g. 1 for Aries and 12 for Pisces.
Example:</para>
<programlisting>  TObj(DataIdx, 'Plu', 6)</programlisting>
<remark>(if Pluto in Virgo)</remark><para>.</para>
</listitem>
<listitem>
<para>
<function>Bool TAsp(<parameter>&lt;DataIdx&gt;</parameter>, <parameter>&lt;Aspect&gt;</parameter>, <parameter>&lt;Object 1&gt;</parameter>, <parameter>&lt;Object 2 or empty&gt;</parameter>)</function>
</para>
<para> Returns <returnvalue>TRUE</returnvalue> if, for the Data set <parameter>&lt;DataIdx&gt;</parameter>, the objects <parameter>&lt;Object 1&gt;</parameter> and <parameter>&lt;Object 2&gt;</parameter> &lt; are linked with the aspect <parameter>&lt;Aspect&gt;</parameter>.
Example: </para><programlisting>  TAsp(DataIdx, 'Con', 'Mar', 'Sat')</programlisting> <remark>(if conjunction Mars-Saturn)</remark>
<programlisting>  TAsp(DataIdx, 'Tri', 'Ura', '  ')</programlisting>
<remark>(if trine Uranus-anything)</remark><para>.</para>
</listitem>
<listitem>
<para>
<function>Bool TRetr(<parameter>&lt;DataIdx&gt;</parameter>, <parameter>&lt;Object&gt;</parameter>)</function>
</para>
<para> Returns <returnvalue>TRUE</returnvalue> if, for the Data set <parameter>&lt;DataIdx&gt;</parameter> <parameter>&lt;Object&gt;</parameter> exists and is retrograde.
Example: </para>
<programlisting>  TRetr(DataIdx, 'Mer')</programlisting>
<remark>(if Mercury retrograde)</remark>
<para>.</para>
</listitem>
<listitem>
<para>
<function>Bool THouse(<parameter>&lt;DataIdx&gt;</parameter>, <parameter>&lt;Object&gt;</parameter>, <parameter>&lt;House Number&gt;</parameter>)</function>
</para>
<para> Returns <returnvalue>TRUE</returnvalue> if, for the Data set <parameter>&lt;DataIdx&gt;</parameter> <parameter>&lt;Object&gt;</parameter> exists and is in house <parameter>&lt;House Number&gt;</parameter>
Example:</para>
<programlisting>  THouse(DataIdx, 'Moo', 11)</programlisting>
<remark>(if moon in 11th house)</remark>
<para>.</para>
</listitem>
</itemizedlist>
</para>
<para>
Those functions can be chained between classical logical operators like AND, OR, NOT. Examples:
</para>
<programlisting>TObj(DataIdx, 'Ven', 1) AND TAsp(DataIdx, 'Squ', 'Ven', 'Jup')</programlisting>
<remark>(Venus in aries square Jupiter)</remark>
<programlisting>(TObj(DataIdx, 'Sun', 4) OR TObj(DataIdx, 'Sun', 10)) AND THouse(DataIdx, 'Sun', 2)</programlisting>
<remark>(Sun in Cancer or Capricornus and in house 2)</remark>
<para>.</para>
<para>The standard <acronym>SQL</acronym> syntax is obviously available, and classical WHERE statements
are possible, such as:</para>
<programlisting>DataIdx IN (SELECT DataIdx FROM Obj WHERE Id = 'Mer' AND Lat &lt; 0.0)</programlisting>
<remark>(all the data sets where Mercury below the ecliptic)</remark>
<programlisting>DataIdx IN (SELECT DataIdx FROM Asp WHERE AspId = 'Con' AND Objs = 'Moo-Nep' AND Pos = 'S')</programlisting>
<para><remark>(all the Data sets having a separating conjunction Moon-Neptune)</remark></para>
</sect2>
</sect1>
<sect1 id="edit-countries">
<title>Countries Edition</title>
<para>
This dialog box allows the user to create and modify a country and its zoneinfo associated file.
Invoke the <guimenu>File</guimenu>-&gt;<guimenuitem>Edit Countries</guimenuitem> menu item
in order to get this dialog box. The <guibutton>...</guibutton> will open a file dialog box, which
will permit you to select the zone info file. A last field has been added, which contains the country code,
such as F for France, D for Germany, GB for England, etc... This country code is useful if you intend to convert
from/to AAF files. See below.
</para>
<para>
Example of country: <emphasis>Germany</emphasis> zone info file: <filename>Europe/Berlin</filename>.
</para>
</sect1>
<sect1 id="SKIF-files">
<title>SKIF files management</title>
<para>
<acronym>SKIF</acronym> means SKylendar Interchange File. It's a data file format, based on the
 <acronym>XML</acronym>/Unicode technology, which allows the user to save and load files containing
 several datasets.
</para>
<para>
  Click on the <guiicon>Open</guiicon> icon and a classical file dialog box will appear. Select a
.skif file, and if everything fine, a dataset edition dialog box will be displayed whenever a dataset
  has been extracted from the <acronym>skif</acronym> file. Thus, you can check or modify the given info.
</para>
<para>
SKIF files are also accepted as arguments on the command line.
</para>
<para>
However, if the .skif file contains an unknow chart type, an unknown country or place, a validation
dialog box will appear. Select either another type of chart, create or edit the unjnown country
and click the <guibutton>Next</guibutton> button. Then the dataset edition doalog box will follow,
with the edited chart type and country.
</para>
<para>
<remark>Don't forget to edit the provided place if not found in your database !</remark>
</para>
<para>
  The reverse process is possible when you click on the <guiicon>Save</guiicon> icon. A question dialog
  box will appear, that will give you the choice between either to save the selected dataset, or to
  save all the present datasets, except Now.
</para>
<sect2 id="skif-utility">
<title>The skif utility</title>
<para>An utility <filename>skif</filename> is provided with the distribution. It's a
<acronym>perl</acronym> script that converts any .kst (kastrolog/astrolog), or <acronym>AAF</acronym>
 data files into .skif files. This utility can also convert any .skif file into AAF file.</para>
<para><filename>skif</filename> uses the <filename>skif.pm</filename> perl module.
Don't forget to copy it into a suitable directory.</para>
<para>Synopsis: <userinput>skif [--help] [--version] [--dbcode] [file...]</userinput></para>
<sect3 id="aaf-skif">
<title>AAF versus SKIF files</title>
<para>The AAF/97 astrology file format has been popular for several years, especially in Germany. For more info
  about the AAF format, see <ulink url="http://astrologix.de/aaf"></ulink>. Unfortunately, the
  documentation is only in german.</para>
<para>The SKIF 1.1 format supports the AAF A-B-C data groups, even if no official validation has been
  performed so far. The country management of this format is quite different from the skif system.
  AAF uses an up to 3 letters code, whereas skif utilizes the full name of the country. Thus,
  skif manages a country name/code equivalence file named <filename>.skif.db</filename>,
  located in your home directory. If this file is not present, or invoked with --dbcode, skif will
  ask you for a db name, username and host name, and will create <filename>.skif.db</filename>
  for you.</para>
  <para></para>
</sect3>
</sect2>
</sect1>
<sect1 id="siblings">
<title>Siblings</title>
<para>
Let's regard as an example the Mr John Doe's case. You have saved his birth dataset, and also
the ones for his marriage and car accident. Those datasets are independant, i.e. you can freely
delete any of them.
</para>
<para>
But if you save with Extract and Save e.g. the planetary positions for his birth, the directing
and transiting ones for respectively his marriage and car accident, the marriage and car accident datasets
are bound to his birth dataset. Both marriage and car accident datasets are called
<emphasis>siblings</emphasis> of his birth dataset.
</para>
<para>
In the Dataset Search dialog box, the <guibutton>Siblings</guibutton> exists, that allows you to search
for all the siblings to the first displayed dataset. In addition, the <guibutton>Delete</guibutton>
permits you to delete either the stored planetary positions for the resulting sibling datasets, or even
the datasets themselves.
<remark>
The latter operation is dangerous ! Be careful when you delete your datasets with this option.
</remark>
</para>
<sect2 id="dumpval">
<title>Dump Values</title>
<para>
If you have got a lot of datasets and want to Extract &amp; Save all the values from thoses sets, you can use the Dump Value option.
For all the displayed datasets, Dump Values automatically computes their corresponding values according to the Default Restrictions Set and
strores them into the database.
</para>
</sect2>
</sect1>
<sect1 id="chart-exportation">
<title>Chart Exportation</title>
<para>&skylendar; can export its charts, i.e. save the drawing of the chart into
  a file. For now, &skylendar; can save the chart only in SVG (Scalable Vector Graphics) format.
  Select the <guimenuitem>Export Chart</guimenuitem> and a file dialog box appears.
  Select or create the wanted .svg chart and the current chart is saved into this file.
  <remark>The Sketch application can read and edit SVG files if you need.</remark></para>
</sect1>
<sect1 id="direct-values-retrieval">
<title>Direct values retrieval</title>
<para>
The users often want to retrieve computed astrological values for further use. They can oviously Extract &amp; Save the
wanted values and retrieve them with a SELECT on the database, but they can also use a more direct way through the <acronym>DCOP</acronym>
interface of Skylendar. <acronym>DCOP</acronym> is a KDE specific protocol for accessing internal data in an application.
</para>
<para>
When run, Skylendar creates a skylendar-intf <acronym>DCOP</acronym> server that, in turn, creates the so-called "val" query object.
This object proposes 11 methods for data retrieval.
</para>
<itemizedlist>
<listitem><para><programlisting>int NbCharts</programlisting></para></listitem>
<listitem><para><programlisting>bool LockChart &lt;int&gt;</programlisting></para></listitem>
<listitem><para><programlisting>UnlockChart &lt;int&gt;</programlisting></para></listitem>
<listitem><para><programlisting>string GetChartName</programlisting></para></listitem>
<listitem><para><programlisting>int NbRings</programlisting></para></listitem>
<listitem><para><programlisting>string GetRingType &lt;int&gt;</programlisting></para></listitem>
<listitem><para><programlisting>bool IfObj &lt;int&gt; &lt;string&gt;</programlisting></para></listitem>
<listitem><para><programlisting>double GetVal &lt;int&gt; &lt;string&gt; &lt;int&gt;</programlisting></para></listitem>
<listitem><para><programlisting>double GetLong &lt;int&gt; &lt;string&gt;</programlisting></para></listitem>
<listitem><para><programlisting>string GetAspect &lt;int&gt;</programlisting></para></listitem>
<listitem><para><programlisting>double GetMidPoint &lt;string&gt; &lt;string&gt;</programlisting></para></listitem>
</itemizedlist>
<para>
<programlisting>NbCharts</programlisting> will return the number of present charts in Skylendar.
</para>
<para>
Before using a chart, you must lock it. <programlisting>LockChart</programlisting> will lock the chart with the
given number. 0 is the first chart number. It will return FALSE if it can't lock the chart.
</para>
<para>
After having used a chart, don't forget to unlocj it with <programlisting>UnlockChart</programlisting>.
</para>
<para>
<programlisting>GetChartName</programlisting> will return the name of the locked chart.
</para>
<para>
<programlisting>NbRings</programlisting> will return the number of active rings on the locked chart.
</para>
<para>
<programlisting>GetRingType</programlisting> will return the short name of the type of the given ring.
</para>
<para>
<programlisting>IfObj</programlisting> will tell you whether the given object (i.e. planet, cusp, star, etc...) is available or not.
</para>
<para>
<programlisting>GetVal</programlisting> will return, for the given ring number, the decimal value of the nth value of the given object name.
Longitude is 0, latitude 1, distance 2, speed 3, etc...
</para>
<para>
<programlisting>GetLong</programlisting> will return the longitude of the given object for the given ring number.
</para>
<para>
<programlisting>GetAspect</programlisting> will return a coded string for the given aspect number. Number 0 for the first
aspect, and string null when aspect not available.
</para>
<para>
<programlisting>GetMidPoint</programlisting> will return the decimal value for the midpoint between the 2 given object
short names.
</para>
<sect2 id="examples">
<title>Examples</title>
<para>This example uses the <command>dcop</command> utility, that can be invoked from a shell prompt. Other <acronym>DCOP</acronym>
exist for languages like perl. See the KDE bindings package for more info.</para>
<para><userinput>dcop skylendar-intf val NbChart</userinput></para>
<para><prompt>2</prompt></para>
<para><userinput>dcop skylendar-intf val LockChart 1</userinput></para>
<para><prompt>true</prompt></para>
<para><remark>Locks the second chart</remark></para>
<para><userinput>dcop skylendar-intf val GetChartName</userinput></para>
<para><prompt>Standard Wheel Chart for Now</prompt></para>
<para><userinput>dcop skylendar-intf val NbRings</userinput></para>
<para><prompt>1</prompt></para>
<para><userinput>dcop skylendar-intf val GetRingType 0</userinput></para>
<para><prompt>Sgl</prompt></para>
<para><remark>Single wheeel chart</remark></para>
<para><userinput>dcop skylendar-intf val IfObj 0 Mar</userinput></para>
<para><prompt>true</prompt></para>
<para><remark>Mars is available on ring 0</remark></para>
<para><userinput>dcop skylendar-intf val GetVal 0 Mar 2</userinput></para>
<para><prompt>0.535637</prompt></para>
<para><remark>Mars-Earth distance</remark></para>
<para><userinput>dcop skylendar-intf val GetLong 0 Mar</userinput></para>
<para><prompt>336.636802</prompt></para>
<para><userinput>dcop skylendar-intf val GetAspect 0</userinput></para>
<para><prompt>Sun Con Mer 0.303790 (Good) Separating</prompt></para>
<para><remark>Sun-Mercury conjunction. Actual orb: 0.3037, good accuracy, separating aspect</remark></para>
<para><userinput>dcop skylendar-intf val GetMidPoint Moo Jup</userinput></para>
<para><prompt>119.34563</prompt></para>
<para><userinput>dcop skylendar-intf val UnlockChart</userinput></para>
<para><prompt></prompt></para>
</sect2>
</sect1>
<sect1 id="standard-wheel-chart">
<title>The Standard Wheel Chart</title>
<para>
In a wheel chart, the 4 possible data sets are displayed as corresponding concentric rings of planets. See
above for a graphical example. This chart also provides 1 or 2 data columns which displays additional
info, such as exact longitude/latitude values for the planets, current houses longitudes, used
houses system, restrictions set for the current ring, etc...
</para>
<para>
if wanted, a subring showing the first ring's decans, solar, lunar or nodal houses can be drawn
as well.
</para>
 <para>
 Below the wheel chart, a table of the current aspects is optionally printed, which symbolically displays
 the found aspects, followed by the '&lt;', '=' and '&gt;' characters, for applying, exact and separating aspects,
 plus its actual orb.
 </para>
 <para>
 On each corner of the concentric rings are displayed captions containing the name, date and place
extracted from the data set, plus a number from 1 to 4, showing the ring level the data set belongs to;
1 for the outermost ring.
 </para>
 <para>
 The size of the glyphs (i.e. planet symbol) changes with respects to the total number of
 displayed planets and rings.
 </para>
 <para>
 In the middle of the concentric rings dwells an aspects disk, where all the available aspects
 are drawn. Aspects are always displayed according to the subcharts rules.
 </para>
 <para> The chart can be oriented with respect to the Ascendant/Descendant line, or to
 the vernal point (0.0 Aries). See <guimenu>Chart</guimenu>-&gt;<guimenuitem>Edit parameters</guimenuitem></para>
 <sect2 id="x-point">
 <title>The X point</title>
 <para>A good astrologer sometimes notice that there are sensitive points on a chart,
 i.e. zodiac degrees where, when planets are conjunct to them, seem to be activated
 and produce effects. Those points are often empty.</para>
 <para>If you want to materialize one of those points, select the X point in your
 current objects restrictions list, and click on your std wheel chart where dwells
 your sensitive point. A X object appears and its current aspects are displayed.</para>
 </sect2>
 <sect2 id="planets-rank">
 <title>Planets Rank</title>
 <para>When you select the "planets rank" option, a ranked list of the ten major planets is displayed
 according to a score based algorithm. For each planet, a score is increased by a chosen value whenever the considered
 planet satisfies a given condition. Those conditions are the following ones:</para>
 <orderedlist>
 <listitem><para>If the planet is conjunct to the Ascendant, Mid-Heaven or Sun (except Mercury and Venus).</para></listitem>
 <listitem><para>If the planet is conjunct to the Descendant or Nadir.</para></listitem>
 <listitem><para>If the planet is master (ruler) of I or X.</para></listitem>
 <listitem><para>If the planet is in its own sign.</para></listitem>
 <listitem><para>If the planet is conjunct to the master of I or X.</para></listitem>
 <listitem><para>If the planet is master of another.</para></listitem>
 <listitem><para>If the planet is in aspect with another.</para></listitem>
 <listitem><para>If the planet is exhalted.</para></listitem>
 </orderedlist>
 <para>The increasing values are members of all the restrictions sets, and can be changed according to
 your taste.</para>
 <para>The obtained scores are displayed beneath the ranked planets symbols.</para>
 </sect2>
</sect1>
<sect1 id="standard-text-list-chart">
<title>The Standard Text List Chart</title>
<para>Whereas the std wheel chart displays its data in and around a wheel, the Standard Text
  List Chart prints its data as tables of numbers or positions, like on a sheet of
  paper. Actually, this chart has been designed so that it can be printed on paper like
  any ordianry word processor document.</para>
<para>
This text list, in addition to the latitude and longitude values, also displays the distance to Sun in Astronomical Units (.e.g. 1 UA = Earth &lt;-&gt; Sun distance),
and the speeds in latitude, longitude (in deg/day) and distance (in AU/day) for the given body.
Optionnaly, the Std Text List Chart
  also provides a list of midpoints of the first visible ring, and conjunctions to the objects of the second rings
  with those midpoints. A list of Risings, Culminating and Settings hours for
  the active planets and stars is also proposed, and also the time and place of the next/previous global and local eclipses,
  and a list of aspects configurations e.g. Grand Trine, Yod, T-Square etc...</para>
</sect1>

<sect1 id="aspects-scan-list-chart">
<title>The Aspects Scan List Chart</title>
<para>
	Drop the Aspects Scan List icon onto the active window and &skylendar; will search for all the
	aspect exact dates between the first single and the second non-hidden ring, like in the aspects ring.
	This search will be performed along the second ring day. The noticeable aspects between the same planet
	are reported along the comment column.
</para>
<para>
	If you double-click on the <guiicon>Aspects Scan List icon</guiicon>, a dialog box will appear, that will allow
	you to select the scan time span, i.e. current day, month, year, or for several years.
</para>
<para>
	This scan only occurs between a static (typically natal) ring and a moving ring.
	This is called a <emphasis>Simple scan</emphasis>. However, <emphasis>when the first single and second ring are the same,
	and both have "Single" as subtype</emphasis>, the search is called <emphasis>Dual Scan</emphasis>.
	The yielded list shows the mutual aspects between the planets, stars, etc... during the given time span.
	The lunar phases, the sign and direction changes are also reported.
</para>
<para>
	When scanning, a small modeless dialog box will be displayed, with a progression bar and a
	<guibutton>Stop</guibutton> button, that will stop the scan process and display the uncomplte
	aspects list.
</para>
<para>
	The aspects list displays the aspect's exact date and hour, the secondary ring's involved
	object, the sign it belongs to, within [] or () whether the object is retro or not. The aspect name
	and first involved object name and sign are given as well. Objects direction changes dates are also
	provided.
</para>
<remark>
	This aspects list is computed asynchronously, within a real multitasking process, i.e. you can launch
	and aspects scan for several years and go on working on other charts, even animations.
</remark>
<sect2 id="active-lines">
<title>Active lines</title>
<para>
Both Standard Text List and Aspects Scan List Charts, display <emphasis>active lines</emphasis>, i.e. lines
beginning with a red '¤'. Whenever you click one of those lines, a corresponding DataSet is created, whose the date
and time matches with the regarded event.
</para>
</sect2>
</sect1>

<sect1 id="local-horizon-chart">
<title>Local Horizon Chart</title>
<para>
This chart displays an image of the local sky as though you were looking southward, straight ahead. An horizontal line shows
the local horizon, whereas 3 vertical lines shows the eastern, southern and western geographical directions.
</para>
</sect1>
<sect1 id="objects-list">
<title>Objects List</title>
<para>
This chart displays a list of all the objects (i.e. planets, cusps, virtual planets, stars, etc...) and all the aspects,
with its glyphs (if available), short names and names. The aspects list also displays the corresponding angles.
</para>
</sect1>
<sect1 id="ephemeris">
<title>Ephemeris</title>
<para>
The Ephemeris list displays a list of 10 planetary positions computed every day at midnight, ZeroGMT. ZeroGMT is a
virtual place situated at 0:0E 0:0N, with GMT as the ruling country. Don't forget to define them into the DB.
</para>
<para>
You can choose the time span for the scanning like for the Aspects List Chart. Double click on the Ephemeris Icon,
and you will get a suitable dialog box.
</para>
</sect1>
<sect1 id="astro-graph">
<title>Astro-Graph</title>
<para>
This chart is similar to the Jim Lewis' Astro*Carto*Graphy map, i.e. a map of the earth is displyed,
crossed by straight or curved lines. Those lines show the longitudes of where on Earth at that time
the regarded objects are on the midheaven or on the nadir, and the latitude of where the planets
actually appeared at zenith, and also the longitude of where the objects appeared on the ascendant
and descendant is displayed.
</para>
<para>
If you click on a region on the chart, a zooming is performed, and displays more and more precise details
of the Earth. From a 128x zooming, the local cities on the map are also displayed.
Press the <keycap>Ctrl</keycap> key while clicking on the map, and the map will be zoomed out.
</para>
</sect1>
<sect1 id="chart-parameters">
<title>Chart Parameters</title>
<para> You can modify the style and/or the appareance of a chart with the following parameters.
Thses options can be set either with the <guimenu>Chart</guimenu>
<guimenuitem>Edit Parameters</guimenuitem>, or by a popup menu activated when the right mouse
button is pressed.</para>
<itemizedlist>
<listitem><para><guibutton>Dynamically Resize</guibutton></para><para>The chart is resized (shrinked or enlarged)
	when its window is itself resized.</para></listitem>
<listitem><para><guibutton>Central Aspect Ring</guibutton></para><para>When on, the aspects are drawn in the center
	of the Wheel Chart.</para></listitem>
<listitem><para><guibutton>Aspects Frame</guibutton></para><para>When on, a table of all the computed aspects is displayed beneath
	the Wheel Chart.</para></listitem>
<listitem><para><guibutton>Displays Seconds</guibutton></para><para>When on, the longitudes are displayed with the seconds.</para></listitem>
<listitem><para><guibutton>Displays Midpoints</guibutton></para><para>In the Std List Chart, the midpoints between the regarded rings are displayed.</para></listitem>
<listitem><para><guibutton>Sort Aspects List by Influence</guibutton></para><para>When on, the Aspects Frame displays its aspects sorted according to an
influence rule. The power of an aspect is given by the sum of its two planets' influences, multiplied with
the aspect's influence pondered by its actual orb.</para></listitem>
</itemizedlist>
</sect1>

<sect1 id="skylendar-features">
<title>More &skylendar; features</title>

<para>Animations</para>
<para>
Animations start/stop <guiicon><inlinemediaobject>
	  <imageobject>
	    <imagedata fileref="animation.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>Aminations start/stop</phrase>
	  </textobject>
</inlinemediaobject></guiicon> This icon switches the display in animation/normal mode.
The time step is determined by the jump base and the jump number.
</para>
<para>Jump base and rate</para>
<para>
Jump base and rate <guiicon><inlinemediaobject>
	  <imageobject>
	    <imagedata fileref="anim2.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>Jump base or jump rate</phrase>
	  </textobject>
</inlinemediaobject></guiicon> These icons permit the selection of the animation base, .i.e. in minutes,
hours, days, months, years, etc..., and the rate, from 1 to 9.
</para>
<para>Direction</para>
<para>
Direction of the animations <guiicon><inlinemediaobject>
	  <imageobject>
	    <imagedata fileref="direction.png" format="PNG"/>
	  </imageobject>
	  <textobject>
	    <phrase>Direction of the animation</phrase>
	  </textobject>
</inlinemediaobject></guiicon> This icon permits the selection of the animation direction, .i.e.
from past to future, or from future to past.
</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 Skylendar window</title>
<para></para>

<sect2>
<title>The File Menu</title>
<para>
<variablelist>
 <varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>o</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>
<guimenuitem>Open</guimenuitem>
</menuchoice></term>
<listitem><para><action>Read a SKIF file.</action></para></listitem>
</varlistentry>
 <varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>s</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>
<guimenuitem>Save</guimenuitem>
</menuchoice></term>
<listitem><para><action>Save the selected data set into a SKIF file.</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>p</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>
<guimenuitem>Print</guimenuitem>
</menuchoice></term>
<listitem><para><action>Prints the current chart</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>S</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>
<guimenuitem>Search for Data</guimenuitem>
</menuchoice></term>
<listitem><para><action>Serach for Data Sets</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>File</guimenu>
<guimenuitem>Search for Restrictions Sets</guimenuitem>
</menuchoice></term>
<listitem><para><action>Search for Restrictions sets</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>File</guimenu>
<guimenuitem>Edit Countries</guimenuitem>
</menuchoice></term>
<listitem><para><action>Edit Countries Data</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>q</keycap></keycombo>
</shortcut>
<guimenu>File</guimenu>
<guimenuitem>Quit</guimenuitem>
</menuchoice></term>
<listitem><para><action>Quits</action> &kapp;</para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2>
<title>The Chart Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Chart</guimenu>
<guimenuitem>Create Chart/Standard Chart</guimenuitem>
</menuchoice></term>
<listitem><para><action>Creates a new standard chart</action></para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Chart</guimenu>
<guimenuitem>Edit Parameters</guimenuitem>
</menuchoice></term>
<listitem><para><action>Edit current chart parameters</action></para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenuitem>Duplicate Window</guimenuitem>
</menuchoice></term>
<listitem><para><action>Duplicate current window</action></para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<guimenu>Chart</guimenu>
<guimenuitem>Export Chart</guimenuitem>
</menuchoice></term>
<listitem><para><action>Export the current chart into a .svg file.</action></para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Shift</keycap><keycap>+</keycap></keycombo>
</shortcut>
<guimenu>Chart</guimenu>
<guimenuitem>Manually Increment Animation</guimenuitem>
</menuchoice></term>
<listitem><para><action>Increment the displayed chart of n minutes/hours/days etc..., according to the animation parameters</action></para></listitem>
</varlistentry>

<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Shift</keycap><keycap>-</keycap></keycombo>
</shortcut>
<guimenu>Chart</guimenu>
<guimenuitem>Manually Decrement Animation</guimenuitem>
</menuchoice></term>
<listitem><para><action>Decrement the displayed chart of n minutes/hours/days etc..., according to the animation parameters</action></para></listitem>
</varlistentry>

</variablelist>
</para>
</sect2>
<sect2>
<title>The Data Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>N</keycap></keycombo>
</shortcut>
<guimenu>Data</guimenu>
<guimenuitem>New</guimenuitem>
</menuchoice></term>
<listitem><para><action>Creates a new data set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo>
</shortcut>
<guimenu>Data</guimenu>
<guimenuitem>New Restrictions set</guimenuitem>
</menuchoice></term>
<listitem><para><action>Creates a new restrictions set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Data</guimenu>
<guimenuitem>Save</guimenuitem>
</menuchoice></term>
<listitem><para><action>Saves into the database the current data or restrictions set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Data</guimenu>
<guimenuitem>Edit</guimenuitem>
</menuchoice></term>
<listitem><para><action>Edits the selected data or restrictions set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Data</guimenu>
<guimenuitem>Delete</guimenuitem>
</menuchoice></term>
<listitem><para><action>Deletes on list and into database the selected data or restrictions set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>Ctrl</keycap><keycap>Ins</keycap></keycombo>
</shortcut>
<guimenu>Data</guimenu>
<guimenuitem>Duplicate</guimenuitem>
</menuchoice></term>
<listitem><para><action>Duplicates the selected data or restrictions set</action></para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2>
<title>The Windows Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Windows</guimenu>
<guimenuitem>Tile windows</guimenuitem>
</menuchoice></term>
<listitem><para><action>Tiles the windows on the screen</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Windows</guimenu>
<guimenuitem>Cascade Windows</guimenuitem>
</menuchoice></term>
<listitem><para><action>Reorganizes as cascade, the windows on the escrren </action></para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2>
<title>The Settings Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guimenuitem>Save Settings</guimenuitem>
</menuchoice></term>
<listitem><para><action>Saves global &skylendar; settings</action></para></listitem>
</varlistentry>
<varlistentry>
<term><menuchoice>
<guimenu>Settings</guimenu>
<guimenuitem>Configure &skylendar;</guimenuitem>
</menuchoice></term>
<listitem><para><action>Edits the global &skylendar; settings</action></para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
<sect2>
<title>The Help Menu</title>
<para>
<variablelist>
<varlistentry>
<term><menuchoice>
<shortcut>
<keycombo><keycap>F1</keycap></keycombo>
</shortcut>
<guimenu>Help</guimenu>
<guimenuitem>Contents</guimenuitem>
</menuchoice></term>
<listitem><para><action>Displays the &skylendar;'s user guide</action></para></listitem>
</varlistentry>
</variablelist>
</para>
</sect2>

</sect1>
</chapter>

<chapter id="developers">
<title>Developer's Guide to Skylendar</title>

<!-- (OPTIONAL) A Programming/Scripting reference chapter should be
used for apps that use plugins or that provide their own scripting hooks
and/or development libraries. -->

<para>
Not written
</para>

<!-- Use refentries to describe APIs.  Refentries are fairly complicated and you
should consult the docbook reference for further details. The example below was
taken from that reference and shortened a bit for readability. -->

</chapter>

<chapter id="faq">
<title>Questions and Answers</title>

<!-- (OPTIONAL but recommended) This chapter should include all of the silly
(and not-so-silly) newbie questions that fill up your mailbox. This chapter
should be reserved for BRIEF questions and answers! If one question uses more
than a page or so then it should probably be part of the
"Using this Application" chapter instead. You should use links to
cross-reference questions to the parts of your documentation that answer them.
This is also a great place to provide pointers to other FAQ's if your users
must do some complicated configuration on other programs in order for your
application work. -->

&reporting.bugs;
&updating.documentation;

<qandaset id="faqlist">
<qandaentry>
<question>
<para>Can I contribute to your project ?</para>
</question>
<answer>
<para>Of course you can, but first of all make sure you really want to contribute, and not
to send me hollow promises. I work in C++ with QT3/KDE3 interface. In order to help me, you
ought to know at least the C++ language and read the sources, possibly with the help of KDevelop.
Then, and only then, I shall be able to regard you as a potential contributor.
You can also act as a beta tester or as a documentation writer/correcter/translater<link linkend="commands">Commands
Section</link> for the answer.</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>What about a port in java.</para>
</question>
<answer>
<para>Java is maybe an excellent language, but as already said, I work in C++. I don't
need a java port, but new charts, relevant contribution, smart debugging, etc... for the current
software.
</para>
</answer>
</qandaentry>
<qandaentry>
<question>
<para>Can I use skylendar as an internet astrological server ?</para>
</question>
<answer>
<para>Skylendar has been designed for amateur or even professional astrologers, not for
merchants of omens.
</para>
</answer>
</qandaentry>
</qandaset>
</chapter>

<chapter id="command-line-options">
<title>Command-line Options</title>

<para>When &skylendar; is started from the command-line, various options
can be specified to modify its behavior.</para>

<para>Synopsis:
<userinput>&skylendar; [-d dataset] [-r restrictions set] [skif file, skif file,...]</userinput></para>
<variablelist>
<varlistentry>
<term><option>-d</option> <parameter>Data Set</parameter></term>
<listitem><para><action>Preload the given Data Set</action></para></listitem>
</varlistentry>
<varlistentry>
<term><option>-r</option> <parameter>Restrictions Set</parameter></term>
<listitem><para><action>>Preload the given Restrictions Set</action></para></listitem>
</varlistentry>
</variablelist>
<para>Example:
<prompt>%</prompt> <userinput>&skylendar; -d "John T. Doe" -d "George W. Bush" -r "With Stars"</userinput>
</para>
</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>
&kapp;
</para>
<para>
Program copyright 2002-2003 Christophe Gros <email>skylendar@yahoo.com</email>
</para>
<para>
Contributors:
<itemizedlist>
<listitem><para>Konqui the KDE Dragon <email>konqui@kde.org</email></para>
</listitem>
<listitem><para>Tux the Linux Penguin <email>tux@linux.org</email></para>
</listitem>
</itemizedlist>
</para>

<para>
Documentation copyright 2002-2003 Christophe Gros <email>skylendar@yahoo.com</email>
</para>

<!-- TRANS:CREDIT_FOR_TRANSLATORS -->

&underFDL;               <!-- FDL: do not remove. Commercial development should -->
<!-- replace this with their copyright and either remove it or re-set this.-->

<!-- Determine which license your application is licensed under, 
     and delete all the remaining licenses below:

     (NOTE:  All documentation are licensed under the FDL, 
     regardless of what license the application uses) -->

&underGPL;        	 <!-- GPL License -->

</chapter>

<appendix id="installation">
<title>Installation</title>

<sect1 id="getting-skylendar">
<title>How to obtain Skylendar</title>

<para>
&skylendar; can be found at
<ulink url="http://skylendar.kde.org"></ulink>, the home page for this project. </para>
</sect1>

<sect1 id="requirements">
<title>Requirements</title>

<!--
List any special requirements for your application here. This should include:
.Libraries or other software that is not included in kdesupport,
kdelibs, or kdebase.
.Hardware requirements like amount of RAM, disk space, graphics card
capabilities, screen resolution, special expansion cards, etc.
.Operating systems the app will run on. If your app is designed only for a
specific OS, (you wrote a graphical LILO configurator for example) put this
information here.
-->

<para>
In order to successfully use &skylendar;, you need KDE 3.0.x and PostgreSQL 7.1. or morex
</para>

<para>
All required libraries as well as &skylendar; itself can be found
at <ulink url="http://skylendar.kde.org">The &skylendar; home page</ulink>.
</para>

<!-- For a list of updates, you may refer to the application web site
or the ChangeLog file, or ... -->
<para>
You can find a list of changes at <ulink url="http://skylendar.kde.org/ChangeLog">http://skylendar.kde.org/ChangeLog</ulink>.
</para>
</sect1>

<sect1 id="compilation">
<title>Compilation and Installation</title>

<para>
In order to compile and install &skylendar; on your system, type the following in the base
directory of the Icon Editor distribution:
<screen width="40">
<prompt>%</prompt> <userinput>./configure</userinput>
<prompt>%</prompt> <userinput>make</userinput>
<prompt>%</prompt><userinput>su</userinput>
<prompt>#</prompt> <userinput>make install</userinput>
</screen>
</para>
<para>
You will certainly need to install the suitable font and database.
Read the PostgresSQL documentation and the related files in the distribution.
You should also read the DESERVEWARE file.
</para>
</sect1>

<sect1 id="configuration">
<title>Configuration</title>
<para></para>
</sect1>

</appendix>

&documentation.index;
</book>
<!--
Local Variables:
mode: sgml
sgml-minimize-attributes:nil
sgml-general-insert-case:lower
sgml-indent-step:0
sgml-indent-data:nil
End:
-->













