[Ml-yokadi] We should use Keyword in a smarter way

[Aurélien Gâteau]

Sébastien Renard wrote:
> Hello,
> 
> I've played some times with Yokadi competitors (yagtd, gtd, todo.sh, todo.py, 
> tudu...) and read some papers about Allen GTD.

I happen to own a copy of the GTD book :)

> Well... Yokadi is, from far, one of the best tools ;-). But it lacks some 
> usability.
> 
> Here's some of the good idea I find in other tools : 
> - the @keyword notation => very easy to use.

I do not think it is a good idea: it complicates the parser, and add 
more than one-way-to-do-it. I agree it saves two keystrokes ("@" vs "-k 
"), but we could save more by implementing keyword tab completion.

I believe the "@" character matches well with keywords describing a 
context (@phone, @computer, @work), but would look odd for other 
keywords. For example I use keywords to mark tasks which contains a 
patch with "patch", those which must be implemented before string freeze 
with "i18n", and those which I should backport with "backport".

> - project are not mandatory. Yes, we have the default project, but it could be 
> better.

Right now the default project is not very useful: to add a task to the 
default project one need to create a one word task with "t_add", this 
does not happen really often. To allow project-less tasks, we would need 
to make the project name an optional parameter.

> - allow to add keyword to project, so I can declare a project @work or @dev or 
> @buy. It save me to put the keyword on each tasks. Every tasks in the project 
> inherit from project keyword. This will change the database model. No patch 
> provivded for now, I am waiting for your thought and approval first.

I am not sure I understand. Can you give a more explicit use-case?

Aurélien