[Taskjuggler] Status of exporter

[Taskjuggler] Status of exporter

[Christian Egli]

Hi all

The Taskjuggler Exporter has seen some major updates. We finally have a
nice out-of-the-box experience with tj3, so please give it a spin.

What's new? Thanks to Nicolas Goaziou the exporter has been ported to
the new export engine. On top of that I added some features that have
been requested and there are some pending issues that I'd like to get
fixed, see below:

Changes
═══════

Process and open
────────────────

  Previously the exporter just exported a tjp file (at least for tj3).
  Now there is a new command to process the exported tjp file with tj3
  and open the reports in a browser.


Dependency resolution against plain IDs
───────────────────────────────────────

  There was some discussion on the list about dependency resolution. A
  good way to express dependencies is to use the org-id module. This is
  now supported in that it resolves dependencies not only against
  "task_id" but also against the "ID" of a task.


Default reports can use document title
──────────────────────────────────────

  John Hendy proposed to create a possibility to integrate the document
  title in the default reports. This is now possible by specifying a
  %title in the default reports. See the doc string of
  `org-taskjuggler-default-reports'.


Use both scheduled and start to determine project start
───────────────────────────────────────────────────────

  John Hendy again reported an problem that the project start was not
  using the scheduled info. This is now fixed.


Misc bug fixes
──────────────

  Nicolas Goaziou fixed a number of bugs and typos in the code.


Pending
═══════

Change mapping of DEADLINE property
───────────────────────────────────

  The DEADLINE property is currently mapped to the "end" attribute in
  the tjp export. The "end" attribute gives tj3 an indication as to when
  a task should end. Also it has some influence on the scheduling policy
  (ALAP) which might not be what the user expects. IMHO this is not
  exactly the semantics of the DEADLINE property. A better fit would be
  the "maxend" attribute. For that reason I'd like to propose a backward
  incompatible change to map the DEADLINE property to the "maxend"
  attribute.


Patch by Baptiste
─────────────────

  This patch fixes some problems with milestones. However it depends on
  above change.


Add the text nodes as a note
────────────────────────────

  It would make sense to export the text content of a headline as a tj3
  "note". The new export engine should make this possible.


-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

Re: [Taskjuggler] Status of exporter

[Carsten Dominik]

Thank you for your work and this update, Christian!

- Carsten

On 29.4.2013, at 22:52, Christian Egli <christian.egli@sbs.ch> wrote:

> Hi all
> 
> The Taskjuggler Exporter has seen some major updates. We finally have a
> nice out-of-the-box experience with tj3, so please give it a spin.
> 
> What's new? Thanks to Nicolas Goaziou the exporter has been ported to
> the new export engine. On top of that I added some features that have
> been requested and there are some pending issues that I'd like to get
> fixed, see below:
> 
> Changes
> ═══════
> 
> Process and open
> ────────────────
> 
>  Previously the exporter just exported a tjp file (at least for tj3).
>  Now there is a new command to process the exported tjp file with tj3
>  and open the reports in a browser.
> 
> 
> Dependency resolution against plain IDs
> ───────────────────────────────────────
> 
>  There was some discussion on the list about dependency resolution. A
>  good way to express dependencies is to use the org-id module. This is
>  now supported in that it resolves dependencies not only against
>  "task_id" but also against the "ID" of a task.
> 
> 
> Default reports can use document title
> ──────────────────────────────────────
> 
>  John Hendy proposed to create a possibility to integrate the document
>  title in the default reports. This is now possible by specifying a
>  %title in the default reports. See the doc string of
>  `org-taskjuggler-default-reports'.
> 
> 
> Use both scheduled and start to determine project start
> ───────────────────────────────────────────────────────
> 
>  John Hendy again reported an problem that the project start was not
>  using the scheduled info. This is now fixed.
> 
> 
> Misc bug fixes
> ──────────────
> 
>  Nicolas Goaziou fixed a number of bugs and typos in the code.
> 
> 
> Pending
> ═══════
> 
> Change mapping of DEADLINE property
> ───────────────────────────────────
> 
>  The DEADLINE property is currently mapped to the "end" attribute in
>  the tjp export. The "end" attribute gives tj3 an indication as to when
>  a task should end. Also it has some influence on the scheduling policy
>  (ALAP) which might not be what the user expects. IMHO this is not
>  exactly the semantics of the DEADLINE property. A better fit would be
>  the "maxend" attribute. For that reason I'd like to propose a backward
>  incompatible change to map the DEADLINE property to the "maxend"
>  attribute.
> 
> 
> Patch by Baptiste
> ─────────────────
> 
>  This patch fixes some problems with milestones. However it depends on
>  above change.
> 
> 
> Add the text nodes as a note
> ────────────────────────────
> 
>  It would make sense to export the text content of a headline as a tj3
>  "note". The new export engine should make this possible.
> 
> 
> -- 
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
> 
> 

Re: [Taskjuggler] Status of exporter

[Eric S Fraga]

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

Christian,

I must be doing something really silly (not unheard of ;-) but I just
cannot get the new tj3 exporter to work.  With an up to date org (as of
a few minutes ago), using the example from the tutorial but also an
example from Baptiste from last week, I get the following error message
when I try to export and open:

