[Ml-yokadi] yokadid updates and somes questions

[Sébastien Renard]

Le mardi 2 décembre 2008, Aurélien Gâteau a écrit :
> 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.

Ok, I add that task in my list.

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

Exactly, I forgot that !

> This could be enough to get started. 

I think, yes.

> But I  
> am not sure it can hosts tarballs.
>
> @Simon: Maybe Sequanux can host the tarballs (and the site)?

I have a box online 24/24 7/7 that can host tarballs.

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

Ok, a dev doc. Yes, you're right.

> It should include some tagging policy for example.

Exact. For each public release and each datamodel change (following 
DB_VERSION) ?

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

I don't see the point. Create already exists, cancel also. Edit line is just 
cancel and arrow up to get back last line.

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

Not really. You can complete on task ID and then all task for whic ID start by 
the ID you given are displayed.

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

You can do that by completing (tab). But then if there's only one task 
matching, you're bitten by the bug I mention above.

> In the case of t_remove, it should issue a confirmation message, which
> would include the task title.

Yes, but with a -f to force (I am thinking to yoakdi scripting where we should 
always have non interactive version of commands).

But default should prompt for t_remove, you're right. But not for mark_done or 
start.

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

I don't know if it's possible to overide parser error routine to just ignore 
unknown option and let them as text in the « args » part.

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

Yes, of course, I have that in mind.

> > - 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 :)

Arhh. We have to spread yokadi all over the world. A web site and announce on 
freshmeat and python cheeseShop should do the trick. We will receive very 
few « thanks  » but lots of bug and billions of wish ;-)

I try to spread around be but people said  « oh, it's too geek for me »  ! 
Hey, that's what I like in Yokadi !

a+
-- 
Sébastien