[Ml-yokadi] yokadid updates and somes questions

Aurélien Gâteau aurelien.gateau
Mar 2 Déc 10:18:09 CET 2008


Sébastien Renard wrote:
> Le lundi 1 décembre 2008, Aurélien Gâteau a écrit :
>> Sébastien Renard wrote:
>>> Hello fellow yokadi citizen,
>>>
>>> I've made some update on yokadi daemon to ignore done tasks and esapce
>>> quotes in task title when launching external command.
>>>
>>> I've had to update default parameters ALARM_DELAY_CMD and ALARM_DUE_CMD
>>> to replace simple quote by double quotes.
>>> I don't know how to update that properly for existing yokadi
>>> installation, as default parameters are copied during db initialisation
>>> on first run. An update script for that is quite overkill isn't it ?
>>> Any idea ?
>> You can change the existing update script so that it replaces the
>> default value with the new if it hasn't been modified by the user.
> 
> Ok. So it needs to bump DB_VERSION ? That's not fully exact.

No, I think it's ok to include this in the current 1to2 update.

>> - Write a README, getting started doc
> 
> A basic user doc should be done with some samples. And a (also basic) web 
> site, because pulling a git repo is not friendly ;-).

Github can host wiki pages. This could be enough to get started. But I 
am not sure it can hosts tarballs.

@Simon: Maybe Sequanux can host the tarballs (and the site)?

>> - Doc update system
> 
> Do you mean API doc generated with doc.sh script ?

No. I mean finishing the documentation you can find in the header of 
update.py. It should include some tagging policy for example.

>> - When project does not exist, prompt the user to create|edit|cancel
> 
> This was done in september or october.

It's not exactly what I have in mind. My idea is something like this:

yokadi> t_add my new task
Project 'my' does not exist.
(c)reate it, (e)dit line, c(a)ncel?

>> - Show task title in t_mark* and t_remove
> 
> Done last week, you can pull it up from my repo. There's a cosmetic bug when 
> only one item can be completed, you have to press tab twice to clear display. 
> I don't know how to fix it. I suspect a readline/python issue.

You mean you can mark task done by name? interesting.
What I have in mind is a bit different: I just want Yokadi to output the 
name of the task marked as done, so that you could revert if you entered 
the wrong id.
In the case of t_remove, it should issue a confirmation message, which 
would include the task title.

> Here's my todo list (I removed items that you already mention above) : 
> - bug if task name have a dash => this must be done properly before 1.0

Ohhh, yet another bug introduced by YokadiParser I guess. Any idea on 
the way to handle this one?

> - link with git to mark_done a task when a special keyword is used in git. 
> This is a geek feature, it could be delayed after 1.0

This can probably be implemented as a git post-commit hook.

> - i18n for yokadi. This may have lots of impact and needs tests. It could be 
> delayed after 1.0

Yes, I think we can get 1.0 out without i18n for now. Especially given 
our target audience :)

> For all non dev stuff (user doc, screenshot, web site etc) we could try to 
> find enthousiast yokadi users. Do you know any ?

Hum... I have been lagging a bit with regards to my Yokadi evangelism 
duties... the Yokadi community (as I know it) is only three people at 
the moment :)

Aurélien


Plus d'informations sur la liste de diffusion Ml-yokadi