Hi,
If the user enters text in the command line which has a start date/time
and a end date/time, the item is automatically stamped as a Calendar
event, whether the user explicitly says "/Event" or not. Eg: "/Msg
Meeting from 2-4pm " will create an item which is stamped as msg and
event both.
If the user creates an item (other than a event) with a single
date/time, the alarm is set at that date/time. If the date is mentioned
and no time is specified, the alarm is set at the custom time of 5pm. If
the user enters "/Event" with a single date/time, an at-time event is
created.
Thanks,
Darshana
Mimi Yin wrote:
We've been working through these very issues with Darshana for the
command-line-for-dummies quick item entry UI.
Darshana, could you chime in about how we're figuring out what's a
task versus an event?
I believe that only dates/times with duration are events, unless the
user specifically says it's an event. So it's in-line with what you're
describing below.
Mimi
On Sep 13, 2006, at 1:14 PM, Brian Kirsch wrote:
Hello,
Actually I am amending my Chandler Task IMAP folder to Chandler Task
suggestion.
Since Tasks in Chandler now have an alarm setting, if the Mail
Message contains a due date a custom alarm will be set when the IMAP
mail message is downloaded and stamped as Task in Chandler.
If the Mail message contains start and end dates etc. it should be
stamped as an Event and not a Task i.e. placed in the Chandler Event
folder on the IMAP server instead of the Chandler Task folder.
If the user places a Mail message with start and end info in the
Chandler Task folder I am open to suggestions as what to do. When
downloading to Chandler we could display a warning dialog such as
"This Task contains start and end date information would you like to
add it to your Calendar?" or simple ignore the date info and just
stamp it as a Task.
-Brian
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
