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

[Sébastien Renard]

Le mardi 10 février 2009, Aurélien Gâteau a écrit :
> > Do you want to remove the -k ?
>
> I would rather revert the change :/. If we want to go for @keyword, then
> I believe we should have a reflexion on our usage of OptionParser. I
> sometimes wonder whether Yokadi would be more usable if it featured a
> natural language.

Cf. Frederic post, yes we should. But with at least little structure to avoid 
black magic. Standard switch (-k --keyword) are quite to strict for common 
use but ideal for complex command (I think to t_list where it is perfect).

For t_add, we could use @ for keyword and other symbol for project (= for 
exemple)
t_add =myProject @aKeyword the title of the task @anotherKeyword

> I am not sure I understand what you mean. Early versions of Yokadi did
> not have projects: I thought projects could be implemented as keywords.
> It turned out to be annoying to use... I can't remember why, though.

If we have a symbol for project we could just omit project. Tasks would go to 
the "default project".

> OK I see. So "t_list -k work" would list all tasks with the "work"
> keyword and all tasks whose projects have the "work" keyword, am I correct?

Correct.

a+
-- 
Sébastien