[Ml-yokadi] feature request

Aurélien Gâteau aurelien.gateau at free.fr
Mon Aug 17 22:08:11 CEST 2009


David Faure wrote:
> On Wednesday 29 July 2009, Sébastien Renard wrote:
>> Le mardi 28 juillet 2009 23:36:33, Aurélien Gâteau a écrit :
>>> Not exactly: my proposition groups only on a specific keyword
>>> expression, not on all keywords. If I run "t_list @people% prj%" on the
>>> tasks listed above, I don't get an @i18n or an @backport group.
>> Ok. Indeed, I did not understand what you proposed. It's much more magic
>> ;-). But interesting for people who have multiple keywords on single tasks.
>>
>>> I can understand you find it a bit too magic to define the way tasks are
>>> grouped based on the criteria order, so here is another suggestion:
>>>
>>> We could introduce a "-g, --group" switch, which would takes as
>>> parameter the grouping keyword expression. This would turn my previous
>>> command into: "t_list -g @people% prj%" or "t_list prj% -g @people%". If
>>> "-g" is not set, then t_list would group by project, as before.
>> So we would have :
>> no option : grouping by project
>> -k : grouping by all keyword (like  zanshin context view)
>> -g : grouping by the given keyword (this one is yokadi exclusivity :D).
>>
>>
>> It's fine for me. David, you ask for a feature and we propose two solutions
>> :-). I hope at least one answer to your needs.
> 
> I'm quite confused now, actually, the details seem to escape me.
> The -g option sounds fine to me, what's the other solution?
> The "t_list @keyword projects" one, implicitly grouping on keywords?
> I guess explicit is better than implicit, for future extensions, no?

We decided to go for the -g option. It's just not done yet :)

Aurélien


More information about the Ml-yokadi mailing list