,----
| Saving file /tmp/x.tjp...
| Wrote /tmp/x.tjp
| Processing TaskJuggler file ./x.tjp...
| /tmp/x.tjp:26: Error: Unexpected token '==' found. Expecting one of :HTMLBLOB, :WORD, :REF, :HREF, :INLINEFUNCSTART, :ITALIC, :BOLD, :CODE, :BOLDITALIC, :FCOLSTART
| ==  ==
| if: TaskJuggler failed with errors: Error: Unexpected token '==' found. Expecting one of :HTMLBLOB, :WORD, :REF, :HREF, :INLINEFUNCSTART, :ITALIC, :BOLD, :CODE, :BOLDITALIC, :FCOLSTART
`----

I have TJ 3.4.0 and Ruby 1.9.1 installed on an Ubuntu system.

I have attached the x.org and x.tjp files in case they prove useful.

Any pointers would be most welcome.  I find that I need to create a
GANTT chart and, although I could use code I posted here a long time ago
for creating charts from org tables, I thought I'd revisit TJ...  the
aim would be to actually use TJ eventually for some of the project
management, from org obviously.

Thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.2-60-g713208

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: x.org --]
[-- Type: text/x-org, Size: 425 bytes --]

#+BEGIN_EXAMPLE
* Project                                               :taskjuggler_project:

** Training material
   :PROPERTIES:
   :task_id:  training_material
   :END:
*** Markup Guidelines
    :PROPERTIES:
    :Effort:   2d
    :task_id:  markup
    :END:
*** Workflow Guidelines
    :PROPERTIES:
    :Effort:   2d
    :END:
** Presentation
   :PROPERTIES:
   :Effort:   2d
   :BLOCKER:   markup
   :END:
#+END_EXAMPLE

[-- Attachment #3: x.tjp --]
[-- Type: application/octet-stream, Size: 1253 bytes --]

project nil "Project" "1.0" 2013-05-02 +280d {
}
shift s40 "Part time shift" {
  workinghours wed, thu, fri off
}
resource ucecesf "Eric S Fraga" {
}
task project "Project" {
  purge allocate
  allocate ucecesf
  task training_material "Training material" {
    task markup "Markup Guidelines" {
      effort 16.0h
    }
    task workflow "Workflow Guidelines" {
      effort 16.0h
    }
  }
  task presentation "Presentation" {
    depends !training_material.markup
    effort 16.0h
  }
}
textreport report "Plan" {
  formats html
  header '==  =='

  center -8<-
    [#Plan Plan] | [#Resource_Allocation Resource Allocation]
    ----
    === Plan ===
    <[report id="plan"]>
    ----
    === Resource Allocation ===
    <[report id="resourceGraph"]>
  ->8-
}

# A traditional Gantt chart with a project overview.
taskreport plan "" {
  headline "Project Plan"
  columns bsi, name, start, end, effort, chart
  loadunit shortauto
  hideresource 1
}

# A graph showing resource allocation. It identifies whether each
# resource is under- or over-allocated for.
resourcereport resourceGraph "" {
  headline "Resource Allocation Graph"
  columns no, name, effort, weekly
  loadunit shortauto
  hidetask ~(isleaf() & isleaf_())
  sorttasks plan.start.up
}

Re: [Taskjuggler] Status of exporter

[John Hendy]

[-- Attachment #1: Type: text/plain, Size: 2313 bytes --]

On Thu, May 2, 2013 at 3:18 PM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Christian,
>
> I must be doing something really silly (not unheard of ;-) but I just
> cannot get the new tj3 exporter to work.  With an up to date org (as of
> a few minutes ago), using the example from the tutorial but also an
> example from Baptiste from last week, I get the following error message
> when I try to export and open:
>
> ,----
> | Saving file /tmp/x.tjp...
> | Wrote /tmp/x.tjp
> | Processing TaskJuggler file ./x.tjp...
> | /tmp/x.tjp:26: Error: Unexpected token '==' found. Expecting one of :HTMLBLOB, :WORD, :REF, :HREF, :INLINEFUNCSTART, :ITALIC, :BOLD, :CODE, :BOLDITALIC, :FCOLSTART
> | ==  ==
> | if: TaskJuggler failed with errors: Error: Unexpected token '==' found. Expecting one of :HTMLBLOB, :WORD, :REF, :HREF, :INLINEFUNCSTART, :ITALIC, :BOLD, :CODE, :BOLDITALIC, :FCOLSTART
> `----
>
> I have TJ 3.4.0 and Ruby 1.9.1 installed on an Ubuntu system.
>
> I have attached the x.org and x.tjp files in case they prove useful.
>

Yeah, something's goofy with your report syntax, but I've just kind of
used the TJ3 report from their tutorial and tweaked it. I attached my
default report file which just gives me a gantt chart. I don't really
use the resource allocation much since I'm on a team for which I'm not
the manager of people's time and don't really have an idea of what %
of their overall load is dedicated to the project we work on together.
I'm interested in those assigned to a task and durations/estimates...
but not really what their overall load is.

Anyway, the .tji attached has a lot of stuff commented out that was in
the actual tj3 tutorial file. I left it for you so you can see some of
the other functionality they use, but I've turned it off as I'm just
not there yet and don't have time to learn more at the moment.


Hope that helps!
John

