First of all, the project seems to look even more professional than
before,
and the screenshots are very promising.
***********
File / Item
***********
> when only a date is given. E.g., "@s 5/5" would give 12:00pm on May 5
Wouldn't it be more convinient to have parameter that says which
is the
default hour in these cases?
> Five types of alerts are now supported
I can't see the point distinguishing them - wasn't the one
commandline
(in this case it would be 'process') enough?
> Similary, this alert
>
> //
> @a e @t -2d &r
ema...@blah.com,
ema...@whatever.org @a file1, file2, file3
> //
>
> would send e)mails to the two listed r)ecipients exactly 2 days before the
> starting time of the event with the event summary as the subject, the event
> description with the date, time and location, if given, prepended as the
> body and with file1, file2 and file3 as attachments.
It makes thing much more complicated. Wouldn't
//
@a &t -2d 'mail_program --to="
ema...@blah.com,
ema...@whatever.org" --attach="file1, file2, file3"'
//
be enough (by the way I can see nonconsistency i usage of '@t'
and '&t'
as 'trigger').
> the following new types
>
> ^ all day event
> = delegated task
> ? someday / maybe
> & inbox
Well, I prefer 'The consistent use of datetimes precludes the
old way of
distinguishing an all day event by simply omitting the starting
time'
The delegated task I would write using actual syntax '@U
another_person'.
And I have no idea what item type are the las two. I would use
'@c
someday/maybe' and '@c inbox' for appropriate item type.
> 'default lines' beginning with a percent character, '%', are now supported
> and can be used anywhere in a data file
What will happen if there will be several such a lines in a
file?
First line only solved this problem.
> task groups ... the priority entries, @p, set the prerequisites
To be clear - if someone wants two task groups with different
priorities, one sets it in the initial group line, e.g.:
//
- garden fence @k projects @s tue @p 1
- pickup lumber @p 1 @c errands
- pickup paint @p 1 @c errands
- mend missing pieces @p 2 @c errands
- paint @p 3 @c errands
+ dog house @k projects @s tue @p 2
+ pickup lumber @p 1 @c errands
+ pickup paint @p 1 @c errands
+ cut pieces @p 2 @c shop
+ assemble @p 3 @c shop
+ sand @p 4 @c shop
+ paint @p 5 @c shop
//
if so, I like this solution.
> Unique id and time stamps
I can see the point introducing @I, @C and @M but it will cause
very
clumsy data file. I suppose that you intend to move to SQLite
adding
this elements or it will become unreadable.
Linking elements seems interesting, but actually this can be
performed
grouping items by projects.
I don't see how to use it with text file (my only idea is
similar to
this used in wikis - one makes direct link to article name).
*************
The wish-list
*************
1. Shortcut exiting from 'search' field (actually to search the string
one
uses <ctrl-s> but to leave it one needs to use mouse).
2. Shortcuts for every action, e.g. <f> for finishing actions without
need to
click appropriate button (just to remember about it).
3. Internationalisation (i18n) - possible use of national translation
of the
application. I can see, that it's not possible to translate the
syntax and
shortcuts, so I mean only interface translation.
Generally, it seems I am rather bremsing you :) but I loved the
simplification
done with change from 7xx to 8xx version, now it's going complicated
again.
Best wishes
----
Sebastian