[Ml-yokadi] yokadi upstream

[Aurélien Gâteau]

Argh... #2, forgot to reply all again.
----
Sébastien Renard wrote:
> You forgot to answer to list ;-)

Argh. I hate it when mailing lists behave this way. I just changed the
list configuration :)

>> I reworked it a bit this evening to use the brand new
>> YokadiOptionParser, an OptionParser based class for yokadi commands :)
> 
> Good. Did you implement it in common class in order to make it  « 
> transparent » for all commands ?

Hum... no, there is no common class anymore :/. The parser needs to be
explicitly instantiated because you need to add your command options to it.

>> good, one more t_remove for me :)
> 
> Or t_mark_done ?

I tend to only mark done stuff I did myself :).

> 
> We will have to talk about archiving one day !

Hum... yes. Actually we were talking about this with Simon the other day :)

>>>> Copying this list just gave me the idea of another one:
>>>> - Provide a way to create a plain t_list (only titles)
>>> To be able to parse it easy in a script ? Well, we can make csv export
>>> more customisable to achieve this.
>> No I was thinking about making it easy to paste a list in a mail :)

> Exact, we don't need explicit subtask or subproject with such naming 
> convention. Maybe we could add this the the future user doc ?

Yes, definitely. This fits with my idea of Yokadi: provide a simple tool
  and let users define their work flow with it.

Aurélien