> Any pointers would be most welcome.  I find that I need to create a
> GANTT chart and, although I could use code I posted here a long time ago
> for creating charts from org tables, I thought I'd revisit TJ...  the
> aim would be to actually use TJ eventually for some of the project
> management, from org obviously.
>
> Thanks,
> eric
>
> --
> : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
> : in Emacs 24.3.50.1 and Org release_8.0.2-60-g713208

[-- Attachment #2: reports.tji --]
[-- Type: application/octet-stream, Size: 3611 bytes --]

### begin report definition
macro TaskTip [
  tooltip istask() -8<-
    '''Start: ''' <-query attribute='start'->
    '''End: ''' <-query attribute='end'->
    ----
    '''Resources:'''

    <-query attribute='resources'->
    ----
    '''Precursors: '''

    <-query attribute='precursors'->
    ----
    '''Followers: '''

    <-query attribute='followers'->
    ----
    '''Notes: '''

    <-query attribute='note'->
    ->8-
]

navigator navbar {
  hidereport 0
}

textreport frame "" {
  header -8<-
    == Project Plan ==
    <[navigator id="navbar"]>
  ->8-
  footer "----"
 
 textreport index "Overview" {
    formats html
    center '<[report id="overview"]>'
  }

#textreport "Status" {
#    formats html
#    center -8<-
#      <[report id="status.dashboard"]>
#      ----
#      <[report id="status.completed"]>
#      ----
#      <[report id="status.ongoing"]>
#      ----
#      <[report id="status.future"]>
#    ->8-
#  }

}


    # === Project Overview ===

    # Project Areas

    # * Technical Development
    # * Business Items
    # * NPI Deliverables
    # * Milestones


taskreport overview "" {
  header -8<-
    === Timeline/Deliverables ===
  ->8-
  columns bsi { title 'WBS' },
          name, start, chart { ${TaskTip} }

#  columns bsi { title 'WBS' },
#          name, start, end, duration, status, chart { ${TaskTip} }

  # For this report we like to have the abbreviated weekday in front
  # of the date. %a is the tag for this.
  timeformat "%Y-%m-%d"
  loadunit days
  hideresource 1
  sorttasks tree
  #caption 'All effort values are in man days.'

  # footer -8<-
  #   === Staffing ===

  #   All project phases are properly staffed. See [[ResourceGraph]] for
  #   detailed resource allocations.

  #   === Current Status ===

  #   The project started off with a delay of 4 days. This slightly affected
  #   the original schedule. See [[Deliveries]] for the impact on the
  #   delivery dates.
  # ->8-
}

# taskreport printout "Print" {
#            formats csv
#            columns id, name, duration, start, complete, precursors
#       }


#macro AlertColor [
#  cellcolor plan.alert = 0 "#00D000" # green
#  cellcolor plan.alert = 1 "#D0D000" # yellow
#  cellcolor plan.alert = 2 "#D00000" # red
#]

#taskreport status "" {
#  columns bsi { width 50 title 'WBS' }, name { width 150 },
#          start { width 100 }, end { width 100 },
#          duration { width 100 },
#          alert { tooltip plan.journal
#                          != '' "<-query attribute='journal'->" width 150 },
#          status { width 150 }

#  taskreport dashboard "" {
#    headline "Project Dashboard (<-query attribute='now'->)"
#    columns name { title "Task" ${AlertColor} width 200},
#            resources { width 200 ${AlertColor}
#                        listtype bullets
#                        listitem "<-query attribute='name'->"
#                        start ${projectstart} end ${projectend} },
#            alerttrend { title "Trend" ${AlertColor} width 50 },
#            journal { width 350 ${AlertColor} }
#    journalmode status_up
#    journalattributes headline, author, date, summary, details
#    hidetask ~hasalert(0)
#    sorttasks alert.down, plan.end.up
#    period %{${now} - 1w} +1w
#  }
#  taskreport completed "" {
#    headline "Already completed tasks"
#    hidetask ~(plan.end <= ${now})
#  }
#  taskreport ongoing "" {
#    headline "Ongoing tasks"
#    hidetask ~((plan.start <= ${now}) & (plan.end > ${now}))
#  }
#  taskreport future "" {
#    headline "Future tasks"
#    hidetask ~(plan.start > ${now})
#  }
#}


### end report definition 

Re: [Taskjuggler] Status of exporter

[Eric S Fraga]

John Hendy <jw.hendy@gmail.com> writes:

[...]

> Yeah, something's goofy with your report syntax, but I've just kind of

Is there something I can do in org to fix the report syntax?  I would
have thought that the /out of the box/ ox-taskjuggler would export
something that works.  Or is it my TJ configuration somehow?

> used the TJ3 report from their tutorial and tweaked it. I attached my
> default report file which just gives me a gantt chart. I don't really

Thanks.  Works well and does what I need!

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.2-65-g1e32d7

Re: [Taskjuggler] Status of exporter

[Christian Egli]

Hi Eric

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I must be doing something really silly (not unheard of ;-) but I just
> cannot get the new tj3 exporter to work.  

No, you found a bug in the exporter :-(.

> Any pointers would be most welcome.  

The problem is that I added a new feature which inserts the TITLE of the
document in the report. As it happens if you don't define a title it is
empty and the default report becomes invalid. So you could either

- define a document title (#+TITLE: Foo)
- define an export title (property 'EXPORT_TITLE')
- or git pull. I just pushed a fix that should use the headline of the
  project if the document title is empty.

Sorry for the inconvenience.

Christian

-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

-----
Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch

Re: [Taskjuggler] Status of exporter

[Eric S Fraga]

Christian Egli <christian.egli@sbs.ch> writes:

> Hi Eric
>
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>
>> I must be doing something really silly (not unheard of ;-) but I just
>> cannot get the new tj3 exporter to work.  
>
> No, you found a bug in the exporter :-(.
>
>> Any pointers would be most welcome.  
>
> The problem is that I added a new feature which inserts the TITLE of the
> document in the report. As it happens if you don't define a title it is
> empty and the default report becomes invalid. So you could either
>
> - define a document title (#+TITLE: Foo)
> - define an export title (property 'EXPORT_TITLE')
> - or git pull. I just pushed a fix that should use the headline of the
>   project if the document title is empty.
>
> Sorry for the inconvenience.
>
> Christian

Thanks!  No worries.  This is all work in progress, of course.  I've
updated my org and the example works just fine.

I now have other problems, as I have started defining an actual project
as opposed to the examples I have found on the list and on Worg.  I get
errors, having allocated efforts to all my tasks, that tasks do
not fit into the project time frame.  How is this time frame defined?
Do I need to specify something else in the org file?  The project I am
defining is several years long with tasks typically a number of months
long each.  Is there some default?  

I have tried allocating resources as well but get the same problem
regardless.

Example output (wrapped):

,----
| if: TaskJuggler failed with errors: Warning in scenario plan: Task
| workplan.framework.implementation.final does not fit into project time
| frame Warning: Task workplan.framework.implementation.final:
| 2014-02-06-17:00-+0000 -> <?> Error in scenario plan: Some tasks did not
| fit into the project time frame.
`----

Maybe I need to relearn taskjuggler...  If that's the case, please don't
hesitate to tell me.  Taskjuggler specifics are OT.

Thanks again,
eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.2-67-gc36435

Re: [Taskjuggler] Status of exporter

[Christian Egli]

Hi Eric

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> I get errors, having allocated efforts to all my tasks, that tasks do
> not fit into the project time frame. How is this time frame defined?

This is defined on the project. I think it is some kind of tj3
optimization to limit the space that it has to allocate.

> Do I need to specify something else in the org file? The project I am
> defining is several years long with tasks typically a number of months
> long each. Is there some default?

There is a default, see `org-taskjuggler-default-project-duration'. In
theory (according to the doc string of `org-taskjuggler--build-project')
you should also be able to set an "end" property on the project, but
this hasn't been implemented yet. You can set a deadline and this will
be used as an end date, but as I said before I might change this as a
DEADLINE maps more to maxend. So your best bet at the moment is to use
the default project duration.

Hope that helps
Christian
-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

Re: [Taskjuggler] Status of exporter

[Eric S Fraga]

Christian Egli <christian.egli@sbs.ch> writes:

[...]

> There is a default, see `org-taskjuggler-default-project-duration'. In

Thanks.  I have used #+BIND to set this.  However, it would be nice if
this variable did not assume days but instead allowed a TJ specification
(e.g. 6m, 4y).  I had to calculate how long 4 years was in days...

Mind you, I find TJ a bit annoying in how it deals with durations other
than days.  I can specify that a task is 1m long but TJ converts this to
4 weeks which is not the same.  I have to start thinking in terms of
weeks, I guess.

> this hasn't been implemented yet. You can set a deadline and this will
> be used as an end date, but as I said before I might change this as a
> DEADLINE maps more to maxend. So your best bet at the moment is to use
> the default project duration.

Done!

On the way home, I had another problem to do with resource allocation
but I can no longer reproduce it.  So it looks like I am all set!

Thanks for this exporter.

eric

-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.2-68-g40635b

Re: [Taskjuggler] Status of exporter

[Christian Egli]

Christian Egli <christian.egli@sbs.ch> writes:

> In theory (according to the doc string of
> `org-taskjuggler--build-project') you should also be able to set an
> "end" property on the project, but this hasn't been implemented yet.

I remember now what the problem with this was. The exporter uses the top
task both as the task and the container for the project[1]. So an start
and an end on this task applies to both the project and the task (which
is not always what you want). You might want to assign a start to the
top task but probably not an end. The end is supposed to be calculated
based on efforts and resource availability. But unless you specify a
default duration you will have to specify and end date for the
_project_.

Maybe we need some fake (in the sense that they are not tj3 attributes)
attributes to specify start and end of a project.

Thanks
Christian

Footnotes: 
[1]  Unless you set `org-taskjuggler-keep-project-as-task' to nil

-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

Org-mode and Taskjuggler

[Louis Turk]

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

 Hi Christian,

I'm very interested in your work to get Org-mode to export to
Taskjuggler version 3 --- very exciting! Being able to export to tj3
from org-mode would be extremely helpful to me. However, I'm having
trouble getting it to work. I suspect that the documentation I've been
reading is too old --- for version 2 of Taskjuggler---, and I have
version 3 installed.

Would you please send me:

 1. The related code in your .emacs file.
 2. A sample full-featured org-mode file that compiles successfully to tj3.
 3. Any up-to-date documentation that is available.
 4. Anything other information needed to get it to work.


 Thank you in advance for your help. And thanks for all your work
already done on this project.

Louis




[-- Attachment #2: Type: text/html, Size: 1215 bytes --]

Re: Org-mode and Taskjuggler

[Christian Egli]

Hi Louis

Louis Turk <lou@dayspringpublisher.com> writes:

> I'm very interested in your work to get Org-mode to export to
> Taskjuggler version 3 --- very exciting! Being able to export to tj3
> from org-mode would be extremely helpful to me. 

Cool.

> However, I'm having trouble getting it to work. I suspect that the
> documentation I've been reading is too old --- for version 2 of
> Taskjuggler---, and I have version 3 installed.

Yes, the documentation should be updated. John Hendy promised to do so a
while ago :-) (hint, hint).

What are the problems you are encountering? It should work out of the
box. Once you have an org file as explained on the worg page you just
invoke the exporter with C-c C-e J o for example and you should see the
schedule in a browser.

> Would you please send me:
>
> 1 The related code in your .emacs file. 

There is nothing special in my .emacs file. You need to include contrib
to your load path (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
and you need to enable the taskjuggler exporter (M-x customize
org-export-backends).

> 2 A sample full-featured org-mode file that compiles successfully to
>   tj3. 

The one on from the taskjuggler tutorial on the worg page should work.

> 3 Any up-to-date documentation that is available.

The best ATM is the tutorial on worg and the comments in the code.

> 4 Anything other information needed to get it to work.

If there is any other info needed then I'd say it is the official
TaskJuggler documentation.

> Thank you in advance for your help. And thanks for all your work
> already done on this project.

My pleasure.

HTH
Christian

-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

-----
Tag der offenen Tuer
Die SBS laedt Sie herzlich ein: 29. Juni 2013 von 9 bis 16 Uhr.
Mehr Informationen erhalten Sie unter http://www.sbs.ch/offenetuer

Re: Org-mode and Taskjuggler

[John Hendy]

[-- Attachment #1: Type: text/plain, Size: 2474 bytes --]

On Jun 11, 2013 3:46 AM, "Christian Egli" <christian.egli@sbs.ch> wrote:
>
> Hi Louis
>
> Louis Turk <lou@dayspringpublisher.com> writes:
>
> > I'm very interested in your work to get Org-mode to export to
> > Taskjuggler version 3 --- very exciting! Being able to export to tj3
> > from org-mode would be extremely helpful to me.
>
> Cool.
>
> > However, I'm having trouble getting it to work. I suspect that the
> > documentation I've been reading is too old --- for version 2 of
> > Taskjuggler---, and I have version 3 installed.
>
> Yes, the documentation should be updated. John Hendy promised to do so a
> while ago :-) (hint, hint).
>

Don't worry... I'm listening despite not being very active on the list
lately. Work is crazy, but I'm actually using tj3, so that will come in
handy when I get back to the documentation!

In the meantime, yes, more specific details about issues would let us help.

Sorry for the delay!

John

> What are the problems you are encountering? It should work out of the
> box. Once you have an org file as explained on the worg page you just
> invoke the exporter with C-c C-e J o for example and you should see the
> schedule in a browser.
>
> > Would you please send me:
> >
> > 1 The related code in your .emacs file.
>
> There is nothing special in my .emacs file. You need to include contrib
> to your load path (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
> and you need to enable the taskjuggler exporter (M-x customize
> org-export-backends).
>
> > 2 A sample full-featured org-mode file that compiles successfully to
> >   tj3.
>
> The one on from the taskjuggler tutorial on the worg page should work.
>
> > 3 Any up-to-date documentation that is available.
>
> The best ATM is the tutorial on worg and the comments in the code.
>
> > 4 Anything other information needed to get it to work.
>
> If there is any other info needed then I'd say it is the official
> TaskJuggler documentation.
>
> > Thank you in advance for your help. And thanks for all your work
> > already done on this project.
>
> My pleasure.
>
> HTH
> Christian
>
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
> -----
> Tag der offenen Tuer
> Die SBS laedt Sie herzlich ein: 29. Juni 2013 von 9 bis 16 Uhr.
> Mehr Informationen erhalten Sie unter http://www.sbs.ch/offenetuer

[-- Attachment #2: Type: text/html, Size: 3261 bytes --]

Re: Org-mode and Taskjuggler

[Louis Turk]

Hi Christian and others that are helping me,

Many thanks!  I've run into more problems, but I'm encouraged that with
your help I'll soon have Taskjuggler enabled.

On 06/11/2013 04:46 PM, Christian Egli wrote:
> Hi Louis
>
> Louis Turk <lou@dayspringpublisher.com> writes:
>
>> I'm very interested in your work to get Org-mode to export to
>> Taskjuggler version 3 --- very exciting! Being able to export to tj3
>> from org-mode would be extremely helpful to me. 
> Cool.
>
>> However, I'm having trouble getting it to work. I suspect that the
>> documentation I've been reading is too old --- for version 2 of
>> Taskjuggler---, and I have version 3 installed.
> Yes, the documentation should be updated. John Hendy promised to do so a
> while ago :-) (hint, hint).
>
> What are the problems you are encountering? It should work out of the
> box. Once you have an org file as explained on the worg page you just
> invoke the exporter with C-c C-e J o for example and you should see the
> schedule in a browser.
>
>> Would you please send me:
>>
>> 1 The related code in your .emacs file. 
> There is nothing special in my .emacs file. You need to include contrib
> to your load path (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
I did this.
> and you need to enable the taskjuggler exporter (M-x customize
> org-export-backends).

"M-x customize org-export-backends" did not work for me. If I type "M-x customize-group" then type "org" I get into org related stuff, but nothing about export-backends. And in trying to figure this out I somehow disabled C-c C-e, so now I can't export to anything. I'm hoping I haven't disable a whole lot of other commands also. How can I fix this?

I'm using Emacs 23.3 which is the latest version packaged by Mint Linux. Do I need to upgrade to version 24.1?

>
>> 2 A sample full-featured org-mode file that compiles successfully to
>>   tj3. 
> The one on from the taskjuggler tutorial on the worg page should work.
I am (and will be) using that file until I get everything working.
>
>> 3 Any up-to-date documentation that is available.
> The best ATM is the tutorial on worg and the comments in the code.
>
>> 4 Anything other information needed to get it to work.
> If there is any other info needed then I'd say it is the official
> TaskJuggler documentation.
>
>> Thank you in advance for your help. And thanks for all your work
>> already done on this project.
> My pleasure.
>
> HTH
> Christian
Thanks again.

Louis

Re: Org-mode and Taskjuggler

[Nick Dokos]

Louis Turk <lou@dayspringpublisher.com> writes:


> "M-x customize org-export-backends" did not work for me. If I type
> "M-x customize-group" then type "org" I get into org related stuff,
> but nothing about export-backends. And in trying to figure this out I
> somehow disabled C-c C-e, so now I can't export to anything. I'm
> hoping I haven't disable a whole lot of other commands also. How can I
> fix this?
>

Restarting emacs will probably restore C-c C-e.

What version of org-mode are you using? Do C-u M-x org-version RET to
find out. org-export-backends is new with 8.x, so if you are not running
v8.x, org-export-backends is not going to be present.

If you *are* running v8.x, do C-h v org-export-backends RET
and then click the customize link towards the bottom of the help text.
That will take you directly to the place where you can customize
the variable.

> I'm using Emacs 23.3 which is the latest version packaged by Mint
> Linux. Do I need to upgrade to version 24.1?
>

As mentioned above, the more interesting question is what version of
org you are running.

-- 
Nick

Re: Org-mode and Taskjuggler

[Louis Turk]

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

Hi Nick,

On 06/13/2013 01:21 PM, Nick Dokos wrote:
> If you *are* running v8.x, do C-h v org-export-backends RET
> and then click the customize link towards the bottom of the help text.
> That will take you directly to the place where you can customize
> the variable.
This does take me to the place, and even allows me to set the variable,
but it doesn't work. And it specifically says it must be set with M-x
customize.
But I've not bee able to find it so far. Or you can run some code, but I
don't know how yet.

I reinstalled org-mode from git, so I using version 8 now.

Louis


[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

Re: Org-mode and Taskjuggler

[Nick Dokos]

Louis Turk <lou@dayspringpublisher.com> writes:

> Hi Nick,
>
> On 06/13/2013 01:21 PM, Nick Dokos wrote:
>
>     If you *are* running v8.x, do C-h v org-export-backends RET
>     and then click the customize link towards the bottom of the help text.
>     That will take you directly to the place where you can customize
>     the variable.
>     
> This does take me to the place, and even allows me to set the
> variable, but it doesn't work. And it specifically says it must be set
> with M-x customize.  But I've not bee able to find it so far. Or you
> can run some code, but I don't know how yet.
>

What doesn't work? Please be more explicit.

There is a little triangle (or something) on the LHS of the Org Export
Backends: line - click that and you'll get a list of check boxes? Can
you see that? Did you check the box for Taskjuggler export? Did you
click "Apply" or "Apply and Save" afterwards?

> I reinstalled org-mode from git, so I using version 8 now.
>

OK.

-- 
Nick

Re: Org-mode and Taskjuggler

[John Hendy]

On Wed, Jun 12, 2013 at 11:38 PM, Louis Turk <lou@dayspringpublisher.com> wrote:
> Hi Christian and others that are helping me,
>
> Many thanks!  I've run into more problems, but I'm encouraged that with
> your help I'll soon have Taskjuggler enabled.
>
> On 06/11/2013 04:46 PM, Christian Egli wrote:
>> Hi Louis
>>
>> Louis Turk <lou@dayspringpublisher.com> writes:
>>
>>> I'm very interested in your work to get Org-mode to export to
>>> Taskjuggler version 3 --- very exciting! Being able to export to tj3
>>> from org-mode would be extremely helpful to me.
>> Cool.
>>
>>> However, I'm having trouble getting it to work. I suspect that the
>>> documentation I've been reading is too old --- for version 2 of
>>> Taskjuggler---, and I have version 3 installed.
>> Yes, the documentation should be updated. John Hendy promised to do so a
>> while ago :-) (hint, hint).
>>
>> What are the problems you are encountering? It should work out of the
>> box. Once you have an org file as explained on the worg page you just
>> invoke the exporter with C-c C-e J o for example and you should see the
>> schedule in a browser.
>>
>>> Would you please send me:
>>>
>>> 1 The related code in your .emacs file.
>> There is nothing special in my .emacs file. You need to include contrib
>> to your load path (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
> I did this.
>> and you need to enable the taskjuggler exporter (M-x customize
>> org-export-backends).
>
> "M-x customize org-export-backends" did not work for me. If I type "M-x customize-group" then type "org" I get into org related stuff, but nothing about export-backends. And in trying to figure this out I somehow disabled C-c C-e, so now I can't export to anything. I'm hoping I haven't disable a whole lot of other commands also. How can I fix this?
>

I'd really re-read through the upgrade guide:
- http://orgmode.org/worg/org-8.0.html#sec-6

The exporters start with ox-*.el now, not org-*, which may be why
you're not finding them. Also, if you're like me (and your comments
look like you are), you may enjoy using the second method to load
backends so that you have the variables accessible for
help/customization *prior* to exporting with the given backend the
first time.

This is sort of mentioned at the link above, covered in Section 3 of
Nicolas' original announcement:
- http://article.gmane.org/gmane.emacs.orgmode/65574

I also walked through it with examples of impact on another post:
- http://permalink.gmane.org/gmane.emacs.orgmode/71874)

It's also discussed on my blog; see the little section toward the end
called "Note on .emacs settings":
- http://jwhendy.blogspot.com/2013/03/migrating-to-new-org-mode-exporter-org.html

While the documentation is still in rough shape (sorry about that),
the tj3 page should at least get you to the point where you can C-c
C-e J for taskjuggler export:
- http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html

Almost everything from the old documentation regarding the Org file
structure is still applicable. The only thing that's really changed is
there's no gui in tj3 and the report format changed.

Keep the questions coming and good luck!

I'll try to get some further setup instructions up as well as porting
Taskjuggler's tutorial file and default report over to the tj3 page
within the next week or so.



John


> I'm using Emacs 23.3 which is the latest version packaged by Mint Linux. Do I need to upgrade to version 24.1?
>
>>
>>> 2 A sample full-featured org-mode file that compiles successfully to
>>>   tj3.
>> The one on from the taskjuggler tutorial on the worg page should work.
> I am (and will be) using that file until I get everything working.
>>
>>> 3 Any up-to-date documentation that is available.
>> The best ATM is the tutorial on worg and the comments in the code.
>>
>>> 4 Anything other information needed to get it to work.
>> If there is any other info needed then I'd say it is the official
>> TaskJuggler documentation.
>>
>>> Thank you in advance for your help. And thanks for all your work
>>> already done on this project.
>> My pleasure.
>>
>> HTH
>> Christian
> Thanks again.
>
> Louis
>
>

Re: Org-mode and Taskjuggler

[Christian Egli]

John Hendy <jw.hendy@gmail.com> writes:

> I'll try to get some further setup instructions up as well as porting
> Taskjuggler's tutorial file and default report over to the tj3 page
> within the next week or so.

Man, you're my hero. I thought I'd have to do this myself :-)

Thanks
Christian

-- 
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland

Re: Org-mode and Taskjuggler

[Louis Turk]

On 06/13/2013 09:06 PM, John Hendy wrote:
> On Wed, Jun 12, 2013 at 11:38 PM, Louis Turk <lou@dayspringpublisher.com> wrote:
>> Hi Christian and others that are helping me,
>>
>> Many thanks!  I've run into more problems, but I'm encouraged that with
>> your help I'll soon have Taskjuggler enabled.
>>
>> On 06/11/2013 04:46 PM, Christian Egli wrote:
>>> Hi Louis
>>>
>>> Louis Turk <lou@dayspringpublisher.com> writes:
>>>
>>>> I'm very interested in your work to get Org-mode to export to
>>>> Taskjuggler version 3 --- very exciting! Being able to export to tj3
>>>> from org-mode would be extremely helpful to me.
>>> Cool.
>>>
>>>> However, I'm having trouble getting it to work. I suspect that the
>>>> documentation I've been reading is too old --- for version 2 of
>>>> Taskjuggler---, and I have version 3 installed.
>>> Yes, the documentation should be updated. John Hendy promised to do so a
>>> while ago :-) (hint, hint).
>>>
>>> What are the problems you are encountering? It should work out of the
>>> box. Once you have an org file as explained on the worg page you just
>>> invoke the exporter with C-c C-e J o for example and you should see the
>>> schedule in a browser.
>>>
>>>> Would you please send me:
>>>>
>>>> 1 The related code in your .emacs file.
>>> There is nothing special in my .emacs file. You need to include contrib
>>> to your load path (add-to-list 'load-path "~/src/org-mode/contrib/lisp")
>> I did this.
>>> and you need to enable the taskjuggler exporter (M-x customize
>>> org-export-backends).
>> "M-x customize org-export-backends" did not work for me. If I type "M-x customize-group" then type "org" I get into org related stuff, but nothing about export-backends. And in trying to figure this out I somehow disabled C-c C-e, so now I can't export to anything. I'm hoping I haven't disable a whole lot of other commands also. How can I fix this?
>>
> I'd really re-read through the upgrade guide:
> - http://orgmode.org/worg/org-8.0.html#sec-6
>
> The exporters start with ox-*.el now, not org-*, which may be why
> you're not finding them. Also, if you're like me (and your comments
> look like you are), you may enjoy using the second method to load
> backends so that you have the variables accessible for
> help/customization *prior* to exporting with the given backend the
> first time.
>
> This is sort of mentioned at the link above, covered in Section 3 of
> Nicolas' original announcement:
> - http://article.gmane.org/gmane.emacs.orgmode/65574
>
> I also walked through it with examples of impact on another post:
> - http://permalink.gmane.org/gmane.emacs.orgmode/71874)
>
> It's also discussed on my blog; see the little section toward the end
> called "Note on .emacs settings":
> - http://jwhendy.blogspot.com/2013/03/migrating-to-new-org-mode-exporter-org.html
>
> While the documentation is still in rough shape (sorry about that),
> the tj3 page should at least get you to the point where you can C-c
> C-e J for taskjuggler export:
> - http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html
>
> Almost everything from the old documentation regarding the Org file
> structure is still applicable. The only thing that's really changed is
> there's no gui in tj3 and the report format changed.
>
> Keep the questions coming and good luck!
>
> I'll try to get some further setup instructions up as well as porting
> Taskjuggler's tutorial file and default report over to the tj3 page
> within the next week or so.
>
>
>
> John
I apologize and thank you! Somehow I totally missed the links in this
email the first time I read it. I'm up and running now.

Thanks again to you all for you great work!

Louis


>
>
>> I'm using Emacs 23.3 which is the latest version packaged by Mint Linux. Do I need to upgrade to version 24.1?
>>
>>>> 2 A sample full-featured org-mode file that compiles successfully to
>>>>   tj3.
>>> The one on from the taskjuggler tutorial on the worg page should work.
>> I am (and will be) using that file until I get everything working.
>>>> 3 Any up-to-date documentation that is available.
>>> The best ATM is the tutorial on worg and the comments in the code.
>>>
>>>> 4 Anything other information needed to get it to work.
>>> If there is any other info needed then I'd say it is the official
>>> TaskJuggler documentation.
>>>
>>>> Thank you in advance for your help. And thanks for all your work
>>>> already done on this project.
>>> My pleasure.
>>>
>>> HTH
>>> Christian
>> Thanks again.
>>
>> Louis
>>
>>

Re: [Taskjuggler] Status of exporter

[Eric S Fraga]

Christian,

ignore my previous email re: time span for the project.  Having looked
at your code, I see that you make use of the SCHEDULED and DEADLINE
properties of the top headline.  This is obvious (in hindsight).  So
this works.

I now have a further problem which I will email later when I am back
online.  I am currently on the train home without Internet access (which
means that this email may cross any from you or others).

Thanks again,
eric
-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 and Org release_8.0.2-68-g40635b

Re: Org-mode and Taskjuggler

[John Hendy]

Just wanted to post and update that I finally put some more work into
the Taskjuggler (tj3) documentation on Worg. Still haven't migrated
over the export file, but added more about the available settings,
pointed to some helpful tj3 documentation, and mapping tj3 syntax to
Org property syntax.

I was planning to use a simple home renovation project (which I am
undergoing, hence my massive delays in contributing) as an example to
walkthrough basic steps and task attributes.

I can still create a tj3 compatible version of the official
Taskjuggler tutorial in Org-mode format (or probably just modify the
TJ v2.4.3 one that's used at the other Taskjuggler worg tutorial) as a
more full capability example.

Lastly, unless the default report definition is done, I'll include a
reports.tji file with the default Taskjuggler report definition from
their tutorial example as well.

Feedback is welcome based on how the above sounds.

- http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html

I noticed that this isn't seeming to be indexed by google. I moved it
from the following location probably 2-3 months ago, but when I search
"orgmode taskjuggler tj3," only the previous location comes up as a
search results:

- http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html

Is the dir structure too deep to get indexed?


John

Re: Org-mode and Taskjuggler

[Nick Dokos]

John Hendy <jw.hendy@gmail.com> writes:

> Just wanted to post and update that I finally put some more work into
> the Taskjuggler (tj3) documentation on Worg. Still haven't migrated
> over the export file, but added more about the available settings,
> pointed to some helpful tj3 documentation, and mapping tj3 syntax to
> Org property syntax.
>
> I was planning to use a simple home renovation project (which I am
> undergoing, hence my massive delays in contributing) as an example to
> walkthrough basic steps and task attributes.
>
> I can still create a tj3 compatible version of the official
> Taskjuggler tutorial in Org-mode format (or probably just modify the
> TJ v2.4.3 one that's used at the other Taskjuggler worg tutorial) as a
> more full capability example.
>
> Lastly, unless the default report definition is done, I'll include a
> reports.tji file with the default Taskjuggler report definition from
> their tutorial example as well.
>
> Feedback is welcome based on how the above sounds.
>

Sounds good to me. The org example blocks were coming out funny (at
least on the chromium browser) so I added commas in front of the
"headlines" (I also made them org src blocks, but I'm not sure that's
the right thing to do). In any case, they look better to me, but can you
take a look and make sure that I didn't screw anything up? Also the footnote
seems to be obsolete, but I didn't change it.

> - http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html
>
> I noticed that this isn't seeming to be indexed by google. I moved it
> from the following location probably 2-3 months ago, but when I search
> "orgmode taskjuggler tj3," only the previous location comes up as a
> search results:
>
> - http://orgmode.org/worg/org-tutorials/org-taskjuggler3.html
>
> Is the dir structure too deep to get indexed?
>
>
> John
>
>

-- 
Nick