[office/calligraplan/3.3] doc: Backport docs from master
Dag Andersen
null at kde.org
Fri Jan 8 13:14:58 GMT 2021
Git commit 9d29fc6dff86bf340c87f6cbb127d35ce2c3a520 by Dag Andersen.
Committed on 08/01/2021 at 12:24.
Pushed by danders into branch '3.3'.
Backport docs from master
A +1 -0 doc/.kateconfig
A +14 -0 doc/CMakeLists.txt
A +- -- doc/Icon-edit-delete.png
A +- -- doc/Icon-go-first.png
A +- -- doc/Icon-view-time-schedule-baselined-add.png
A +- -- doc/Icon-view-time-schedule-calculus.png
A +- -- doc/Icon-view-time-schedule-child-insert.png
A +- -- doc/Icon-view-time-schedule-insert.png
D +0 -39 doc/announce-2.1.txt
A +8 -0 doc/contexthelp.docbook
A +110 -0 doc/costbreakdownstructureeditor.docbook
A +1267 -0 doc/creatingodtreporttemplates.docbook
A +28 -0 doc/creatingproject.docbook
A +153 -0 doc/definitions.docbook
D +- -- doc/dependencyeditor1.png
D +- -- doc/gantt1.png
A +11 -0 doc/guidelines.docbook
A +73 -0 doc/index.docbook
D +- -- doc/intro1.png
A +31 -0 doc/introduction.docbook
D +- -- doc/kplatowork1.png
A +44 -0 doc/mainworkspace.docbook
A +10 -0 doc/managingresources.docbook
A +98 -0 doc/milestoneganttview.docbook
A +- -- doc/plan_accounteditor.png
A +- -- doc/plan_criticalpath.png
A +- -- doc/plan_dependencyeditor.png
A +- -- doc/plan_pertresult.png
A +- -- doc/plan_project_perf_chart.png
A +- -- doc/plan_resourceeditor.png
A +- -- doc/plan_resourceeditor_config.png
A +- -- doc/plan_scheduleeditor.png
A +- -- doc/plan_scheduleeditor_config.png
A +- -- doc/plan_schedulinglog.png
A +- -- doc/plan_taskeditor.png
A +- -- doc/plan_taskeditor_config.png
A +- -- doc/plan_taskexecutionview.png
A +- -- doc/plan_taskexecutionview_config.png
A +- -- doc/plan_taskprogressdialog.png
A +- -- doc/plan_tasks_perf_chart.png
A +- -- doc/plan_taskstatusview.png
A +- -- doc/plan_taskstatusview_config.png
A +- -- doc/plan_work_space.png
A +- -- doc/plan_workandvacation.png
A +18 -0 doc/planintroduction.docbook
A +33 -0 doc/projectperformanceview.docbook
A +5 -0 doc/reports.docbook
A +122 -0 doc/reportsgeneratorview.docbook
A +110 -0 doc/resourceassignmentganttview.docbook
A +104 -0 doc/resourceassignmentview.docbook
A +222 -0 doc/resourceeditor.docbook
D +- -- doc/resourceeditor1.png
D +- -- doc/scheduleeditor1.png
A +278 -0 doc/scheduleseditor.docbook
D +- -- doc/scripting1.png
A +11 -0 doc/startupview.docbook
A +132 -0 doc/taskdependencyeditorgraphical.docbook
A +6 -0 doc/taskdependencyeditorlist.docbook
A +369 -0 doc/taskeditor.docbook
D +- -- doc/taskeditor1.png
D +- -- doc/taskexecution1.png
A +173 -0 doc/taskexecutionview.docbook
A +106 -0 doc/taskganttview.docbook
A +36 -0 doc/taskperformanceview.docbook
A +214 -0 doc/taskstatusview.docbook
A +163 -0 doc/usingtheviews.docbook
A +50 -0 doc/viewsandeditors.docbook
A +87 -0 doc/workandvacationeditor.docbook
https://invent.kde.org/office/calligraplan/commit/9d29fc6dff86bf340c87f6cbb127d35ce2c3a520
diff --git a/doc/.kateconfig b/doc/.kateconfig
new file mode 100644
index 00000000..651757bb
--- /dev/null
+++ b/doc/.kateconfig
@@ -0,0 +1 @@
+kate: indent-width 2
diff --git a/doc/CMakeLists.txt b/doc/CMakeLists.txt
new file mode 100644
index 00000000..058221b4
--- /dev/null
+++ b/doc/CMakeLists.txt
@@ -0,0 +1,14 @@
+
+find_package(ECM ${REQUIRED_ECM_VERSION} QUIET)
+if(NOT ECM_FOUND)
+ return()
+endif()
+
+set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${ECM_MODULE_PATH})
+include(KDEInstallDirs)
+
+macro_optional_find_package(KF5 ${REQUIRED_KF5_VERSION} QUIET COMPONENTS DocTools)
+
+if(KF5_FOUND)
+ kdoctools_create_handbook(index.docbook INSTALL_DESTINATION ${KDE_INSTALL_DOCBUNDLEDIR}/en SUBDIR calligraplan)
+endif()
diff --git a/doc/Icon-edit-delete.png b/doc/Icon-edit-delete.png
new file mode 100644
index 00000000..936de215
Binary files /dev/null and b/doc/Icon-edit-delete.png differ
diff --git a/doc/Icon-go-first.png b/doc/Icon-go-first.png
new file mode 100644
index 00000000..cf458716
Binary files /dev/null and b/doc/Icon-go-first.png differ
diff --git a/doc/Icon-view-time-schedule-baselined-add.png b/doc/Icon-view-time-schedule-baselined-add.png
new file mode 100644
index 00000000..24c9a54e
Binary files /dev/null and b/doc/Icon-view-time-schedule-baselined-add.png differ
diff --git a/doc/Icon-view-time-schedule-calculus.png b/doc/Icon-view-time-schedule-calculus.png
new file mode 100644
index 00000000..b1d9abdd
Binary files /dev/null and b/doc/Icon-view-time-schedule-calculus.png differ
diff --git a/doc/Icon-view-time-schedule-child-insert.png b/doc/Icon-view-time-schedule-child-insert.png
new file mode 100644
index 00000000..ee8f5e89
Binary files /dev/null and b/doc/Icon-view-time-schedule-child-insert.png differ
diff --git a/doc/Icon-view-time-schedule-insert.png b/doc/Icon-view-time-schedule-insert.png
new file mode 100644
index 00000000..fc15b1d0
Binary files /dev/null and b/doc/Icon-view-time-schedule-insert.png differ
diff --git a/doc/announce-2.1.txt b/doc/announce-2.1.txt
deleted file mode 100644
index 5c2daa93..00000000
--- a/doc/announce-2.1.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-<A general summary>
-
-User interface:
-Many new views has been added to simplify data entry, project execution and analyzes, like:
-* Introduction that includes a small tutorial to get you started.
-* Separate tree view based editors for editing tasks, resources and cost structures.
-* Graphical- and list based task dependency editors.
-* Task status views for inspecting and modifying task progress.
-* Schedules view to handle scheduling. It supports critical path and PERT analyzes.
-
-Views are listed in a configurable view selector docker. Most views are also configurable,
-making it possible to tailor the ui to the users particular needs.
-
-Earned value management:
-KPlato can now calculate and display performance indexes, BCWS, BCWP, and ACWP
-for the whole project or for individual tasks or group of tasks.
-
-Scheduling:
-User can select if resource overbooking should be allowed or avoided.
-PERT distribution based on optimistic-, pessimistic- and most likely estimates.
-It is possible to re-schedule the project from a specified time based on the
-current performance, to cater for changes like additional tasks or resource availability changes.
-
-Scripting:
-Scripting is provided via the common Calligra scripting interface.
-Scripts are provided that can:
-* Import resources from a KPlato file.
-* Export and import resource assignments.
-This makes it possible to coordinate resource usage between projects.
-
-
-Work flow support:
-It is possible to issue "work packages" from KPlato to the resources in the project.
-A work package is task information issued to a particular resource. The resource
-can then use KPlatoWork to access the task information, and report status/progress back to the project.
-KPlatoWork is similar to a pim todo view and handles all (KPlato) tasks the resource is assigned to.
-
-Export filter:
-Export to icalendar format makes it possible to handle tasks as todos in pim applications.
diff --git a/doc/contexthelp.docbook b/doc/contexthelp.docbook
new file mode 100644
index 00000000..c6d003af
--- /dev/null
+++ b/doc/contexthelp.docbook
@@ -0,0 +1,8 @@
+<sect2><title/>
+<para>Many functions and views have help and hints that can be displayed with the <emphasis>What's This</emphasis> function.
+</para>
+<para>You can activate it with the menu entry <menuchoice><guimenu>Help</guimenu><guimenuitem>WhatsThis</guimenuitem></menuchoice> or keyboard shortcut <keycombo>&Shift;<keycap>F1</keycap></keycombo>.
+</para>
+<para>In dialogs it is activated by pressing the <varname>?</varname> in the dialogs title bar.
+</para>
+</sect2>
diff --git a/doc/costbreakdownstructureeditor.docbook b/doc/costbreakdownstructureeditor.docbook
new file mode 100644
index 00000000..8d50c0d3
--- /dev/null
+++ b/doc/costbreakdownstructureeditor.docbook
@@ -0,0 +1,110 @@
+<sect2><title/>
+<sect3 id="description12"><title>Description</title>
+ <para>
+ The Cost Breakdown Structure Editor is used to create, edit, and delete accounts.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_accounteditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>Accounts can be connected to by tasks and resources to accumulate costs from those tasks and resources.
+ </para>
+ <para>The default account accumulates costs incurred from tasks that are not connected to an account.
+ </para>
+</sect3>
+<sect3 id="toolbar13"><title>Toolbar</title>
+ <para>The toolbar provides the means to create and delete accounts:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Account</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create an account. The new account is inserted after the selected account. If no account is selected, the new account is appended at the top level.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add Subaccount</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a sub-account. The new account is appended as a child to selected account.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Delete</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected account.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data14"><title>Editing data</title>
+ <para>Data can be edited inline as described <link linkend="using-the-views">here</link>.
+ </para>
+ <para>The following columns are available:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the account.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Description</para>
+ </entry>
+ <entry>
+ <para>The description of the account.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/creatingodtreporttemplates.docbook b/doc/creatingodtreporttemplates.docbook
new file mode 100644
index 00000000..f174064b
--- /dev/null
+++ b/doc/creatingodtreporttemplates.docbook
@@ -0,0 +1,1267 @@
+<sect2><title/>
+<sect3 id="description1"><title>Description</title>
+ <para>Open Document Text report templates are regular ODT files that can be designed using any ODT word processor like <emphasis>Calligra Words</emphasis> or <emphasis>LibreOffice Writer</emphasis>. The technique used is to use <emphasis>user field</emphasis> variables to hold references to the information that shall be fetched from the project. The variables are called <emphasis>User Fields</emphasis> in <emphasis>Writer</emphasis> and can be found under <menuchoice><guimenu>Insert</guimenu><guisubmenu>Field</guisubmenu><guimenuitem>More Fields</guimenuitem><guimenuitem>Variables</guimenuitem><guimenuitem>User Fields</guimenuitem></menuchoice>. In <emphasis>Words</emphasis> they are called <emphasis>Custom Variables</emphasis> and can be found under <menuchoice><guimenu>Text Editing docker</guimenu><guisubmenu>Variable</guisubmenu><guimenuitem>Custom</guimenuitem></menuchoice>.
+ </para>
+ <para>The easiest way to create a new report template is to modify an existing one as all user fields are defined.
+ </para>
+</sect3>
+<sect3 id="user-field-variables"><title>User Field Variables</title>
+ <sect4 id="variables"><title>Variables</title>
+ <para>The variables are used to enable the generator to extract data from the project.
+ </para>
+ <para>A variable can be a reference to a single data field, a reference to table data or a reference to chart data.
+ </para>
+ <sect5><title>Single Data Field</title>
+ <para>A single data field variable has the following format:
+ </para>
+ <para><replaceable>data group name</replaceable>.<replaceable>property</replaceable> = <replaceable>property identifier</replaceable>
+ </para>
+ <para>where:
+ </para>
+ <itemizedlist>
+ <listitem><para><replaceable>data group name</replaceable> can be tr, project or schedule (see below).</para></listitem>
+ <listitem><para><replaceable>property</replaceable> makes the user field name unique.</para></listitem>
+ <listitem><para><replaceable>property identity</replaceable> identifies the property in the data group.</para></listitem>
+ </itemizedlist>
+ </sect5>
+ <sect5><title>Table Data</title>
+ <para>A table in a report template consists of a variable to specify the data table to use.
+ </para>
+ <para>The variable name must start with <replaceable>table</replaceable> (⪚ tableTasks) and the variable value must be the name of the data table (⪚ tasks).
+ </para>
+ <para>Immediately after the variable, a table must be inserted and columns filled with user field variables that specify which properties to fetch from the table specified above. These variables must have names that start with the name of the table variable above.
+ </para>
+ <para>These variables have the following format:
+ </para>
+ <para>tableTasks.<replaceable>property</replaceable> = <replaceable>property identifier</replaceable>
+ </para>
+ <para>where:
+ </para>
+ <itemizedlist>
+ <listitem><para><guilabel>property</guilabel> makes the user field name unique.</para></listitem>
+ <listitem><para><guilabel>property identifier</guilabel> identifies the property in the data group.</para></listitem>
+ </itemizedlist>
+ </sect5>
+ <sect5><title>Chart Data</title>
+ <para>A chart in a report template consists of a variable to specify the data to use in the chart.
+ </para>
+ <para>The variable name must start with <replaceable>chart</replaceable> (⪚ chartBudgetCost) and the variable value specifies the data group and values to populate the chart.
+ </para>
+ <para>The variable has the following format (note the semicolons):
+ </para>
+ <para><replaceable>name</replaceable> = <replaceable>data group</replaceable>; values=<replaceable>comma separated list of data properties</replaceable>;
+ </para>
+ <para>where:
+ </para>
+ <itemizedlist>
+ <listitem><para><replaceable>name</replaceable> must start with <guilabel>chart</guilabel> (⪚ chartBudgetCost)</para></listitem>
+ <listitem><para><replaceable>data group</replaceable></para></listitem>
+ <listitem><para><guilabel>comma separated list of data properties</guilabel> identifies the properties in the data group.</para></listitem>
+ </itemizedlist>
+ <para>E.g.:
+ </para>
+ <para>chartBudget = project; values=bcws cost, bcwp cost, acwp cost;
+ </para>
+ </sect5>
+ </sect4>
+ <sect4 id="translated-labels"><title>Translated Labels</title>
+ <para>Translated labels enable us to produce general report templates that can be used in different languages.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Variable Name</guilabel></entry>
+ <entry><guilabel>Variable Value</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>tr.project</para>
+ </entry>
+ <entry>
+ <para>Project</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.manager</para>
+ </entry>
+ <entry>
+ <para>Manager</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.schedule</para>
+ </entry>
+ <entry>
+ <para>Schedule</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.bcws</para>
+ </entry>
+ <entry>
+ <para>BCWS</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.bcwp</para>
+ </entry>
+ <entry>
+ <para>BCWP</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.acwp</para>
+ </entry>
+ <entry>
+ <para>ACWP</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.spi</para>
+ </entry>
+ <entry>
+ <para>SPI</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>tr.cpi</para>
+ </entry>
+ <entry>
+ <para>CPI</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ </sect4>
+ <sect4 id="project-values"><title>Project Values</title>
+ <para>Shows values from the main project.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Variable Name</guilabel></entry>
+ <entry><guilabel>Variable Value</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>project.name</para>
+ </entry>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the project</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.manager</para>
+ </entry>
+ <entry>
+ <para>Manager</para>
+ </entry>
+ <entry>
+ <para>The name of the project manager</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.bcwscost</para>
+ </entry>
+ <entry>
+ <para>BCWS Cost</para>
+ </entry>
+ <entry>
+ <para>Cost based Budgeted Cost of Work Scheduled</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.bcwpcost</para>
+ </entry>
+ <entry>
+ <para>BCWP Cost</para>
+ </entry>
+ <entry>
+ <para>Cost based Budgeted Cost of Work Performed</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.acwpcost</para>
+ </entry>
+ <entry>
+ <para>ACWP Cost</para>
+ </entry>
+ <entry>
+ <para>Cost based Actual Cost of Work Performed</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.spicost</para>
+ </entry>
+ <entry>
+ <para>SPI Cost</para>
+ </entry>
+ <entry>
+ <para>Cost based Schedule Performance Index</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.cpicost</para>
+ </entry>
+ <entry>
+ <para>CPI Cost</para>
+ </entry>
+ <entry>
+ <para>Cost based Cost Performance Index</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.bcwseffort</para>
+ </entry>
+ <entry>
+ <para>BCWS Effort</para>
+ </entry>
+ <entry>
+ <para>Effort based Budgeted Cost of Work Scheduled</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.bcwpeffort</para>
+ </entry>
+ <entry>
+ <para>BCWP Effort</para>
+ </entry>
+ <entry>
+ <para>Effort based Budgeted Cost of Work Performed</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.acwpeffort</para>
+ </entry>
+ <entry>
+ <para>ACWP Effort</para>
+ </entry>
+ <entry>
+ <para>Effort based Actual Cost of Work Performed</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.spieffort</para>
+ </entry>
+ <entry>
+ <para>SPI Effort</para>
+ </entry>
+ <entry>
+ <para>Effort based Schedule Performance Index</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>project.cpieffort</para>
+ </entry>
+ <entry>
+ <para>CPI Effort</para>
+ </entry>
+ <entry>
+ <para>Effort based Cost Performance Index</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ </sect4>
+ <sect4 id="schedule-values"><title>Schedule Values</title>
+ <para>Shows values from the current schedule.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Variable Name</guilabel></entry>
+ <entry><guilabel>Variable Value</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>schedule.name</para>
+ </entry>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the schedule</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.state</para>
+ </entry>
+ <entry>
+ <para>State</para>
+ </entry>
+ <entry>
+ <para>Scheduling state</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.direction</para>
+ </entry>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>Scheduling direction</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.overbooking</para>
+ </entry>
+ <entry>
+ <para>Overbooking</para>
+ </entry>
+ <entry>
+ <para>Overbooking</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.distribution</para>
+ </entry>
+ <entry>
+ <para>Distribution</para>
+ </entry>
+ <entry>
+ <para>Distribution</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.plannedstart</para>
+ </entry>
+ <entry>
+ <para>Planned Start</para>
+ </entry>
+ <entry>
+ <para>Planned Start</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.plannedfinish</para>
+ </entry>
+ <entry>
+ <para>Planned Finish</para>
+ </entry>
+ <entry>
+ <para>Planned Finish</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.scheduler</para>
+ </entry>
+ <entry>
+ <para>Scheduler</para>
+ </entry>
+ <entry>
+ <para>Scheduler</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.granularity</para>
+ </entry>
+ <entry>
+ <para>Granularity</para>
+ </entry>
+ <entry>
+ <para>Granularity</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>schedule.mode</para>
+ </entry>
+ <entry>
+ <para>Mode</para>
+ </entry>
+ <entry>
+ <para>Scheduling mode (Auto or Manual)</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ </sect4>
+ <sect4 id="tables"><title>Tables</title>
+ <para>Supported table types:
+ </para>
+ <itemizedlist>
+ <listitem><para>tasks</para></listitem>
+ <listitem><para>taskstatus</para></listitem>
+ <listitem><para>schedules</para></listitem>
+ <listitem><para>projects</para></listitem>
+ </itemizedlist>
+ <para>To create a table, place a variable just before a table in your template file. The variable name identifies the table and must start with <guilabel>table</guilabel>, ⪚ <guilabel>tableTaskStatus</guilabel>.
+ </para>
+ <para>The value of the variable is used to point to the data to be fetched and must be one of the supported tables listed above, ⪚ <guilabel>taskstatus</guilabel>.
+ </para>
+ <para>You then put variables inside the table cells with name and value from the table below.
+ </para>
+ <para>Note that the schedules table supports the values described in <link linkend="schedule-values">Schedule Values</link> above.
+ </para>
+ <para>The projects, tasks and taskstatus tables supports the following values:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Variable Name</guilabel></entry>
+ <entry><guilabel>Variable Value</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.name</para>
+ </entry>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the task or project</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.wbscode</para>
+ </entry>
+ <entry>
+ <para>WBS Code</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.type</para>
+ </entry>
+ <entry>
+ <para>Type</para>
+ </entry>
+ <entry>
+ <para>Type of task</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.responsible</para>
+ </entry>
+ <entry>
+ <para>Responsible</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.allocation</para>
+ </entry>
+ <entry>
+ <para>Allocation</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.estimatetype</para>
+ </entry>
+ <entry>
+ <para>Estimate Type</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.calendar</para>
+ </entry>
+ <entry>
+ <para>Calendar</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.estimate</para>
+ </entry>
+ <entry>
+ <para>Estimate</para>
+ </entry>
+ <entry>
+ <para>Most likely estimate</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.optimistic</para>
+ </entry>
+ <entry>
+ <para>Optimistic</para>
+ </entry>
+ <entry>
+ <para>Optimistic ratio</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.pessimistic</para>
+ </entry>
+ <entry>
+ <para>Pessimistic</para>
+ </entry>
+ <entry>
+ <para>Pessimistic ratio</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.risk</para>
+ </entry>
+ <entry>
+ <para>Risk</para>
+ </entry>
+ <entry>
+ <para>Estimate uncertainty</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.constraint</para>
+ </entry>
+ <entry>
+ <para>Constraint</para>
+ </entry>
+ <entry>
+ <para>Type of time constraint</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.constraintstart</para>
+ </entry>
+ <entry>
+ <para>Constraint Start</para>
+ </entry>
+ <entry>
+ <para>Constraint start time</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.constraintend</para>
+ </entry>
+ <entry>
+ <para>Constraint End</para>
+ </entry>
+ <entry>
+ <para>Constraint finish time</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.runingaccount</para>
+ </entry>
+ <entry>
+ <para>Running Account</para>
+ </entry>
+ <entry>
+ <para>Account for running costs</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.startupaccount</para>
+ </entry>
+ <entry>
+ <para>Startup Account</para>
+ </entry>
+ <entry>
+ <para>Account for startup cost</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.startupcost</para>
+ </entry>
+ <entry>
+ <para>Startup Cost</para>
+ </entry>
+ <entry>
+ <para>The cost incurred at startup of the task</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.shutdownaccount</para>
+ </entry>
+ <entry>
+ <para>Shutdown Account</para>
+ </entry>
+ <entry>
+ <para>Account for shutdown cost</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.shutdowncost</para>
+ </entry>
+ <entry>
+ <para>Shutdown Cost</para>
+ </entry>
+ <entry>
+ <para>The cost incurred at shutdown of the task</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.description</para>
+ </entry>
+ <entry>
+ <para>Description</para>
+ </entry>
+ <entry>
+ <para>Task description</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.expected</para>
+ </entry>
+ <entry>
+ <para>Expected</para>
+ </entry>
+ <entry>
+ <para>Calculated most likely estimate</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.optimistic</para>
+ </entry>
+ <entry>
+ <para>Optimistic</para>
+ </entry>
+ <entry>
+ <para>Calculated optimistic estimate</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.pessimistic</para>
+ </entry>
+ <entry>
+ <para>Pessimistic</para>
+ </entry>
+ <entry>
+ <para>Calculated pessimistic estimate</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.starttime</para>
+ </entry>
+ <entry>
+ <para>Start Time</para>
+ </entry>
+ <entry>
+ <para>Scheduled start time</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.endtime</para>
+ </entry>
+ <entry>
+ <para>End Time</para>
+ </entry>
+ <entry>
+ <para>Scheduled finish time</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.duration</para>
+ </entry>
+ <entry>
+ <para>Duration</para>
+ </entry>
+ <entry>
+ <para>Scheduled duration</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.earlystart</para>
+ </entry>
+ <entry>
+ <para>Early Start</para>
+ </entry>
+ <entry>
+ <para>Earliest possible start</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.earlyfinish</para>
+ </entry>
+ <entry>
+ <para>Early Finish</para>
+ </entry>
+ <entry>
+ <para>Earliest possible finish</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.latestart</para>
+ </entry>
+ <entry>
+ <para>Late Start</para>
+ </entry>
+ <entry>
+ <para>Latest possible start</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.latefinish</para>
+ </entry>
+ <entry>
+ <para>Late Finish</para>
+ </entry>
+ <entry>
+ <para>Latest possible finish</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.positivefloat</para>
+ </entry>
+ <entry>
+ <para>Positive Float</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.freefloat</para>
+ </entry>
+ <entry>
+ <para>Free Float</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.negativefloat</para>
+ </entry>
+ <entry>
+ <para>Negative Float</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.startfloat</para>
+ </entry>
+ <entry>
+ <para>Start Float</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.finishfloat</para>
+ </entry>
+ <entry>
+ <para>Finish Float</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.assignaments</para>
+ </entry>
+ <entry>
+ <para>Assignments</para>
+ </entry>
+ <entry>
+ <para>Resource assignments</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.varianceest</para>
+ </entry>
+ <entry>
+ <para>Variance (Est)</para>
+ </entry>
+ <entry>
+ <para>Calculated estimate variance</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.variancedur</para>
+ </entry>
+ <entry>
+ <para>Variance (Dur)</para>
+ </entry>
+ <entry>
+ <para>Calculated duration variance</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.optimisticdur</para>
+ </entry>
+ <entry>
+ <para>Optimistic (Dur)</para>
+ </entry>
+ <entry>
+ <para>Calculated optimistic duration</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.pessimisticdur</para>
+ </entry>
+ <entry>
+ <para>Pessimistic (Dur)</para>
+ </entry>
+ <entry>
+ <para>Calculated pessimistic duration</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.status</para>
+ </entry>
+ <entry>
+ <para>Status</para>
+ </entry>
+ <entry>
+ <para>Task status as shown in Task Status View</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.completion</para>
+ </entry>
+ <entry>
+ <para>% Completed</para>
+ </entry>
+ <entry>
+ <para>Task completion</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.plannedeffort</para>
+ </entry>
+ <entry>
+ <para>Planned Effort</para>
+ </entry>
+ <entry>
+ <para>Planned effort</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.actualeffort</para>
+ </entry>
+ <entry>
+ <para>Actual Effort</para>
+ </entry>
+ <entry>
+ <para>Actual effort</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.remaningeffort</para>
+ </entry>
+ <entry>
+ <para>Remaining Effort</para>
+ </entry>
+ <entry>
+ <para>Remaining effort</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.plannedcost</para>
+ </entry>
+ <entry>
+ <para>Planned Cost</para>
+ </entry>
+ <entry>
+ <para>Planned cost</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.actualcost</para>
+ </entry>
+ <entry>
+ <para>Actual Cost</para>
+ </entry>
+ <entry>
+ <para>Actual cost</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.actualstart</para>
+ </entry>
+ <entry>
+ <para>Actual Start</para>
+ </entry>
+ <entry>
+ <para>Actual start</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.started</para>
+ </entry>
+ <entry>
+ <para>Started</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.actualfinish</para>
+ </entry>
+ <entry>
+ <para>Actual Finish</para>
+ </entry>
+ <entry>
+ <para>Actual finish</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.finished</para>
+ </entry>
+ <entry>
+ <para>Finished</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.schedulingstatus</para>
+ </entry>
+ <entry>
+ <para>Scheduling Status</para>
+ </entry>
+ <entry>
+ <para>Scheduling status</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.bcws</para>
+ </entry>
+ <entry>
+ <para>BCWS</para>
+ </entry>
+ <entry>
+ <para>Budgeted Cost of Work Scheduled (cost based)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.bcwp</para>
+ </entry>
+ <entry>
+ <para>BCWP</para>
+ </entry>
+ <entry>
+ <para>Budgeted Cost of Work Performed (cost based)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.acwp</para>
+ </entry>
+ <entry>
+ <para>ACWP</para>
+ </entry>
+ <entry>
+ <para>Actual Cost of Work Performed (cost based)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.spi</para>
+ </entry>
+ <entry>
+ <para>SPI</para>
+ </entry>
+ <entry>
+ <para>Schedule Performance Index</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.critical</para>
+ </entry>
+ <entry>
+ <para>Critical</para>
+ </entry>
+ <entry>
+ <para>Task is critical</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.criticalpath</para>
+ </entry>
+ <entry>
+ <para>Critical Path</para>
+ </entry>
+ <entry>
+ <para>Task is in critical path</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.notscheduled</para>
+ </entry>
+ <entry>
+ <para>Not Scheduled</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.assignmentmissing</para>
+ </entry>
+ <entry>
+ <para>Assignment Missing</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.resourceoverbooked</para>
+ </entry>
+ <entry>
+ <para>Resource Overbooked</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.resourceunavailable</para>
+ </entry>
+ <entry>
+ <para>Resource Unavailable</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.constrainterror</para>
+ </entry>
+ <entry>
+ <para>Constraints Error</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.effortnotmet</para>
+ </entry>
+ <entry>
+ <para>Effort Not Met</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.schedulingerror</para>
+ </entry>
+ <entry>
+ <para>Scheduling Error</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.level</para>
+ </entry>
+ <entry>
+ <para>Node level, Level</para>
+ </entry>
+ <entry>
+ <para>Not interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.statusnote</para>
+ </entry>
+ <entry>
+ <para>Status Note</para>
+ </entry>
+ <entry>
+ <para>Note: Not implemented</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.owner</para>
+ </entry>
+ <entry>
+ <para>Owner</para>
+ </entry>
+ <entry>
+ <para>Must not be used, and are not very interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.status</para>
+ </entry>
+ <entry>
+ <para>Status</para>
+ </entry>
+ <entry>
+ <para>Must not be used, and are not very interesting</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><replaceable>table name</replaceable>.time</para>
+ </entry>
+ <entry>
+ <para>Time</para>
+ </entry>
+ <entry>
+ <para>Must not be used, and are not very interesting</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ </sect4>
+</sect3>
+<sect3 id="chart"><title>Chart</title>
+ <para>Use by placing a variable with name chartX (X=some text to make the variable name unique) with a value project before the chart that shall be used.
+ </para>
+ <para>The variable has this format:
+ </para>
+ <para>Variable: <varname>Name: chartX (X=some text) Value: project; values=<replaceable>data</replaceable>;</varname>
+ </para>
+ <para>where <replaceable>data</replaceable> is a comma separated list of values to be include in the chart.
+ </para>
+ <para>Possible <replaceable>data</replaceable> values are:
+ </para>
+ <itemizedlist>
+ <listitem><para><guilabel>bcws effort</guilabel> Budgeted cost of work scheduled, effort based.</para></listitem>
+ <listitem><para><guilabel>bcwp effort</guilabel> Budgeted cost of work performed, effort based.</para></listitem>
+ <listitem><para><guilabel>acwp effort</guilabel> Actual cost of work performed, effort based.</para></listitem>
+ <listitem><para><guilabel>spi effort</guilabel> Schedule performance index, effort based.</para></listitem>
+ <listitem><para><guilabel>cpi effort</guilabel> Cost performance index, effort based.</para></listitem>
+ <listitem><para><guilabel>bcws cost</guilabel> Budgeted cost of work scheduled, cost based.</para></listitem>
+ <listitem><para><guilabel>bcwp cost</guilabel> Budgeted cost of work performed, cost based.</para></listitem>
+ <listitem><para><guilabel>acwp cost</guilabel> Actual cost of work performed, cost based.</para></listitem>
+ <listitem><para><guilabel>spi cost</guilabel> Schedule performance index, cost based.</para></listitem>
+ <listitem><para><guilabel>cpi cost</guilabel> Cost performance index, cost based.</para></listitem>
+ </itemizedlist>
+ <para>The charts you create in your template must have the same (or more) number of columns as the number of values you specify in your variable.
+ </para>
+ <para>Example:
+ </para>
+ <para>Variable name: <varname>chart1</varname> Value: <varname>project; values=bcws cost,bcwp cost, acwp cost;</varname>
+ </para>
+ <para>Note that you cannot mix effort- and cost-based values. If you want to show both, create two charts.
+ </para>
+ <sect4 id="gantt"><title>Gantt</title>
+ <para>Not supported.
+ </para>
+ </sect4>
+</sect3>
+</sect2>
diff --git a/doc/creatingproject.docbook b/doc/creatingproject.docbook
new file mode 100644
index 00000000..5c608443
--- /dev/null
+++ b/doc/creatingproject.docbook
@@ -0,0 +1,28 @@
+<sect2><title/>
+<para>A new project can be created by pressing the <emphasis>New Project</emphasis> button or selecting a <emphasis>project template</emphasis> in the <link linkend="startup-view">Startup View</link>.
+</para>
+<para>This will create a new project with default values defined in <ulink url="http://userbase.kde.org/Special:myLanguage/Plan/Manual/Configure Plan Dialog">Settings</ulink> or from values defined in the template. The Project Settings Dialog will open to enable you to define project specific properties like <emphasis>project name</emphasis>, <emphasis>manager</emphasis> and <emphasis>target times</emphasis>.
+</para>
+<para>When you create your first project, consider creating resources in a separate file. When you refer to this file in your project(s), you do not need to define your resources again, and you can coordinate resource usage across projects.
+</para>
+<para>See <link linkend="managing-resources">Managing Resources</link>.
+</para>
+<para>If you want to coordinate resource usage across projects, your project files must be stored in the same directory.
+</para>
+<para>A useful structure could be something like this:
+</para>
+<para><screen>
+ Plan
+ !-- Resources
+ ! !-- SharedResources.plan
+ !-- Taskmodules
+ ! !-- Task modules (if any)
+ !-- Templates
+ ! !-- Project templates (if any)
+ !-- Projects
+ ! !-- <project 1>.plan
+ ! !-- <project 2>.plan
+ ! !-- etc
+ </screen>
+</para>
+</sect2>
diff --git a/doc/definitions.docbook b/doc/definitions.docbook
new file mode 100644
index 00000000..1f583adf
--- /dev/null
+++ b/doc/definitions.docbook
@@ -0,0 +1,153 @@
+<sect2><title/>
+<sect3 id="introduction0"><title>Introduction</title>
+ <para>In project management, terms may be used in different ways in different programs or different companies or project types. Looking at more exhaustive project management glossaries, one will find alternative definitions for most terms.
+ </para>
+ <para>This list defines how certain terms are used in <guilabel>Plan</guilabel>.
+ </para>
+</sect3>
+<sect3 id="terms"><title>Terms</title>
+ <variablelist>
+ <varlistentry><term id="account"><emphasis role="bold">Account</emphasis></term>
+ <listitem>
+ <para>An account is used in a <emphasis>Cost Breakdown Structure</emphasis> (<link linkend="cbs">CBS</link>) to represent a place where cost from <link linkend="task">tasks</link> or <link linkend="resource">resources</link> can be aggregated.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="acwp"><emphasis role="bold">ACWP</emphasis></term>
+ <listitem>
+ <para><link linkend="Actual-Cost-of-Work-Performed">Actual Cost of Work Performed</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Actual-Cost-of-Work-Performed"><emphasis role="bold">Actual Cost of Work Performed</emphasis></term>
+ <listitem>
+ <para>The actual cost (or effort) that has been performed.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="allocation"><emphasis role="bold">Allocation</emphasis></term>
+ <listitem>
+ <para>Tasks are allocated to <link linkend="resource">Resources</link> during the planning stage of the project. The actual assignment is done during scheduling. Note that assignment is not guaranteed as the resource may not be available.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="assignment"><emphasis role="bold">Assignment</emphasis></term>
+ <listitem>
+ <para>Tasks are assigned to <link linkend="resource">Resources</link> during scheduling.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="bcws"><emphasis role="bold">BCWS</emphasis></term>
+ <listitem>
+ <para><link linkend="Budgeted-Cost-of-Work-Scheduled">Budgeted Cost of Work Scheduled</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Budgeted-Cost-of-Work-Scheduled"><emphasis role="bold">Budgeted Cost of Work Scheduled</emphasis></term>
+ <listitem>
+ <para>The cost (or effort) that should have been used in order to reach the stated progress.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="bcwp"><emphasis role="bold">BCWP</emphasis></term>
+ <listitem>
+ <para><link linkend="Budgeted-Cost-of-Work-Performed">Budgeted Cost of Work Performed</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Budgeted-Cost-of-Work-Performed"><emphasis role="bold">Budgeted Cost of Work Performed</emphasis></term>
+ <listitem>
+ <para>The cost (or effort) that has been performed.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="cbs"><emphasis role="bold">CBS</emphasis></term>
+ <listitem>
+ <para><link linkend="Cost-Breakdown-Structure">Cost Breakdown Structure</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="cpi"><emphasis role="bold">CPI</emphasis></term>
+ <listitem>
+ <para>Is the <emphasis>Cost Performance Index</emphasis> and is equal to <link linkend="bcwp">BCWP</link>/<link linkend="acwp">ACWP</link>. When this index is below 1, means that you are over budget. If the index is greater than 1 means that the costs are under budget.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Cost-Breakdown-Structure"><emphasis role="bold">Cost Breakdown structure</emphasis></term>
+ <listitem>
+ <para>The CBS organizes <link linkend="account">accounts</link> into a structure to enable cost to be aggregated independent of the <link linkend="wbs">WBS</link> and <link linkend="rbs">RBS</link>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="estimate"><emphasis role="bold">Estimate</emphasis></term>
+ <listitem>
+ <para>The estimate is the expected amount of effort or time needed to complete a <link linkend="task">task</link>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="milestone"><emphasis role="bold">Milestone</emphasis></term>
+ <listitem>
+ <para>A milestone is a <link linkend="task">task</link> with an effort of 0.00h. It is typically used to mark a major outcome, for example the completion of a deliverable upon customer acceptance.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="pert"><emphasis role="bold">PERT</emphasis></term>
+ <listitem>
+ <para><link linkend="Program-Evaluation-and-Review-Technique">Program Evaluation and Review Technique</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Program-Evaluation-and-Review-Technique"><emphasis role="bold">Program Evaluation and Review Technique</emphasis></term>
+ <listitem>
+ <para>The Program Evaluation and Review Technique is an enhancement to the Critical Path Method. <link linkend="task">Task</link> effort estimates in CPM are point estimates, while <link linkend="task">task</link> effort estimates in PERT are computed by weighting the Optimistic, Most Likely, and Pessimistic estimates (O+(4*M)+P)/6.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="PERT-Distribution"><emphasis role="bold">PERT Distribution</emphasis></term>
+ <listitem>
+ <para>A simplified way to calculate Expected estimate from Optimistic-, Most Likely- and Pessimistic estimate.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="rbs"><emphasis role="bold">RBS</emphasis></term>
+ <listitem>
+ <para><link linkend="Resource-Breakdown-Structure">Resource Breakdown Structure</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Resource-Breakdown-Structure"><emphasis role="bold">Resource Breakdown Structure</emphasis></term>
+ <listitem>
+ <para>The RBS organizes resources into <link linkend="Resource-Group">resource groups</link>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="resource"><emphasis role="bold">Resource</emphasis></term>
+ <listitem>
+ <para>A resource can be of type <emphasis>Work</emphasis>, <emphasis>Material</emphasis> or <emphasis>Team</emphasis>. A resource must always belong to a <link linkend="Resource-Group">Resource Group</link>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Resource-Group"><emphasis role="bold">Resource Group</emphasis></term>
+ <listitem>
+ <para>A resource group is used to group similar <link linkend="resource">resources</link>.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Resource-Team"><emphasis role="bold">Resource Team</emphasis></term>
+ <listitem>
+ <para>A <link linkend="resource">resource</link> team is a resource that consists of a number of other resources.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="spi"><emphasis role="bold">SPI</emphasis></term>
+ <listitem>
+ <para>Is the Schedule Performance Index and is equal to BCWP/BCWS. When this index is below 1, means that you are behind schedule. If the index is greater than 1 means that you are ahead of the schedule.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="summary-task"><emphasis role="bold">Summary Task</emphasis></term>
+ <listitem>
+ <para>A Summary Task has subordinate Sub-Tasks, and rolls up information based on the Sub-Tasks.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="task"><emphasis role="bold">Task</emphasis></term>
+ <listitem>
+ <para>A Task is a unit of work. <link linkend="resource">Resources</link> are generally allocated at the Task level.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="vcard"><emphasis role="bold">vCard</emphasis></term>
+ <listitem>
+ <para>vCard is a file format standard for electronic business cards.</para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="wbs"><emphasis role="bold">WBS</emphasis></term>
+ <listitem>
+ <para><link linkend="Work-Breakdown-Structure">Work Breakdown Structure</link></para>
+ </listitem>
+ </varlistentry>
+ <varlistentry><term id="Work-Breakdown-Structure"><emphasis role="bold">Work Breakdown Structure</emphasis></term>
+ <listitem>
+ <para>The WBS is used to break down large projects into manageable chunks to ease planning and management.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+
+</sect3>
+</sect2>
diff --git a/doc/dependencyeditor1.png b/doc/dependencyeditor1.png
deleted file mode 100644
index 8c85f536..00000000
Binary files a/doc/dependencyeditor1.png and /dev/null differ
diff --git a/doc/gantt1.png b/doc/gantt1.png
deleted file mode 100644
index 21680915..00000000
Binary files a/doc/gantt1.png and /dev/null differ
diff --git a/doc/guidelines.docbook b/doc/guidelines.docbook
new file mode 100644
index 00000000..6ef1a84f
--- /dev/null
+++ b/doc/guidelines.docbook
@@ -0,0 +1,11 @@
+<chapter id="creating-a-project"><title>Guidelines</title>
+ <sect1 id="creating-a-project-section"><title>Creating a Project</title>
+ &creating-project-section;
+ </sect1>
+ <sect1 id="managing-resources"><title>Managing Resources</title>
+ &managing-resources-section;
+ </sect1>
+ <sect1 id="creating-odt-report-templates"><title>Creating ODT Report Templates</title>
+ &creating-odt-report-templates-section;
+ </sect1>
+</chapter>
diff --git a/doc/index.docbook b/doc/index.docbook
new file mode 100644
index 00000000..490501b2
--- /dev/null
+++ b/doc/index.docbook
@@ -0,0 +1,73 @@
+<?xml version="1.0" ?>
+<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.5-Based Variant V1.1//EN" "dtd/kdedbx45.dtd" [
+<!ENTITY plan-introduction-chapter SYSTEM "planintroduction.docbook">
+<!ENTITY guidelines-chapter SYSTEM "guidelines.docbook">
+<!ENTITY common-user-interface-chapter SYSTEM "commonuserinterface.docbook">
+<!ENTITY views-and-editors-chapter SYSTEM "viewsandeditors.docbook">
+<!ENTITY reports-chapter SYSTEM "reports.docbook">
+<!ENTITY introduction-section SYSTEM "introduction.docbook">
+<!ENTITY definitions-section SYSTEM "definitions.docbook">
+<!ENTITY context-help-section SYSTEM "contexthelp.docbook">
+<!ENTITY creating-project-section SYSTEM "creatingproject.docbook">
+<!ENTITY managing-resources-section SYSTEM "managingresources.docbook">
+<!ENTITY creating-odt-report-templates-section SYSTEM "creatingodtreporttemplates.docbook">
+<!ENTITY main-work-space-section SYSTEM "mainworkspace.docbook">
+<!ENTITY using-the-views-section SYSTEM "usingtheviews.docbook">
+<!ENTITY startup-view-section SYSTEM "startupview.docbook">
+<!ENTITY task-editor-section SYSTEM "taskeditor.docbook">
+<!ENTITY resource-editor-section SYSTEM "resourceeditor.docbook">
+<!ENTITY work-and-vacation-editor-section SYSTEM "workandvacationeditor.docbook">
+<!ENTITY cost-breakdown-structure-editor-section SYSTEM "costbreakdownstructureeditor.docbook">
+<!ENTITY task-dependency-editor-graphical-section SYSTEM "taskdependencyeditorgraphical.docbook">
+<!ENTITY task-dependency-editor-list-section SYSTEM "taskdependencyeditorlist.docbook">
+<!ENTITY schedules-editor-section SYSTEM "scheduleseditor.docbook">
+<!ENTITY project-performance-view-section SYSTEM "projectperformanceview.docbook">
+<!ENTITY task-performance-view-section SYSTEM "taskperformanceview.docbook">
+<!ENTITY task-status-view-section SYSTEM "taskstatusview.docbook">
+<!ENTITY task-execution-view-section SYSTEM "taskexecutionview.docbook">
+<!ENTITY task-gantt-view-section SYSTEM "taskganttview.docbook">
+<!ENTITY milestone-gantt-view-section SYSTEM "milestoneganttview.docbook">
+<!ENTITY resource-assignment-view-section SYSTEM "resourceassignmentview.docbook">
+<!ENTITY resource-assignment-gantt-view-section SYSTEM "resourceassignmentganttview.docbook">
+<!ENTITY reports-generator-view-section SYSTEM "reportsgeneratorview.docbook">
+<!ENTITY % addindex "IGNORE">
+<!ENTITY % English "INCLUDE"><!-- change language only here -->
+]>
+<book lang="&language;">
+ <bookinfo>
+ <title>The Plan Handbook</title>
+ <authorgroup>
+ <author>
+ <personname>
+ <firstname>Dag</firstname><surname>Andersen</surname>
+ </personname>
+ </author>
+ <!-- TRANS:ROLES_OF_TRANSLATORS -->
+ </authorgroup>
+ <legalnotice>&FDLNotice;</legalnotice>
+ <date>2019-11-01</date>
+ <releaseinfo>3.2</releaseinfo>
+ <abstract>
+ <para></para>
+ </abstract>
+ <keywordset>
+ <keyword>KDE</keyword>
+ </keywordset>
+ </bookinfo>
+
+ &plan-introduction-chapter;
+ &guidelines-chapter;
+ &views-and-editors-chapter;
+ &reports-chapter;
+
+ <!--userbase-content-->
+ <chapter id="credits">
+ <title>Credits and License</title>
+ <para>
+ Documentation Copyright see the UserBase
+ <ulink url="http://userbase.kde.org/index.php?title=Plan&action=history">Plan page history</ulink></para>
+ <!-- TRANS:CREDIT_FOR_TRANSLATORS -->
+ &underFDL;
+ </chapter>
+ &documentation.index;
+</book>
diff --git a/doc/intro1.png b/doc/intro1.png
deleted file mode 100644
index a36091c6..00000000
Binary files a/doc/intro1.png and /dev/null differ
diff --git a/doc/introduction.docbook b/doc/introduction.docbook
new file mode 100644
index 00000000..46dfefb8
--- /dev/null
+++ b/doc/introduction.docbook
@@ -0,0 +1,31 @@
+<sect2><title/>
+<para>Features include:
+</para>
+<itemizedlist>
+ <listitem><para>Task management using the <link linkend="task-editor">Task Editor</link> <itemizedlist>
+ <listitem><para>Work breakdown structure with configurable WBS codes</para></listitem>
+ <listitem><para>Tasks, summary tasks, and milestones</para></listitem>
+ <listitem><para>Different types of time constraints</para></listitem>
+ <listitem><para>Different types of dependencies.</para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>Resource management using the <link linkend="resource-editor">Resource Editor</link> <itemizedlist>
+ <listitem><para>Resource breakdown structure</para></listitem>
+ <listitem><para>Working- and material resource types</para></listitem>
+ <listitem><para>Resource allocation on group level</para></listitem>
+ <listitem><para>Resource teams</para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>Work time & vacation definition using the <link linkend="work-and-vacation-editor">Work and Vacation Editor</link> </para></listitem>
+ <listitem><para>Cost management using the <link linkend="cost-breakdown-structure-editor">Cost Breakdown Structure Editor</link> </para></listitem>
+ <listitem><para>Earned value management</para></listitem>
+ <listitem><para>Project scheduling using the <link linkend="schedules-editor">Schedules Editor</link> <itemizedlist>
+ <listitem><para>Schedule forward from start time or backward from finish time</para></listitem>
+ <listitem><para>Allow or avoid resource overbooking</para></listitem>
+ <listitem><para>PERT distribution with optimistic-, pessimistic-, and most likely estimates</para></listitem>
+ <listitem><para>Multiple schedules with a possibility to schedule from current progress information</para></listitem>
+ </itemizedlist>
+ </para></listitem>
+ <listitem><para>Task tracking using the <link linkend="task-execution-view">Task Execution View</link> or <link linkend="task-status-view">Task Status View</link> </para></listitem>
+</itemizedlist>
+</sect2>
diff --git a/doc/kplatowork1.png b/doc/kplatowork1.png
deleted file mode 100644
index db4c25ed..00000000
Binary files a/doc/kplatowork1.png and /dev/null differ
diff --git a/doc/mainworkspace.docbook b/doc/mainworkspace.docbook
new file mode 100644
index 00000000..4b853d27
--- /dev/null
+++ b/doc/mainworkspace.docbook
@@ -0,0 +1,44 @@
+<sect2><title/>
+<sect3 id="description2"><title>Description</title>
+ <para>
+ The Main Work Space is normally organized with the View Selector to the left and the data view to the right.</para><para>As usual, you will also find the Menu bar and Toolbar at the top, and the Status bar at the bottom.
+ </para>
+ <para>
+ Since both the View selector and the Scripts docker are dockers they can be moved to the different border, floated or hidden. To show a hidden docker, use the <menuchoice><guimenu>Settings</guimenu><guimenuitem>Dockers</guimenuitem></menuchoice> menu entry.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_work_space.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para>
+</sect3>
+<sect3 id="the-view-selector"><title>The View Selector</title>
+ <para>The <link linkend="the-view-selector">View Selector</link> enables you to select the data view you want to display from the currently listed views.
+ </para>
+ <para>Views are grouped into categories for easier retrieval: Editors, Views, Execution and Reports by default:
+ </para>
+ <itemizedlist>
+ <listitem><para>Editors holds the editors that you need to define and schedule your project.</para></listitem>
+ <listitem><para>Views holds views that are used for inspecting your project.</para></listitem>
+ <listitem><para>Execution holds views that are especially useful during the execution of your project.</para></listitem>
+ <listitem><para>Reports holds views for report generation.</para></listitem>
+ </itemizedlist>
+ <para>Views can also be moved within or across categories, or added to or removed from the <link linkend="the-view-selector">View Selector</link>.
+ </para>
+</sect3>
+<sect3 id="schedule-selector"><title>Schedule Selector</title>
+ <para>The Schedule Selector enables you to select the schedule all the views (⪚ <link linkend="task-gantt-view">Gantt View</link>) shall display values from. Tasks which has not been scheduled in the selected schedule are not normally shown in any of the views. (They are shown in editors, of course.)
+ </para>
+</sect3>
+<sect3 id="status-bar"><title>Status Bar</title>
+ <para>The status bar shows messages and progress information. Most notably is the currently selected schedule shown at the right of the status bar. Note that most of the views in the <emphasis>Views</emphasis> category display information depending on the selected schedule, so if the project is not scheduled (<emphasis>Not Scheduled</emphasis>), most views will be empty.
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/managingresources.docbook b/doc/managingresources.docbook
new file mode 100644
index 00000000..c594b017
--- /dev/null
+++ b/doc/managingresources.docbook
@@ -0,0 +1,10 @@
+<sect2 id="description"><title>Description</title>
+ <para>You can create resources for a project using the <link linkend="resource-editor">Resource Editor</link> and <link linkend="work-and-vacation-editor">Work and Vacation Editor</link>.
+ </para>
+ <para>However, if you are going to use the same resources in many projects (which is often the case) it is more convenient to maintain resources in a separate file. The best way to do this is to create your resources file first and then set up Plan to always load this file when creating a new project.
+ </para>
+ <para>If you are managing projects that use totally different resource pools you can create multiple resource files, but one project can only refer to one resource file.
+ </para>
+ <para>You can select the resource file to use when creating a new project.
+ </para>
+</sect2>
diff --git a/doc/milestoneganttview.docbook b/doc/milestoneganttview.docbook
new file mode 100644
index 00000000..d4942246
--- /dev/null
+++ b/doc/milestoneganttview.docbook
@@ -0,0 +1,98 @@
+<sect2><title/>
+<sect3 id="description30"><title>Description</title>
+ <para>
+ The Milestone Gantt view is used to show milestones in a time line.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_milestoneganttview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Gantt View</phrase>
+ </textobject>
+ <caption>
+ <para>Gantt View</para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="editing-data31"><title>Editing data</title>
+ <para>Milestone description and progress can be edited using the context menu.
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>WBS Code</para>
+ </entry>
+ <entry>
+ <para>The Work Breakdown Structure code</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the milestone.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Start Time</para>
+ </entry>
+ <entry>
+ <para>The scheduled start time.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration32"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured using the configure dialog.</para>
+ <para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_milestoneganttview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Configuration Dialog</phrase>
+ </textobject>
+ <caption>
+ <para>Configuration Dialog</para>
+ </caption>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/plan_accounteditor.png b/doc/plan_accounteditor.png
new file mode 100644
index 00000000..6d8cd06d
Binary files /dev/null and b/doc/plan_accounteditor.png differ
diff --git a/doc/plan_criticalpath.png b/doc/plan_criticalpath.png
new file mode 100644
index 00000000..d193a0d8
Binary files /dev/null and b/doc/plan_criticalpath.png differ
diff --git a/doc/plan_dependencyeditor.png b/doc/plan_dependencyeditor.png
new file mode 100644
index 00000000..115e1d29
Binary files /dev/null and b/doc/plan_dependencyeditor.png differ
diff --git a/doc/plan_pertresult.png b/doc/plan_pertresult.png
new file mode 100644
index 00000000..a728f88c
Binary files /dev/null and b/doc/plan_pertresult.png differ
diff --git a/doc/plan_project_perf_chart.png b/doc/plan_project_perf_chart.png
new file mode 100644
index 00000000..d09460e3
Binary files /dev/null and b/doc/plan_project_perf_chart.png differ
diff --git a/doc/plan_resourceeditor.png b/doc/plan_resourceeditor.png
new file mode 100644
index 00000000..846a9505
Binary files /dev/null and b/doc/plan_resourceeditor.png differ
diff --git a/doc/plan_resourceeditor_config.png b/doc/plan_resourceeditor_config.png
new file mode 100644
index 00000000..46143e83
Binary files /dev/null and b/doc/plan_resourceeditor_config.png differ
diff --git a/doc/plan_scheduleeditor.png b/doc/plan_scheduleeditor.png
new file mode 100644
index 00000000..8b650a43
Binary files /dev/null and b/doc/plan_scheduleeditor.png differ
diff --git a/doc/plan_scheduleeditor_config.png b/doc/plan_scheduleeditor_config.png
new file mode 100644
index 00000000..72662a1b
Binary files /dev/null and b/doc/plan_scheduleeditor_config.png differ
diff --git a/doc/plan_schedulinglog.png b/doc/plan_schedulinglog.png
new file mode 100644
index 00000000..5b4bb8b5
Binary files /dev/null and b/doc/plan_schedulinglog.png differ
diff --git a/doc/plan_taskeditor.png b/doc/plan_taskeditor.png
new file mode 100644
index 00000000..c8983aef
Binary files /dev/null and b/doc/plan_taskeditor.png differ
diff --git a/doc/plan_taskeditor_config.png b/doc/plan_taskeditor_config.png
new file mode 100644
index 00000000..2a2fb731
Binary files /dev/null and b/doc/plan_taskeditor_config.png differ
diff --git a/doc/plan_taskexecutionview.png b/doc/plan_taskexecutionview.png
new file mode 100644
index 00000000..7550b705
Binary files /dev/null and b/doc/plan_taskexecutionview.png differ
diff --git a/doc/plan_taskexecutionview_config.png b/doc/plan_taskexecutionview_config.png
new file mode 100644
index 00000000..b54dda76
Binary files /dev/null and b/doc/plan_taskexecutionview_config.png differ
diff --git a/doc/plan_taskprogressdialog.png b/doc/plan_taskprogressdialog.png
new file mode 100644
index 00000000..c3de5be1
Binary files /dev/null and b/doc/plan_taskprogressdialog.png differ
diff --git a/doc/plan_tasks_perf_chart.png b/doc/plan_tasks_perf_chart.png
new file mode 100644
index 00000000..d1c06245
Binary files /dev/null and b/doc/plan_tasks_perf_chart.png differ
diff --git a/doc/plan_taskstatusview.png b/doc/plan_taskstatusview.png
new file mode 100644
index 00000000..025011e5
Binary files /dev/null and b/doc/plan_taskstatusview.png differ
diff --git a/doc/plan_taskstatusview_config.png b/doc/plan_taskstatusview_config.png
new file mode 100644
index 00000000..16c56726
Binary files /dev/null and b/doc/plan_taskstatusview_config.png differ
diff --git a/doc/plan_work_space.png b/doc/plan_work_space.png
new file mode 100644
index 00000000..a93b9c19
Binary files /dev/null and b/doc/plan_work_space.png differ
diff --git a/doc/plan_workandvacation.png b/doc/plan_workandvacation.png
new file mode 100644
index 00000000..6eb5d86c
Binary files /dev/null and b/doc/plan_workandvacation.png differ
diff --git a/doc/planintroduction.docbook b/doc/planintroduction.docbook
new file mode 100644
index 00000000..8fb5d5c7
--- /dev/null
+++ b/doc/planintroduction.docbook
@@ -0,0 +1,18 @@
+<!-- Note: Set id of chapter to the id the first section should have had -->
+<chapter id="introduction"><title>Introduction to Plan</title>
+ <sect1 id="introduction-section"><title>Introduction</title>
+ &introduction-section;
+ </sect1>
+ <sect1 id="definitions"><title>Definitions</title>
+ &definitions-section;
+ </sect1>
+ <sect1 id="context-help"><title>Context Help</title>
+ &context-help-section;
+ </sect1>
+ <sect1 id="main-work-space"><title>Main Work Space</title>
+ &main-work-space-section;
+ </sect1>
+ <sect1 id="using-the-views"><title>Using the Views</title>
+ &using-the-views-section;
+ </sect1>
+</chapter>
diff --git a/doc/projectperformanceview.docbook b/doc/projectperformanceview.docbook
new file mode 100644
index 00000000..5e8117d1
--- /dev/null
+++ b/doc/projectperformanceview.docbook
@@ -0,0 +1,33 @@
+<sect2 id="description21"><title>Description</title>
+ <para>
+ The Project performance view is a project management chart where can be understood the actual situation of the project according to the Earned Value Method.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_project_perf_chart.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>where:
+ </para>
+ <itemizedlist>
+ <listitem><para>BCWS means Budgeted Cost Work Scheduled,</para></listitem>
+ <listitem><para>BCWP means Budgeted Cost Work Performed,</para></listitem>
+ <listitem><para>ACWP means Actual Cost Work Performed.</para></listitem>
+ </itemizedlist>
+ <para>All these are considered as effort in hours and costs.
+ </para>
+ <para>PI are the Performance Indexes, where:
+ </para>
+ <itemizedlist>
+ <listitem><para>CPI is the Cost Performance Index,</para></listitem>
+ <listitem><para>SPI is the Schedule Performance Index.</para></listitem>
+ </itemizedlist>
+</sect2>
diff --git a/doc/reports.docbook b/doc/reports.docbook
new file mode 100644
index 00000000..0c4fe750
--- /dev/null
+++ b/doc/reports.docbook
@@ -0,0 +1,5 @@
+<chapter id="reports-generator-view"><title>Reports</title>
+ <sect1 id="reports-generator-view-section"><title>Reports Generator View</title>
+ &reports-generator-view-section;
+ </sect1>
+</chapter>
diff --git a/doc/reportsgeneratorview.docbook b/doc/reportsgeneratorview.docbook
new file mode 100644
index 00000000..21ea2e85
--- /dev/null
+++ b/doc/reportsgeneratorview.docbook
@@ -0,0 +1,122 @@
+<sect2><title/>
+<sect3 id="description41"><title>Description</title>
+ <para>
+ The Reports Generator View is used to add and generate reports in Open Document Text (odt) format.</para><para>The reports can be based on the supplied report templates, or you can <link linkend="creating-odt-report-templates">write your own templates</link>.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_reportsgeneratorview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>A name of your choice</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Report Template</para>
+ </entry>
+ <entry>
+ <para>Path to the report template file. You can select one of the supplied standard templates or you can enter the filename of a template you provide yourself.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Report File</para>
+ </entry>
+ <entry>
+ <para>The name of the file that will be generated.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add</para>
+ </entry>
+ <entry>
+ <para>Information that can be added to the report file name to distinguish it from previously generated versions. This can be:</para>
+ <itemizedlist>
+ <listitem><para><emphasis>Nothing</emphasis>; use the filename as is</para></listitem>
+ <listitem><para><emphasis>Number</emphasis>; add a sequence number to the file name</para></listitem>
+ <listitem><para><emphasis>Date</emphasis>; add the current date to the file name</para></listitem>
+ </itemizedlist>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="toolbar42"><title>Toolbar</title>
+ <para>The toolbar provides the means to add, remove and generate reports.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Report</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Add a new report</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Remove Report</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>D</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Remove the selected report</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Generate Report</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>G</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Generate the selected report</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/resourceassignmentganttview.docbook b/doc/resourceassignmentganttview.docbook
new file mode 100644
index 00000000..09c19d25
--- /dev/null
+++ b/doc/resourceassignmentganttview.docbook
@@ -0,0 +1,110 @@
+<sect2><title/>
+<sect3 id="description37"><title>Description</title>
+ <para>The Resource Assignment Gantt View displays the scheduled task-resource assignments in a Gantt chart.
+ </para>
+ <!--
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceassignmentganttview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Gantt View</phrase>
+ </textobject>
+ <caption>
+ <para>Gantt View</para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+ </para>
+ -->
+</sect3>
+<sect3 id="data38"><title>Data</title>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the object (Resource group, resource, task)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Type</para>
+ </entry>
+ <entry>
+ <para>Object type</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Start Time</para>
+ </entry>
+ <entry>
+ <para>The start of the assignment</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>End Time</para>
+ </entry>
+ <entry>
+ <para>The end of the assignment</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data39"><title>Editing data</title>
+ <para>The task description and progress can be edited using the context menu.
+ </para>
+</sect3>
+<sect3 id="configuration40"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured using the configure dialog.</para><para>The configure dialog enables you to select which columns to display.
+ </para>
+
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceassignmentganttview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Configuration Dialog</phrase>
+ </textobject>
+ <caption>
+ <para>Configuration Dialog</para>
+ </caption>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/resourceassignmentview.docbook b/doc/resourceassignmentview.docbook
new file mode 100644
index 00000000..3e92a988
--- /dev/null
+++ b/doc/resourceassignmentview.docbook
@@ -0,0 +1,104 @@
+<sect2><title/>
+<sect3 id="description33"><title>Description</title>
+ <para>
+ The Resource Assignment View displays the scheduled task-resource assignments in a table.
+ <note><para>This view can severely impact performance in large projects.</para></note>
+ </para>
+ <para>
+ <!--
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceassignmentview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Resource assignment table</phrase>
+ </textobject>
+ <caption>
+ <para>Resource Assignment Table</para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+ -->
+ </para>
+</sect3>
+<sect3 id="data34"><title>Data</title>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the object (Resource group, resource, task)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Total</para>
+ </entry>
+ <entry>
+ <para>The total assignment for a resource</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Dates</para>
+ </entry>
+ <entry>
+ <para>The total assignments for a resource per day and the assignments for the resource per task.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data35"><title>Editing data</title>
+ <para>The task description and progress can be edited using the context menu.
+ </para>
+</sect3>
+<sect3 id="configuration36"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured using the configure dialog.</para><para>The configure dialog enables you to include or exclude assignments.
+ </para>
+
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceassignmentview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Configuration Dialog</phrase>
+ </textobject>
+ <caption>
+ <para>Configuration Dialog</para>
+ </caption>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/resourceeditor.docbook b/doc/resourceeditor.docbook
new file mode 100644
index 00000000..1cc47023
--- /dev/null
+++ b/doc/resourceeditor.docbook
@@ -0,0 +1,222 @@
+<sect2><title/>
+<sect3 id="description6"><title>Description</title>
+ <para>
+ The Resource Editor is used to create, edit, and delete resources and resource groups. Resources must belong to a resource group. At the moment sub-groups are not allowed.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceeditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>Working resources must refer to a <emphasis>calendar</emphasis> that defines the working hours for the resource. Calendars are created using the <link linkend="work-and-vacation-editor">Work and Vacation Editor</link>.
+ </para>
+ <para>Material resources are by default always available. You can use a calendar to limit its availability.
+ </para>
+ <para>Resources can be <emphasis>Shared</emphasis> or <emphasis>Local</emphasis>. A local resource is only used in the current project. A shared resource can be shared between multiple projects and is stored in a separate file, see <link linkend="managing-resources">Managing Resources</link>.
+ </para>
+</sect3>
+<sect3 id="toolbar7"><title>Toolbar</title>
+ <para>The toolbar provides the means to create and delete resources and resource groups:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Resource Group</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a resource group. The new group is appended at the end of the groups.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add Resource</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a resource. The new resource is appended as a child to the currently selected group. If a resource is selected, the new resource is appended to its parent group.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Delete</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected resources and/or resource groups.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ <para>Resources can be created by dropping data from any application that supports dragging vCard information, like <emphasis>KAddressBook</emphasis> or <emphasis>Evolution</emphasis>.
+ </para>
+ <para>Resources can be copied or moved to a different resource group using drag-and-drop.
+ </para>
+ <para><note><para>When moving a resource, the resource will lose any allocations.</para></note>
+ </para>
+</sect3>
+<sect3 id="editing-data8"><title>Editing data</title>
+ <para>Data can be edited inline as described <link linkend="using-the-views">here</link>.
+ </para>
+ <para>Resources can also be edited using the Resource Settings Dialog.
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the resource or resource group.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Scope</para>
+ </entry>
+ <entry>
+ <para>A resource can be <emphasis>Shared</emphasis> or <emphasis>Local</emphasis>. A shared resource cannot be edited.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Type</para>
+ </entry>
+ <entry>
+ <para>The type of resource or resource group.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Initials</para>
+ </entry>
+ <entry>
+ <para>The initials of the resource.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Email</para>
+ </entry>
+ <entry>
+ <para>The e-mail address of the resource.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Calendar</para>
+ </entry>
+ <entry>
+ <para>The calendar defines when the resource is working.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Limit (%)</para>
+ </entry>
+ <entry>
+ <para>The maximum load that can be assigned.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Available From</para>
+ </entry>
+ <entry>
+ <para>Defines when the resource is available to the project.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Available Until</para>
+ </entry>
+ <entry>
+ <para>Defines when the resource is available to the project.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Normal Rate</para>
+ </entry>
+ <entry>
+ <para>The cost per hour, normal hours.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Account</para>
+ </entry>
+ <entry>
+ <para>The account where the resource cost is accumulated.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration9"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured to split/unsplit the tree view or it can be configured using the configure dialog.</para><para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.
+ </para>
+
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_resourceeditor_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/resourceeditor1.png b/doc/resourceeditor1.png
deleted file mode 100644
index 002a7b9d..00000000
Binary files a/doc/resourceeditor1.png and /dev/null differ
diff --git a/doc/scheduleeditor1.png b/doc/scheduleeditor1.png
deleted file mode 100644
index a83467b3..00000000
Binary files a/doc/scheduleeditor1.png and /dev/null differ
diff --git a/doc/scheduleseditor.docbook b/doc/scheduleseditor.docbook
new file mode 100644
index 00000000..c731a383
--- /dev/null
+++ b/doc/scheduleseditor.docbook
@@ -0,0 +1,278 @@
+<sect2><title/>
+<sect3 id="description17"><title>Description</title>
+ <para>
+ The Schedule Editor is used to create, edit, calculate and delete schedules.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_scheduleeditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The Schedule Editor has three sub-views that show the results of the scheduling.
+ </para>
+ <para>The Result sub-view shows the values needed for PERT analysis including early start and -finish, late start and -finish along with different types of float.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_pertresult.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The Critical Path sub-view shows the tasks that belong to the critical path.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_criticalpath.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The Scheduling Log sub-view shows a list of messages produced during scheduling.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_schedulinglog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="toolbar18"><title>Toolbar</title>
+ <para>The toolbar provides the means to create, delete and calculate schedules:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-view-time-schedule-insert.png" format="PNG"/> </imageobject> </inlinemediaobject> Add Schedule</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a resource group. The new group is appended at the end of the groups.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-view-time-schedule-child-insert.png" format="PNG"/> </imageobject> </inlinemediaobject> Add Subschedule</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a sub-schedule. The new schedule is appended as a child to the currently selected schedule.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-edit-delete.png" format="PNG"/> </imageobject> </inlinemediaobject> Delete</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected schedule.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-view-time-schedule-calculus.png" format="PNG"/> </imageobject> </inlinemediaobject> Calculate</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Calculates the selected schedule.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-view-time-schedule-baselined-add.png" format="PNG"/> </imageobject> </inlinemediaobject> Baseline</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Baselines the selected schedule. Prevents the schedule from being re-calculated or deleted.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><inlinemediaobject> <imageobject> <imagedata fileref="Icon-go-first.png" format="PNG"/> </imageobject> </inlinemediaobject> Detach</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Make the selected sub-schedule a top schedule</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data19"><title>Editing data</title>
+ <para>Data can be edited in-line as described <link linkend="using-the-views">here</link>.
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the schedule.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>State</para>
+ </entry>
+ <entry>
+ <para>The schedules state. Shows a progress bar during scheduling.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Direction</para>
+ </entry>
+ <entry>
+ <para>The scheduling direction.</para><para>If the direction is Forward, the project is scheduled starting at the project's earliest start time specified in the main project dialog. If the direction is Backward, the project is scheduled starting at the project's latest finish time specified in the main project dialog.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Overbooking</para>
+ </entry>
+ <entry>
+ <para>Controls resource overbooking when scheduling.</para><para>If overbooking is allowed, a resource may be booked (on working days) to work more than it is available. This can happen if the resource is allocated to multiple tasks or are booked on other projects.
+ </para>
+ <para>If overbooking is to be avoided, resources will not be booked more than they are available. On resource conflict, tasks will be delayed until the resource is available.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Distribution</para>
+ </entry>
+ <entry>
+ <para>The distribution to be used during scheduling.</para><para>If the distribution is 'None', the estimate of the task is used as-is during scheduling.
+ </para>
+ <para>If the distribution is 'PERT', the estimate (E) used is calculated based on the entered optimistic- (O), pessimistic-(P) and most likely (M) estimate. The formula used for this is:
+ </para>
+ <para>E = (O + 4 * M + P) / 6.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Planned Start</para>
+ </entry>
+ <entry>
+ <para>The scheduled start time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Planned Finish</para>
+ </entry>
+ <entry>
+ <para>The scheduled finish time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Scheduler</para>
+ </entry>
+ <entry>
+ <para>The scheduler used for calculating the project schedule.</para><para>The default built-in scheduler is the Network Scheduler.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration20"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured to split/unsplit the tree view or it can be configured using the configure dialog.</para><para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.
+ </para>
+
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_scheduleeditor_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/scripting1.png b/doc/scripting1.png
deleted file mode 100644
index 24acffcb..00000000
Binary files a/doc/scripting1.png and /dev/null differ
diff --git a/doc/startupview.docbook b/doc/startupview.docbook
new file mode 100644
index 00000000..fbc2f7a2
--- /dev/null
+++ b/doc/startupview.docbook
@@ -0,0 +1,11 @@
+<sect2><title/>
+<para>The Startup View is shown at startup and when <menuchoice><guimenu>File</guimenu><guimenuitem>New</guimenuitem></menuchoice> is selected.
+</para>
+<para>It has 3 sections for:
+</para>
+<itemizedlist>
+ <listitem><para>Creation of new projects. See also <link linkend="creating-a-project">Creating a Project</link> and <link linkend="managing-resources">Managing Resources</link> </para></listitem>
+ <listitem><para>Opening existing projects. This section gives you the possibility to open an existing project file or one of the 10 most recent projects you have opened.</para></listitem>
+ <listitem><para>The Help section gives you links to introductory pages, documentation and community forum.</para></listitem>
+</itemizedlist>
+</sect2>
diff --git a/doc/taskdependencyeditorgraphical.docbook b/doc/taskdependencyeditorgraphical.docbook
new file mode 100644
index 00000000..7fa9cb2f
--- /dev/null
+++ b/doc/taskdependencyeditorgraphical.docbook
@@ -0,0 +1,132 @@
+<sect2><title/>
+<sect3 id="description15"><title>Description</title>
+ <para>
+ The Task Dependency Editor is used to create, edit, and delete task dependencies. For convenience, tasks can also be inserted, deleted or edited.</para><para>The tasks are ordered in accordance with the Work Breakdown Structure (WBS).
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_dependencyeditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The symbols for summary tasks, tasks and milestones are shown below:
+ </para>
+ <para>As the <emphasis>Task</emphasis> and <emphasis>Milestone</emphasis> are sub-items to the <emphasis>Summary task</emphasis>, they are indented. Also, note that the WBS code is displayed along with the name.
+ </para>
+ <para>In the following figure, a <emphasis>Finish-Start</emphasis> dependency has been inserted to make <emphasis>Milestone</emphasis> depend on <emphasis>Task</emphasis>.
+ </para>
+ <para>As shown below, an item consists of three different selection areas:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Item area</para>
+ </entry>
+ <entry>
+ <para>Select the item for editing</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Start area</para>
+ </entry>
+ <entry>
+ <para>Used for creating <emphasis>Finish-Start</emphasis> and <emphasis>Start-Start</emphasis> dependencies</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Finish area</para>
+ </entry>
+ <entry>
+ <para>Used for creating <emphasis>Finish-Start</emphasis> and <emphasis>Finish-Finish</emphasis> dependencies</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-dependencies"><title>Editing dependencies</title>
+ <para>Dependencies are created by first selecting a start- or finish area of the predecessor task, then selecting the start- or finish area of the successor task.
+ </para>
+ <para>This can be done using the mouse or the keyboard.
+ </para>
+ <para>Alternatively, you can drop the predecessor's connection area on the successor's connection area.
+ </para>
+ <para>To edit or delete an existing dependency, you can open a dependency by selecting it, or open its context menu.
+ </para>
+ <para>You can also open the context menu on a connection area which will enable you to edit all dependencies connected to that area.
+ </para>
+</sect3>
+<sect3 id="toolbar16"><title>Toolbar</title>
+ <para>The toolbar provides the means to create and delete tasks:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Task</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Dropdown box to create a task or milestone. The new item is positioned after the currently selected item on the same level as the selected item. If no item is selected, the new item is appended at the top level.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>I</keycap></keycombo></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add Sub-task</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Dropdown box to create a sub-task or -milestone. The new item is appended as a child to the currently selected item.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;&Alt;<keycap>I</keycap></keycombo></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Delete Task</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected tasks.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/taskdependencyeditorlist.docbook b/doc/taskdependencyeditorlist.docbook
new file mode 100644
index 00000000..01b96603
--- /dev/null
+++ b/doc/taskdependencyeditorlist.docbook
@@ -0,0 +1,6 @@
+<sect2><title/>
+<para><note><para>This view is not shown by default. For large projects, it can impact performance severely</para></note>
+</para>
+<para>It can be activated using the <link linkend="the-view-selector">View Selector</link> context menu.
+</para>
+</sect2>
diff --git a/doc/taskeditor.docbook b/doc/taskeditor.docbook
new file mode 100644
index 00000000..7b1dc27a
--- /dev/null
+++ b/doc/taskeditor.docbook
@@ -0,0 +1,369 @@
+<sect2><title/>
+<sect3 id="description4"><title>Description</title>
+ <para>
+ The Task Editor is used to create, edit, and delete tasks.</para><para>Tasks can be organized into a hierarchical tree structure to any depth.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskeditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="toolbar"><title>Toolbar</title>
+ <para>The toolbar provides the means to create, delete and move tasks and milestones:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Task</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Dropdown box to create a task or milestone. The new item is positioned after the currently selected item on the same level as the selected item. If no item is selected, the new item is appended at the top level.</para>
+ </entry>
+ </row>
+ <row>
+ <entry><para> </para></entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>I</keycap></keycombo></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add Sub-task</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Dropdown box to create a sub-task or -milestone. The new item is appended as a child to the currently selected item.</para>
+ </entry>
+ </row>
+ <row>
+ <entry><para> </para></entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;&Alt;<keycap>I</keycap></keycombo></para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Delete Task</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected tasks.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Indent Task</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Appends the selected task as a child to the task above.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Unindent Task</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Moves the selected task one level up, inserting it after its current parent task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Move Up</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Moves the selected task up one place.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Move Down</para>
+ </entry>
+ <entry>
+ <para></para>
+ </entry>
+ <entry>
+ <para>Moves the selected task down one place.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ <para>
+ Note that you can also move or copy tasks using drag and drop or copy/paste.
+ </para>
+</sect3>
+<sect3 id="editing-data5"><title>Editing data</title>
+ <para>Data can be edited inline as described <link linkend="using-the-views">here</link> or by using the Task Settings Dialog.
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Status</para>
+ </entry>
+ <entry>
+ <para>Task status</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Responsible</para>
+ </entry>
+ <entry>
+ <para>The person responsible for this task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Allocation</para>
+ </entry>
+ <entry>
+ <para>List of resource allocations.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Type</para>
+ </entry>
+ <entry>
+ <para>The type of task or the estimate type of the task.</para><para>The type can be set to <emphasis>Milestone</emphasis>, <emphasis>Effort</emphasis> or <emphasis>Duration</emphasis>.
+ </para>
+ <para><guilabel>Note:</guilabel> If the type is <emphasis>Summary</emphasis> or <emphasis>Project</emphasis> the type is not editable.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Calendar</para>
+ </entry>
+ <entry>
+ <para>The calendar used when estimate type is <emphasis>Duration</emphasis>.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Estimate</para>
+ </entry>
+ <entry>
+ <para>The most likely estimate. The estimate is the expected amount of effort or time needed to complete a task. It can be expressed in different units: h (hours), d (days), w (weeks) and M (months).</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Optimistic Ratio</para>
+ </entry>
+ <entry>
+ <para>Optimistic estimate expressed as a negative percentage of the most likely estimate. (E.g. -20%).</para><para>This is only used if a PERT distribution is used.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Pessimistic Ratio</para>
+ </entry>
+ <entry>
+ <para>Pessimistic estimate expressed as a positive percentage of the most likely estimate. (E.g. 50%).</para><para>This is only used if a PERT distribution is used.
+ </para>
+
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Risk</para>
+ </entry>
+ <entry>
+ <para>Risk controls the PERT distribution used when calculating the actual estimate for this task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Constraint</para>
+ </entry>
+ <entry>
+ <para>The timing constraint type.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Constraint Start</para>
+ </entry>
+ <entry>
+ <para>Constraint start time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Constraint End</para>
+ </entry>
+ <entry>
+ <para>Constraint end time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Running Account</para>
+ </entry>
+ <entry>
+ <para>Account for running costs.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Startup Account</para>
+ </entry>
+ <entry>
+ <para>Account for cost incurred at startup of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Startup Cost</para>
+ </entry>
+ <entry>
+ <para>The cost incurred at startup of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Shutdown Account</para>
+ </entry>
+ <entry>
+ <para>Account for cost incurred at shutdown of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Shutdown Cost</para>
+ </entry>
+ <entry>
+ <para>The cost incurred at shutdown of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Description</para>
+ </entry>
+ <entry>
+ <para>Task notes.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="task-modules-docker"><title>Task Modules Docker</title>
+ <para>Task Modules are groups of tasks that can be reused across projects.
+ </para>
+ <para>This makes it possible to draw on past experience and to standardize similar operations.
+ </para>
+ <para>A task module is inserted into your project by dragging it from the docker and dropping it into your project.
+ </para>
+ <para>A task module is a regular plan file, and is designed using <guilabel>Plan</guilabel> in the same way as designing a regular project.
+ </para>
+ <para>A task module, however, typically includes only tasks, estimates, and dependencies.
+ </para>
+ <para>The project name is displayed in the docker, and the description is used as the tooltip.
+ </para>
+ <para>A module can be opened for inspection or editing by double-clicking on the module.
+ </para>
+ <para>The modules can be grouped by storing them in different directories. Where to search for them is configured using the Project Settings Dialog.
+ </para>
+ <para>Default values for new projects can be defined using the Plan Configuration Dialog.
+ </para>
+</sect3>
+<sect3 id="resources-docker"><title>Resources Docker</title>
+ <para>The Resources Docker offers a simple way to allocate resources to tasks by selecting the resources you need and dragging them onto the <emphasis>Allocation</emphasis> column.
+ </para>
+ <para>A resource can also be dropped on the <emphasis>Responsible</emphasis> column.
+ </para>
+</sect3>
+<sect3 id="allocations-docker"><title>Allocations Docker</title>
+ <para>The Allocations Docker displays the current resource allocation for the selected task.
+ </para>
+</sect3>
+<sect3 id="configuration"><title>Configuration</title>
+ <para>Using the context menu, the view can be configured to show / hide the Project, split / unsplit the tree view or it can be configured using the configure dialog.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskeditor_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/taskeditor1.png b/doc/taskeditor1.png
deleted file mode 100644
index 33a4082d..00000000
Binary files a/doc/taskeditor1.png and /dev/null differ
diff --git a/doc/taskexecution1.png b/doc/taskexecution1.png
deleted file mode 100644
index 2c462d07..00000000
Binary files a/doc/taskexecution1.png and /dev/null differ
diff --git a/doc/taskexecutionview.docbook b/doc/taskexecutionview.docbook
new file mode 100644
index 00000000..09969dc1
--- /dev/null
+++ b/doc/taskexecutionview.docbook
@@ -0,0 +1,173 @@
+<sect2><title/>
+<sect3 id="description25"><title>Description</title>
+ <para>
+ The Task Execution View is used to inspect task performance information.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskexecutionview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="data"><title>Data</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Progress information can be edited in-line as described <link linkend="using-the-views">here</link> or by using the task progress dialog.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskprogressdialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Status</para>
+ </entry>
+ <entry>
+ <para>Task status</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>% Completed</para>
+ </entry>
+ <entry>
+ <para>Task completion</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Responsible</para>
+ </entry>
+ <entry>
+ <para>The person responsible for this task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Assignment</para>
+ </entry>
+ <entry>
+ <para>The resources assigned to this task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>SPI</para>
+ </entry>
+ <entry>
+ <para>Schedule Performance Index. (BCWP / BCWS)</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>BCWS</para>
+ </entry>
+ <entry>
+ <para>Budgeted Cost of Work Scheduled.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>BCWP</para>
+ </entry>
+ <entry>
+ <para>Budgeted Cost of Work Performed.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>ACWP</para>
+ </entry>
+ <entry>
+ <para>Actual Cost of Work Performed.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Description</para>
+ </entry>
+ <entry>
+ <para>Task description</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration26"><title>Configuration</title>
+ <para>Using the context menu, the view can be configured to show / hide the Project, split / unsplit the tree view or it can be configured using the configure dialog.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskexecutionview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/taskganttview.docbook b/doc/taskganttview.docbook
new file mode 100644
index 00000000..e036982a
--- /dev/null
+++ b/doc/taskganttview.docbook
@@ -0,0 +1,106 @@
+<sect2><title/>
+<sect3 id="description27"><title>Description</title>
+ <para>
+ The Gantt view is used to show tasks in a timeline.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_ganttview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Gantt View</phrase>
+ </textobject>
+ <caption>
+ <para>Gantt View</para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="editing-data28"><title>Editing data</title>
+ <para>Task description and progress can be edited using the context menu.
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Start Time</para>
+ </entry>
+ <entry>
+ <para>The scheduled start time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>End Time</para>
+ </entry>
+ <entry>
+ <para>The scheduled end time.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>% Completed</para>
+ </entry>
+ <entry>
+ <para>Completion</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration29"><title>Configuration</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Using the context menu, the view can be configured using the configure dialog.</para>
+ <para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_ganttview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Configuration Dialog</phrase>
+ </textobject>
+ <caption>
+ <para>Configuration Dialog</para>
+ </caption>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/taskperformanceview.docbook b/doc/taskperformanceview.docbook
new file mode 100644
index 00000000..3545dffb
--- /dev/null
+++ b/doc/taskperformanceview.docbook
@@ -0,0 +1,36 @@
+<sect2><title/>
+<para>On the task performance chart, we can analyze deeply each subtask or task with the same indexes as for the project performance view.
+</para>
+<para>This is really useful in a long and complicated project.
+</para>
+<para>On the left window, you can choose every single sub-task as well as an entire task, then on the right window will appear in the corresponding chart.
+</para>
+<para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_tasks_perf_chart.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+</para>
+<para>where:
+</para>
+<itemizedlist>
+ <listitem><para>BCWS means Budgeted Cost Work Scheduled,</para></listitem>
+ <listitem><para>BCWP means Budgeted Cost Work Performed,</para></listitem>
+ <listitem><para>ACWP means Actual Cost Work Performed.</para></listitem>
+</itemizedlist>
+<para>All these are considered as effort in hours and costs.
+</para>
+<para>PI are the Performance Indexes, where:
+</para>
+<itemizedlist>
+ <listitem><para>CPI is the Cost Performance Index,</para></listitem>
+ <listitem><para>SPI is the Schedule Performance Index.</para></listitem>
+</itemizedlist>
+</sect2>
diff --git a/doc/taskstatusview.docbook b/doc/taskstatusview.docbook
new file mode 100644
index 00000000..14b1b4db
--- /dev/null
+++ b/doc/taskstatusview.docbook
@@ -0,0 +1,214 @@
+<sect2><title/>
+<sect3 id="description22"><title>Description</title>
+ <para>
+ The Task Status View is used to inspect task progress information at a period, set in the configuration.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskstatusview.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The tasks are divided into groups dependent on the status of the task:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Not Started</para>
+ </entry>
+ <entry>
+ <para>Tasks that should have been started by now.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Running</para>
+ </entry>
+ <entry>
+ <para>Tasks that have been started, but not yet finished.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Finished</para>
+ </entry>
+ <entry>
+ <para>Tasks that were finished in this period</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Next Period</para>
+ </entry>
+ <entry>
+ <para>Tasks that are scheduled to be started in the next period.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data23"><title>Editing data</title>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>Progress information can be edited in-line as described <link linkend="using-the-views">here</link> or by using the task progress dialog.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskprogressdialog.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+ <para>The following columns are displayed as default:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry><guilabel>Column</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Name</para>
+ </entry>
+ <entry>
+ <para>The name of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Status</para>
+ </entry>
+ <entry>
+ <para>Task status</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>% Completion</para>
+ </entry>
+ <entry>
+ <para>Task completion</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Planned Effort</para>
+ </entry>
+ <entry>
+ <para>The amount of work planned to be used at the end of the current period.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Actual Effort</para>
+ </entry>
+ <entry>
+ <para>The amount of work spent.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Remaining Effort</para>
+ </entry>
+ <entry>
+ <para>The remaining effort needed to complete the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Planned Cost</para>
+ </entry>
+ <entry>
+ <para>The planned cost at the end of the current period.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Actual Cost</para>
+ </entry>
+ <entry>
+ <para>The actual cost incurred.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Actual Start</para>
+ </entry>
+ <entry>
+ <para>The actual start time of the task.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Actual Finish</para>
+ </entry>
+ <entry>
+ <para>The actual finish time of the task.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="configuration24"><title>Configuration</title>
+ <para>Using the context menu, the view can be configured to split / unsplit the tree view or it can be configured using the configure dialog.
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para>The configure dialog enables you to tailor the amount of information the view displays to fit your needs.</para>
+ </entry>
+ <entry>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskstatusview_config.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot></para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/usingtheviews.docbook b/doc/usingtheviews.docbook
new file mode 100644
index 00000000..4455d7cf
--- /dev/null
+++ b/doc/usingtheviews.docbook
@@ -0,0 +1,163 @@
+<sect2><title/>
+<sect3 id="description3"><title>Description</title>
+ <para>
+ The Task Editor is a view that displays task data in a tree structure. Most data in the Task Editor can be edited in situ.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_taskeditor.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+</sect3>
+<sect3 id="navigation"><title>Navigation</title>
+ <para>You can navigate the tree structure using the keyboard:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para><keycap>+</keycap></para>
+ </entry>
+ <entry>
+ <para>Expand an expandable row.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>-</keycap></para>
+ </entry>
+ <entry>
+ <para>Collapse a collapsible item.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Arrow left</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to previous column in the same row.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Arrow right</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to next column in the same row.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Arrow up</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to previous row in the same column.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Arrow down</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to next row in the same column.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Home</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to first row, first column.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>End</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to last row, last column.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Page up</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to first visible row in the same column.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycap>Page down</keycap></para>
+ </entry>
+ <entry>
+ <para>Go to last visible row in the same column.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data"><title>Editing data</title>
+ <para>Editable items are opened for editing by double-clicking on the item or, if using the keyboard, pressing <keycap>F2</keycap> will open the current item.
+ </para>
+ <para>When editing an item you can navigate to the next editable item as follows:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="2">
+ <tbody>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>Arrow left</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Go to the previous editable item in the same row.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>Arrow right</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Go to the next editable item in the same row.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>Arrow up</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Go to the next editable item in preceding rows.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para><keycombo>&Ctrl;&Alt;<keycap>Arrow down</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Go to the next editable item in succeeding rows.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="using-the-views-drag-drop"><title>Drag & drop and copy/paste</title>
+ <para>
+ Most views support drag & drop and copy/paste. Charts and Gantt charts can be dragged to applications that support images.
+ Table data uses the html mime type, so can be dropped on any applications that supports this.
+ If the view supports moving or copying items internally ⪚ the <link linkend="task-editor">Task Editor</link>, items can also be moved or copied.
+ </para>
+</sect3>
+</sect2>
diff --git a/doc/viewsandeditors.docbook b/doc/viewsandeditors.docbook
new file mode 100644
index 00000000..94ab7421
--- /dev/null
+++ b/doc/viewsandeditors.docbook
@@ -0,0 +1,50 @@
+<chapter id="startup-view"><title>Views and Editors</title>
+ <sect1 id="startup-view-section"><title>Startup View</title>
+ &startup-view-section;
+ </sect1>
+ <sect1 id="task-editor"><title>Task Editor</title>
+ &task-editor-section;
+ </sect1>
+ <sect1 id="resource-editor"><title>Resource Editor</title>
+ &resource-editor-section;
+ </sect1>
+ <sect1 id="work-and-vacation-editor"><title>Work and Vacation Editor</title>
+ &work-and-vacation-editor-section;
+ </sect1>
+ <sect1 id="cost-breakdown-structure-editor"><title>Cost Breakdown Structure Editor</title>
+ &cost-breakdown-structure-editor-section;
+ </sect1>
+ <sect1 id="task-dependency-editor-graphical"><title>Task Dependency Editor (Graphical)</title>
+ &task-dependency-editor-graphical-section;
+ </sect1>
+ <sect1 id="task-dependency-editor-list"><title>Task Dependency Editor (List)</title>
+ &task-dependency-editor-list-section;
+ </sect1>
+ <sect1 id="schedules-editor"><title>Schedules Editor</title>
+ &schedules-editor-section;
+ </sect1>
+ <sect1 id="project-performance-view"><title>Project Performance View</title>
+ &project-performance-view-section;
+ </sect1>
+ <sect1 id="task-performance-view"><title>Task Performance View</title>
+ &task-performance-view-section;
+ </sect1>
+ <sect1 id="task-status-view"><title>Task Status View</title>
+ &task-status-view-section;
+ </sect1>
+ <sect1 id="task-execution-view"><title>Task Execution View</title>
+ &task-execution-view-section;
+ </sect1>
+ <sect1 id="task-gantt-view"><title>Task Gantt View</title>
+ &task-gantt-view-section;
+ </sect1>
+ <sect1 id="milestone-gantt-view"><title>Milestone Gantt View</title>
+ &milestone-gantt-view-section;
+ </sect1>
+ <sect1 id="resource-assignment-gantt-view"><title>Resource Assignment Gantt View</title>
+ &resource-assignment-view-section;
+ </sect1>
+ <sect1 id="resource-assignment-view"><title>Resource Assignment View</title>
+ &resource-assignment-gantt-view-section;
+ </sect1>
+</chapter>
diff --git a/doc/workandvacationeditor.docbook b/doc/workandvacationeditor.docbook
new file mode 100644
index 00000000..72fdde1f
--- /dev/null
+++ b/doc/workandvacationeditor.docbook
@@ -0,0 +1,87 @@
+<sect2><title/>
+ <sect3 id="description10"><title>Description</title>
+ <para>
+ The Work and Vacation Editor is used to create, edit, and delete calendars.</para><para>Calendars define the working hours for resources. Calendars can also be used by tasks with estimate type <emphasis>Duration</emphasis>.
+ </para>
+ <para>
+ Calendars have a time zone specification so you can define working hours in the resources local time.
+ </para>
+ <para>
+ A calendar consists of definitions for weekdays and dates. If the date has a definition, this definition is used. If the state of the date is <emphasis>Undefined</emphasis>, the definition for the weekday is used. If this is also <emphasis>Undefined</emphasis>, the parent calendar is checked.
+ </para>
+ <para>
+ A calendar can be defined as <emphasis>Default</emphasis> and is then used by all working resources without a calendar reference.
+ </para>
+ <para>
+ <screenshot>
+ <screeninfo></screeninfo>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="plan_workandvacation.png" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase></phrase>
+ </textobject>
+ </mediaobject>
+ </screenshot>
+ </para>
+ <para>The toolbar provides the means to create and delete calendars:
+ </para>
+ <para>
+ <informaltable>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry><guilabel>Button</guilabel></entry>
+ <entry><guilabel>Shortcut</guilabel></entry>
+ <entry><guilabel>Description</guilabel></entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ <para>Add Calendar</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create a calendar. The new calendar is appended on the same level as the selected calendar.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Add Subcalendar</para>
+ </entry>
+ <entry>
+ <para><keycombo>&Ctrl;&Shift;<keycap>I</keycap></keycombo></para>
+ </entry>
+ <entry>
+ <para>Button to create child calendar. The new calendar is appended as a child to the currently selected calendar.</para>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <para>Delete Selected Calendar</para>
+ </entry>
+ <entry>
+ <para><keycap>Delete</keycap></para>
+ </entry>
+ <entry>
+ <para>Deletes the selected calendar.</para></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+ </para>
+</sect3>
+<sect3 id="editing-data11"><title>Editing data</title>
+ <para>Calendar name and time zone can be edited inline as described <link linkend="using-the-views">here</link>.
+ </para>
+ <para>The state of days and weekdays are edited by selecting the day or days you want to edit and open the context menu.
+ </para>
+ <para>Selecting <emphasis>Work...</emphasis> opens the Edit Work Intervals Dialog.
+ </para>
+
+</sect3>
+</sect2>
More information about the kde-doc-english
mailing list