← Back to team overview

gtg-user team mailing list archive

Re: Adapting GTG to a custom workflow

 

Bryce Harrington wrote:
> On Wed, Apr 14, 2010 at 01:51:33AM +0200, Tomasz Melcer wrote:
>> [...]
> The new 0.3 codebase has added a functionality called "filters" which
> provide for views into the task tree.  There are four stock filters
> provided: workview, active, closed, and notag.  See filters_bank.py for
> details.
Good to see that. I don't mind hardcoding some filters for myself, this
might be good enough for my needs.

>> Task templates. I run a series of lectures at my university. For each
>> lecture I need to do a (fixed) set of tasks, there's almost 40 of them
>> (http://files.exroot.org/dump/tasks.png) with a complex dependency
>> relations. This set of tasks needs to be repeated for each lecture. I
>> don't want to reenter all the tasks by hand each time. To solve this
>> problem I wrote a simple python script to import a set of tasks from a
>> custom text format. A better solution would be to firstly prepare a
>> "template" inside GTG, then make a deep copy of it -- a good idea for a
>> plugin, I guess. Is there another way to do this?
> 
> I'd love to see more discussion of this idea, as task templates is
> something I'd really like to see myself as well.  Have you posted your
> import code to a bzr branch?
No, it wouldn't make sense. It uses few of my personal helper libraries
to parse my custom format, and it would take too much time to adapt them
for other people. Also, I guess I should rather make a simple converter
to your json format; no use in two competing formats.

>> Projects and tasks. My projects usually contain one or more tasks and a
>> repository of data (documents, links). Going from a task to its project
>> repository should be easy... but now it would involve making a link from
>> each task by hand.
> 
> Interesting, yes this is a work flow that gtg doesn't address yet,
> although there is a plugin for associating tasks to tomboy notes.
>
That gives me an idea for another quick&dirty solution (i love them
:-)): a plugin that would automatically add to new tasks all links to
tomboy notes which exist in parent task should be enough for me. This
would actually solve the task names problem for me: project's tasks
would be identified not by tags, but by a link to tomboy note containing
repository for a given project.

I'll wait for 0.3 to become more stable, and for my thesis to become
more complete...

Thanks for answer!

Tomasz Melcer

Attachment: signature.asc
Description: OpenPGP digital signature


References