emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Setting taskjuggler project start date (ox-taskjuggler)
Date: Mon, 25 Mar 2013 02:17:02 -0500	[thread overview]
Message-ID: <CA+M2ft_5pFe7qdsBR9jmzGgdP9o3JEtOWBumksp7785_wX7_LA@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft9vgw3kYNQ4Jw=tJdqCDsYtJYn-LTca=-MT9tDwNZkbxw@mail.gmail.com>

On Mon, Mar 25, 2013 at 1:27 AM, John Hendy <jw.hendy@gmail.com> wrote:
> Having trouble setting the project start date, which results in a
> build error since my project started before today, and the default
> project start appears to be today's date. This was with no
> customization to the top level headline. Intuitively, I added a
> :start: property like so:
>
> #+begin_src org
>
> * Project                                               :taskjuggler_project:
>   :PROPERTIES:
>   :start:    2013-03-01
>   :END:
>
> #+end_src
>
> This results in (no change from exporting with no :start: property:
>
> #+begin_src TJ
>
> project nil "Project" "1.0" 2013-03-25 +280d {
> }
>
> #+end_src
>
> From digging around in ox-taskjuggler.el, it looks like the project
> gets defined here:
>
> #+begin_src ox-taskjuggler.el (line 607)
>
> (defun org-taskjuggler--build-project (project info)
>   "Return a project declaration.
> PROJECT is a headline.  INFO is a plist used as a communication
> channel.  If no start date is specified, start today.  If no end
> date is specified, end `org-taskjuggler-default-project-duration'
> days from now."
>   (format "project %s \"%s\" \"%s\" %s %s {\n}\n"
>           (org-taskjuggler-get-id project info)
>           (org-taskjuggler-get-name project)
>           ;; Version is obtained through :TASKJUGGLER_VERSION:
>           ;; property or `org-taskjuggler-default-project-version'.
>           (or (org-element-property :VERSION project)
>               org-taskjuggler-default-project-version)
>           (or (org-taskjuggler-get-start project)
>               (format-time-string "%Y-%m-%d"))
>           (let ((end (org-taskjuggler-get-end project)))
>             (or (and end (format "- %s" end))
>                 (format "+%sd" org-taskjuggler-default-project-duration)))))]
>
> #+end_src
>
> I'm no esliper, but I think I can track that the consecutive =%s=
> arguments are replaced by the successive function calls. That, and
> =org-taskjuggler-get-start project= looks like the ticket. That
> function is here:
>
> #+begin_src ox-taskjuggler.el (line 372)
>
> (defun org-taskjuggler-get-start (item)
>   "Return start date for task or resource ITEM.
> ITEM is a headline.  Return value is a string or nil if ITEM
> doesn't have any start date defined.."
>   (let ((scheduled (org-element-property :scheduled item)))
>     (and scheduled (org-timestamp-format scheduled "%Y-%02m-%02d"))))
>
> #+end_src
>
> So, that suggested that perhaps I needed to use :scheduled: instead of
> :start:. I tried that with the same results. It appears that this
> property /is/ applied at the task level for the top headline, however:
>
> #+begin_src TJ
>
> task project "Project" {
>   purge allocate
>   allocate jwhendy
>   start 2013-03-01
> ...
>
> }
>
> #+end_src
>
> So, it applies :start: to the top level project in the /task/
> definition area, but doesn't apply it to the very top level project
> definition.
>
> Any suggestions?

This works, though I know approximately nil (didja see what I did
there) about elisp:

#+begin_src ox-taskjuggler.el

(defun org-taskjuggler--build-project (project info)
  "Return a project declaration.
PROJECT is a headline.  INFO is a plist used as a communication
channel.  If no start date is specified, start today.  If no end
date is specified, end `org-taskjuggler-default-project-duration'
days from now."
  (format "project %s \"%s\" \"%s\" %s %s {\n}\n"
          (org-taskjuggler-get-id project info)
          (org-taskjuggler-get-name project)
          ;; Version is obtained through :TASKJUGGLER_VERSION:
          ;; property or `org-taskjuggler-default-project-version'.
          (or (org-element-property :VERSION project)
              org-taskjuggler-default-project-version)
          (or (org-element-property :START project)
              (format-time-string "%Y-%02m-%02d"))
          (let ((end (org-element-property :END project)))
            (or (and end (format "- %s" end))
                (format "+%sd" org-taskjuggler-default-project-duration)))))

#+end_src

I don't know why the org-taskjuggler-get-start function works for the
task definition and not the project definition... but just looking for
the contents of the :start: and :end: properties directly is my
current hack. I'll leave it like that just so I don't have to manually
change the .tjp file at every export, but I'm sure there's a "proper"
way to fix :)



John

>
>
> John

  reply	other threads:[~2013-03-25  7:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  6:27 Setting taskjuggler project start date (ox-taskjuggler) John Hendy
2013-03-25  7:17 ` John Hendy [this message]
2013-03-25  7:30   ` John Hendy
2013-03-25 20:15     ` Nicolas Goaziou
2013-03-25 22:14       ` John Hendy
2013-03-27 14:37         ` Nicolas Goaziou
2013-03-27 22:00           ` John Hendy
2013-04-24  8:30             ` Christian Egli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+M2ft_5pFe7qdsBR9jmzGgdP9o3JEtOWBumksp7785_wX7_LA@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).