[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] [PATCH v2 10/11] org-taskjuggler: update doc to reflect latest chang
From: |
Yann Hodique |
Subject: |
[O] [PATCH v2 10/11] org-taskjuggler: update doc to reflect latest changes |
Date: |
Wed, 15 Aug 2012 21:11:56 +0200 |
---
doc/org.texi | 48 ++++++++++++++++++++++++++++++------------------
1 file changed, 30 insertions(+), 18 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 3fdb4ac..0f8b0d9 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -11898,9 +11898,9 @@ nodes of a document or strictly follow the order of the
nodes in the
document.
Instead the TaskJuggler exporter looks for a tree that defines the tasks and
-a optionally tree that defines the resources for this project. It then
-creates a TaskJuggler file based on these trees and the attributes defined in
-all the nodes.
+optionally trees that define the resources and reports for this project.
+It then creates a TaskJuggler file based on these trees and the attributes
+defined in all the nodes.
@subsection TaskJuggler export commands
@@ -11909,7 +11909,8 @@ all the nodes.
Export as a TaskJuggler file.
@orgcmd{C-c C-e J,org-export-as-taskjuggler-and-open}
-Export as a TaskJuggler file and then open the file with TaskJugglerUI.
+Export as a TaskJuggler file and then open the file with TaskJugglerUI (only
+for TaskJugglerUI 2.x).
@end table
@subsection Tasks
@@ -11947,15 +11948,17 @@ time.
@subsection Export of properties
-The exporter also takes TODO state information into consideration, i.e.@: if a
-task is marked as done it will have the corresponding attribute in
-TaskJuggler (@samp{complete 100}). Also it will export any property on a task
-resource or resource node which is known to TaskJuggler, such as
address@hidden, @samp{vacation}, @samp{shift}, @samp{booking},
address@hidden, @samp{journalentry}, @samp{rate} for resources or
address@hidden, @samp{start}, @samp{note}, @samp{duration}, @samp{end},
address@hidden, @samp{milestone}, @samp{reference}, @samp{responsible},
address@hidden, etc for tasks.
+The exporter also takes TODO state information into consideration, i.e.@: if
+a task is marked as done it will have the corresponding attribute in
+TaskJuggler (@samp{complete 100}). Scheduling information is also taken into
+account to set start/end dates for tasks.
+
+The exporter will also export any property on a task resource or resource
+node which is known to TaskJuggler, such as @samp{limits}, @samp{vacation},
address@hidden, @samp{booking}, @samp{efficiency}, @samp{journalentry},
address@hidden for resources or @samp{account}, @samp{start}, @samp{note},
address@hidden, @samp{end}, @samp{journalentry}, @samp{milestone},
address@hidden, @samp{responsible}, @samp{scheduling}, etc for tasks.
@subsection Dependencies
@@ -12001,11 +12004,20 @@ examples should illustrate this:
@vindex org-export-taskjuggler-default-reports
TaskJuggler can produce many kinds of reports (e.g.@: gantt chart, resource
allocation, etc). The user defines what kind of reports should be generated
-for a project in the TaskJuggler file. The exporter will automatically insert
-some default reports in the file. These defaults are defined in
address@hidden They can be modified using
-customize along with a number of other options. For a more complete list, see
address@hidden customize-group @key{RET} org-export-taskjuggler @key{RET}}.
+for a project in the TaskJuggler file. By default, the exporter will
+automatically insert some pre-set reports in the file. These defaults are
+defined in @code{org-export-taskjuggler-default-reports}. They can be
+modified using customize along with a number of other options. For a more
+complete list, see @kbd{M-x customize-group @key{RET} org-export-taskjuggler
address@hidden
+
+Alternately, the user can tag a tree with
address@hidden, and define reports in sub-nodes,
+similarly to what is done with tasks or resources. The properties used for
+report generation are defined in
address@hidden In addition, a special
+property named @samp{report-kind} is used to define the kind of report one
+wants to generate (by default, a @samp{taskreport}).
For more information and examples see the Org-taskjuggler tutorial at
@uref{http://orgmode.org/worg/org-tutorials/org-taskjuggler.html}.
--
1.7.11.4
- Re: [O] [PATCH v3 00/11] Taskjuggler exporter improvements, (continued)
- [O] [PATCH v2 01/11] org-taskjuggler: make task and resource properties customizable, Yann Hodique, 2012/08/15
- [O] [PATCH v2 02/11] org-taskjuggler: properly install local variables at export time, Yann Hodique, 2012/08/15
- [O] [PATCH v2 03/11] org-taskjuggler: make use of org properties, Yann Hodique, 2012/08/15
- [O] [PATCH v2 04/11] org-taskjuggler: fix milestone definition, Yann Hodique, 2012/08/15
- [O] [PATCH v2 05/11] org-taskjuggler: introduce a global header, for early macros, Yann Hodique, 2012/08/15
- [O] [PATCH v2 06/11] org-taskjuggler: use project end date, if specified, Yann Hodique, 2012/08/15
- [O] [PATCH v2 07/11] org-taskjuggler: make project umbrella task optional, Yann Hodique, 2012/08/15
- [O] [PATCH v2 08/11] org-taskjuggler: disambiguate "headline", as it's also a valid property, Yann Hodique, 2012/08/15
- [O] [PATCH v2 09/11] org-taskjuggler: allow reports definition from within the org file, Yann Hodique, 2012/08/15
- [O] [PATCH v2 10/11] org-taskjuggler: update doc to reflect latest changes,
Yann Hodique <=
- [O] [PATCH v2 11/11] org-taskjuggler: make taskjuggler compatible with org-publish, Yann Hodique, 2012/08/15