Re: [PATCH] Support for more flexible effort specifications in TaskJuggler exporter

[Christian Egli <christian.egli@sbs.ch>]

Hi Stuart

Stuart Hickinbottom <stuart@hickinbottom.com> writes:

> I've been experimenting with tracking medium-sized tasks in org as a
> work-breakdown and exporting to TaskJuggler to see just how many
> evenings and weekends I'll have to work to meet my promised deadlines! A
> recent patch (patch 638, 6th Match 2011) added support for more flexible
> effort estimate properties such as 4h, 3.5d etc.
>
> Unfortunately, at the moment the TaskJuggler exporter is more fussy over
> this property and only accepts HH:MM or an integer, both of which it
> translates to a number of days when exporting.
>
> The attached patch adds support for passing-through effort
> specifications when they're in the form "REAL UNIT" as they are for TJ,
> supporting the suffixes d, w, m and y in a consistent way to org.
> Support for HH:MM or bare number of days should still work as before. It
> also cleans up another couple of things about the export of effort:
>
> - HH:MM produces a floating point days duration now (was previously
> rounded to an integer)
> - The bare REAL effort regex failed to escape the decimal point (and
> would match any char)
> - Regexes now anchor to the string start to avoid matching the end of
> duff values
> - Docstring updated for more flexible effort specification

Thanks for your patch. I just pushed a patch along the lines of yours
which uses the built-in facilities of orgmode. It handles all effort
durations that are defined in `org-duration-string-to-minutes'. This
brings it in line with the rest of orgmode's effort handling. It also
fixes the documentation in org.texi.

Can you check and see if this fixes all your issues?

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