[Commits] (sheila) 2nd draft - added content to date-time section

commits at osafoundation.org commits at osafoundation.org
Tue Apr 26 10:08:26 PDT 2005

Commit by: sheila
Modified files:
docs/specs/rel0_6/Detailview-0.6.htm 1.1 1.2

Log message:
2nd draft - added content to date-time section

ViewCVS links:

Index: docs/specs/rel0_6/Detailview-0.6.htm
diff -u docs/specs/rel0_6/Detailview-0.6.htm:1.1 docs/specs/rel0_6/Detailview-0.6.htm:1.2
--- docs/specs/rel0_6/Detailview-0.6.htm:1.1	Sun Apr 24 15:06:14 2005
+++ docs/specs/rel0_6/Detailview-0.6.htm	Tue Apr 26 10:08:25 2005
@@ -26,7 +26,7 @@
       <td width="33%">Authors: <a
  href="mailto:sheila at osafoundation.org">Sheila Mooney</a></td>
       <td width="33%">Last edited:<!-- #BeginDate format:Am1a --> April
-25, 2005 3:00 PM - Version 1.1<!-- #EndDate --></td>
+26, 2005 10:00 AM - Version 1.2<!-- #EndDate --></td>
       <td width="33%">Creation date: April 20, 2005</td>
@@ -136,8 +136,9 @@
 particular date but they do not have to indicate a specific time. These
 events appear in the top anytime area of the calendar view.</dd>
   <dt>@ Time Events</dt>
-  <dd>These are events where the user can specify a specific start date
-and time but they do not have to indicate an end time.</dd>
+  <dd>These are events that support the ability of a user to indicate
+when event starts but they aren't sure when it will end. The 4 date
+fields are filled in and the start date time matches the end date time.</dd>
 <p class="issue">Get Bryan S to add some other detail here if
@@ -214,34 +215,101 @@
 events, we wish to expand this to include multi-day events. For 0.6,
 date time fields should change to be structured as 4 separate
-fields as in the screen shot above. They should have the following
+fields as in the screen shot above.</p>
+<p>Creating a new event has the following default behavior. <br>
+  <li>By default, when creating a new event from the <b>File</b> menu,
+the date
+time fields default to the Anytime format. The <b>starts</b> field
+displays today's date and the associated time field shows the HH:MM
+format with no specific time. The <b>ends</b> field also displays
+today's date and the associated time has the HH:MM format.</li>
+  <li>When creating an event in-place by double clicking on the
+both the start date and time are filled in according to where the user
+clicked. The <b>ends</b> field display the same date as the <b>starts</b>
+field. The default duration for an event upon creation is 1 hour and
+the end time field automatically gets set according to the start time.</li>
   <li>All 4 fields are regular text fields and not "edit in place"
   <li>The format text should be displayed and in black since
 engineering indicated it was difficult to have gray text for 0.6.</li>
-  <li>To specify an <b>All-Day event</b>, check the All-Day checkbox.
-The 2
-ends fields (date and time) should disappear.</li>
-  <li>To specify an <b>Anytime event</b>, the user can simply type in
-a date
-only in the <b>starts</b> date field. Although we might want to have
-some UI
-to help the discoverability of this in the future we would like to keep
-this simple in 0.6.</li>
-  <li>To specify an <b>@ Time event</b>, the user simply specifies a
-start date and time and does not enter and end date and time.<br>
-  </li>
-  <li>To specify a <b>Multi-day event</b>, the user enters a start
-date and an
-end date. They do not have to enter data into the time fields. If they
-do, it's not added to the anytime area as a multi-day event but spans
-over that date and time range on the calendar view.</li>
+<p>Setting the various event types are described
+  <li><b>All-Day Events:</b> Check the All-Day checkbox.
+This causes the both the start and end time
+fields to
+disappear. For 0.6 an All-Day event exists for a single day or a
+multi-day depending on the values in the date fields.
+Unchecking the All-Day
+checkbox simply re-displays the start time and end time fields,
+populated with whatever data was in there previously. <br>
+  </li>
+  <li><b>Anytime Events:</b> The user can default to this
+by creating an event via the menu. Alternatively, they can simply
+delete whatever is in the start time and end time fields. If the start
+date matches the end date, it's an anytime event on that day,
+otherwise, it's a multi-day anytime event. We are hoping that by
+new events in the Anytime format, this will help with the
+discoverability of this feature.</li>
+  <li><b>@ Time Events:</b> Simply specify a
+matching start date, start time and end date and end time.<br>
+  </li>
+  <li><b>Multi-day Events:</b> These are supported in 3 formats. The
+specify and date and time range that spans multiple days ie: 05/01/05
+2:00pm - 05/03/05 1:00pm. This will display on the main calendar view.
+You can also specify an <b>All-Day Multi-Day</b> event by selecting
+All-Day checkbox and specifying an end date later than the start date.
+You can also specify an <b>Anytime Multi-Day</b> event which is done
+specifying an end date later than the start date and leaving the time
+fields blank or in HH:MM format. The later 2 formats display in the
+Anytime are of the calendar, the former in D logenze format and the
+later in regular lozenge format.<br>
+  </li>
+<p>The behavior when setting the various date-time combinations is
+described below.</p>
+  <li>Upon
+creating a new anytime event (start date = end date) adding a time in
+the end time field automatically updates
+the start time to create an event of 1 hour duration. If you had
+specified the start
+time instead, the end time would automatically populate to 1 hour in
+duration. If you then modify the start time to 3 hours before, this is
+  </li>
+  <li>If the start dates are different ie: 05/01/05 and 05/04/05 then
+the start time and end times can be any values.<br>
+  </li>
+  <li>If you change the start time to be after the end time, the end
+time updates to be an hour later than the start time. If the start time
+is 11:00pm, the end date automatically changes to the next day and the
+end time would be 12:00am.<br>
+  </li>
+  <li>Changing either the start time or the end time to be the same
+time as the other one is fine. If the dates are the same, this is
+simply an
+@ Time event. <br>
+  </li>
+  <li>Setting an end date EARLIER than a start date simply changes the
+start date to be the same as the end date.</li>
+  <li>If the user deletes both the time fields and the start and end
+dates DO NOT match, this is simply a Multi-Day event which appears at
+the top in the anytime area. If the start and end dates match, this is
+an anytime event.<br>
+  </li>
+  <li>If you try and delete the start or end date, they get reset to
+today's date when you try and tab/click out of the field.</li>
-  <p class="issue">[Sheila] Mimi, I need you to review all the cases
-above to make sure these are right.</p>
 <h3>Handling Recurring Events</h3>
 <p>For 0.6 we will be handling the display and creating of recurring
@@ -372,6 +440,11 @@
       <td>April 25, 2005</td>
       <td>First Draft</td>
+    <tr>
+      <td><a href="mailto:sheila at osafoundation.org">Sheila Mooney</a></td>
+      <td>April 26, 2005</td>
+      <td>Second Draft - Modifications to date-time section</td>
+    </tr>

More information about the Commits mailing list