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

[Sébastien Renard]

Le lundi 9 février 2009, Aurélien Gâteau a écrit :
> 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 :)

;-)

> I do not think it is a good idea: it complicates the parser,

That's not a nice part. I admit.

> and add 
> more than one-way-to-do-it.

Do you want to remove the -k ?

> I agree it saves two keystrokes ("@" vs "-k 
> "), but we could save more by implementing keyword tab completion.

We do have ;-). Try it with t_list. But it does not work for t_add for now. It 
needs more work.

> 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".

It's not so great with other keyword, right. But easy to remember and quite 
common for people who used CLI todo list tools.

> > - 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.

Yes. But the "first word" position of project is a problem for that... And in 
the other hand, it is a simple solution to manage project. The t_edit make it 
easy to change project.
Could we say that project are just a special keyword named project ?

> > - 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?

I have some project related to work. I don't want to add keyword "work" to all 
of tasks in those project. And I would like to make a t_list -u @work

Same things for dev project or linux or kde project... 

I could use project hiearchy for that, but that's unidimensional...

a+
-- 
Sébastien