Re: [O] taskjuggler - using gaplength or gapduration

2014-02-13 Thread Christian Egli
Hi all

frank f...@breengeosci.com writes:

 One issue that I am having is regarding gaplength and gapduration for
 tasks.  Under the TJ3 syntax, the command would be
  depends !!PHII {gapduration 7w} .

 I added gaplength and gapduration under ' Org Taskjuggler Valid Task
 Attributes ' and added the following in my org-mode file:

 *** PSF
 :PROPERTIES:
 :Task_id: PSF
 :depends: PHII
 :gaplength: 7w
 :duration: 10d
 :END:

 The resulting export comes out:
 depends !!PHII
 duration 10d
 gaplength 7w

 which is incorrect.  What am I doing wrong.

gaplength and gapduration need special treatment of the exporter. They
need to be part of the depends statement. So it woll not work if you
just add them as properties. The dependencies section in the comments of
ox-taskjuggler.el has an example how this can be done:

;; * Training material
;;   :PROPERTIES:
;;   :task_id:  training_material
;;   :ORDERED:  t
;;   :END:
;; ** Markup Guidelines
;;:PROPERTIES:
;;:Effort:   2d
;;:END:
;; ** Workflow Guidelines
;;:PROPERTIES:
;;:Effort:   2d
;;:END:
;; * Presentation
;;   :PROPERTIES:
;;   :Effort:   2d
;;   :BLOCKER:  training_material { gapduration 1d } some_other_task
;;   :END:

Now, I haven't tested this in a long time and AFAIK this used to work. I
don't know if it survived the port to the new exporter framework. I
would recommend that you try the above mentioned method. From looking at
the source code it seems that Nicolas implemented options on
dependencies.

Thanks
Christian

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




[O] taskjuggler - using gaplength or gapduration

2014-02-12 Thread frank
One issue that I am having is regarding gaplength and gapduration for 
tasks.  Under the TJ3 syntax, the command would be

 depends !!PHII {gapduration 7w} .

I added gaplength and gapduration under ' Org Taskjuggler Valid Task 
Attributes ' and added the following in my org-mode file:


*** PSF
:PROPERTIES:
:Task_id: PSF
:depends: PHII
:gaplength: 7w
:duration: 10d
:END:

The resulting export comes out:
depends !!PHII
duration 10d
gaplength 7w

which is incorrect.  What am I doing wrong.

Frank



Re: [O] taskjuggler - using gaplength or gapduration

2014-02-12 Thread John Hendy
Looks correct to me?

:gaplength: 7w - gaplength 7w
:duration: 10d - duration 10d

Do you mean to try:

*** PSF
:PROPERTIES:
:Task_id: PSF
:depends: PHII
:gapduration: 7w
:duration: 10d
:END:

I've not used these attributes, but assuming you pasted your actual file
correctly to the email, it looks like the properties are being directly
mapped to tj attributes. Let me know if I've missed something!


Thanks,
John


On Wed, Feb 12, 2014 at 2:11 PM, frank f...@breengeosci.com wrote:

 One issue that I am having is regarding gaplength and gapduration for
 tasks.  Under the TJ3 syntax, the command would be
  depends !!PHII {gapduration 7w} .

 I added gaplength and gapduration under ' Org Taskjuggler Valid Task
 Attributes ' and added the following in my org-mode file:

 *** PSF
 :PROPERTIES:
 :Task_id: PSF
 :depends: PHII
 :gaplength: 7w
 :duration: 10d
 :END:

 The resulting export comes out:
 depends !!PHII
 duration 10d
 gaplength 7w

 which is incorrect.  What am I doing wrong.

 Frank




Re: [O] taskjuggler - using gaplength or gapduration

2014-02-12 Thread John Hendy
On Wed, Feb 12, 2014 at 2:11 PM, frank f...@breengeosci.com wrote:

 One issue that I am having is regarding gaplength and gapduration for tasks.  
 Under the TJ3 syntax, the command would be
  depends !!PHII {gapduration 7w} .

 I added gaplength and gapduration under ' Org Taskjuggler Valid Task 
 Attributes ' and added the following in my org-mode file:


Ah, my apologies. Now I understand. I think you'll need Nicholas' or
someone else's help with this regarding the tj3 exporter. The typical
mapping is simply:

- Org

:property: value

- tj3

task {
property value
}

I just re-read how gaplength and gapduration work, and you'll need new
mapping of the :property: value to the output format so it ends up in
curly braces. I didn't catch that initially. The gapduration and
gaplength docs don't really make that clear, but the depends page
does:
- http://www.taskjuggler.org/tj3/manual/depends.html

So, no, you didn't do anything wrong, I just don't think the exporter
is setup to handle this sort of mapping.


John


 *** PSF
 :PROPERTIES:
 :Task_id: PSF
 :depends: PHII
 :gaplength: 7w
 :duration: 10d
 :END:

 The resulting export comes out:
 depends !!PHII
 duration 10d
 gaplength 7w

 which is incorrect.  What am I doing wrong.

 Frank




Re: [O] taskjuggler - using gaplength or gapduration

2014-02-12 Thread Nicolas Goaziou
Hello,

frank f...@breengeosci.com writes:

 One issue that I am having is regarding gaplength and gapduration for
 tasks.  Under the TJ3 syntax, the command would be
  depends !!PHII {gapduration 7w} .

 I added gaplength and gapduration under ' Org Taskjuggler Valid Task
 Attributes ' and added the following in my org-mode file:

 *** PSF
 :PROPERTIES:
 :Task_id: PSF
 :depends: PHII
 :gaplength: 7w
 :duration: 10d
 :END:

 The resulting export comes out:
 depends !!PHII
 duration 10d
 gaplength 7w

 which is incorrect.  What am I doing wrong.

I think it is, assuming PHII is already defined in the buffer,

  :depends: PHII {gapduration 7w}



Regards,

-- 
Nicolas Goaziou