- Revision
- 847
- Author
- mimi
- Date
- 2006-07-12 17:34:28 -0700 (Wed, 12 Jul 2006)
Log Message
For Alpha 4 Dashboard:
Tweak to behavior of Reminder column.
Smarter date column.
For Alpha 5 Dashboard: Auto-triaging events directly added to the calendar canvas.
New stuff is in BLUE :o)
Tweak to behavior of Reminder column.
Smarter date column.
For Alpha 5 Dashboard: Auto-triaging events directly added to the calendar canvas.
New stuff is in BLUE :o)
Modified Paths
Diff
Modified: trunk/docs/specs/rel0_7/Dashboard-0.7.html (846 => 847)
--- trunk/docs/specs/rel0_7/Dashboard-0.7.html 2006-07-12 19:57:15 UTC (rev 846) +++ trunk/docs/specs/rel0_7/Dashboard-0.7.html 2006-07-13 00:34:28 UTC (rev 847) @@ -612,7 +612,7 @@ Communication status and Reminder columns.</p> <p><b>Clickable Task, Communication status and Reminder columns:</b> One of the -features that was deferred from Alpha 2 wass the ability to toggle the +features that was deferred from Alpha 2 was the ability to toggle the state of an Item by clicking on the icon (or lack thereof) in the Task, Communication status and Reminder columns. The three columns behave differently from each other. Their individual behaviors are described @@ -954,6 +954,19 @@ </ul> <li>Reminder column should be sub-sorted by the Triage status column</li> </ul> +<p style="color: rgb(51, 51, 255);">Activating the Reminder icon in the +Reminder column blanks out the Date column for that row, overriding +whatever Date should be displayed in the Date column. User motivation: +This provides users with a way to 'tag' Items as 'Needs to be assigned +a Tickler date.'<br> +</p> +<p><span style="color: rgb(51, 51, 255);">However, once the user +assigns a Tickler date, the usual Date column rules apply. For example, +if the custom Tickler date is not the right Date to be displayed, both +the Tickler icon in the Reminder column and the Tickler date in the +Date column will be overridden by the Calendar stamp icon and the Event +Start-date and time. (See below in the Date column section for +specifics).</span> </p> <p><span style="font-weight: bold;">Staging proposal</span>: In the absence of custom-date ticklers, we can leave the current Calendar stamp the way it is today.<br> @@ -1332,52 +1345,60 @@ <li>All times appear in the form of <span style="font-weight: bold;">'(H)H:MM AM/PM' e.g. 3:30 PM</span></li> <span style="font-weight: bold;"><br> - </span> <li>If an Item has a custom-date Tickler, the <span - style="font-weight: bold;">custom</span> <span - style="font-weight: bold;">Tickler date</span> is displayed no matter -what; otherwise</li> + </span> <li style="color: rgb(51, 51, 255);">Always display the <span + style="font-weight: bold;">NEXT important date</span>.<br> + </li> + <li style="color: rgb(51, 51, 255);">If both the custom tickler and +event start dates/times have past, in other words, if there is no NEXT +important date, display the <span style="font-weight: bold;">Start +date and time</span> of the event.<br> + </li> + <li style="color: rgb(51, 51, 255);">If the custom tickler date has +past and there is no event date/time, keep displaying the <span + style="font-weight: bold;">Custom Tickler date.</span></li> </ul> <ul> - <li>If an Item is an Event the <span style="font-weight: bold;">Start-date -and time</span> (if there is one) is displayed; otherwise<br> + <li>If an Item is not an Event, always display the <span + style="font-weight: bold;">most RECENT date</span>: either +the <span style="font-weight: bold;">Date last modified</span> or the <span + style="font-weight: bold;">Date sent</span> which ever one happened +most recently.<br> </li> - <li>If an Item is not an Event, then the date displayed is either -the <span style="font-weight: bold;">Date last modified</span> or the <span - style="font-weight: bold;">Date sent</span> depending on what was the -last -action</li> <li>If an Item has none of these dates, the date column displays the <span style="font-weight: bold;">Date created</span>.</li> - <li>If both the custom tickler and event dates/times have PAST, in -other words, display the event date.</li> - <li>If the custom tickler date has past and there is no event -date/time, keep displaying the custom tickler date.<br> - </li> </ul> -<p>We would like to give the user the ability to edit the date column +<p><span style="font-weight: bold;">Deferred pending outcome of +Reminder column and Date column design for Alpha 4:</span> <span + style="text-decoration: line-through;">We would like to give the user +the ability to edit the date column but this functionality does not have to be in the first iteration of the Dashboard and can be deferred to Alpha5. Editing the date field -should only work for:<br> +should only work for:</span><br style="text-decoration: line-through;"> </p> -<ul> +<ul style="text-decoration: line-through;"> <li>Items with custom-date Ticklers. </li> <li> Items where the user has activated the custom-date Tickler by clicking in the Reminder column.</li> <li> Items that are on the Calendar.</li> </ul> -<p>We only want to allow editing in the date column IF deleting also +<p style="text-decoration: line-through;">We only want to allow editing +in the date column IF deleting also works. It doesn't make sense to have one with out the other.<br> </p> -<p>Deleting the date from the Date column results in the following:<br> +<p style="text-decoration: line-through;">Deleting the date from the +Date column results in the following:<br> </p> <ul> - <li> If the user has activated the custom-date Tickler in the + <li style="text-decoration: line-through;"> If the user has activated +the custom-date Tickler in the Reminder column, leave the Date column blank. It will serve as a reminder to the user that they still need to set a custom-date Tickler for that Item. </li> - <li> If the user has stamped the Item to add it to their + <li><span style="text-decoration: line-through;"> If the user has +stamped the Item to add it to their Calendar, leave the Date column blank. It will serve as a reminder to -the user that they still need to set a date for that event Item. </li> +the user that they still need to set a date for that event Item.</span> + </li> </ul> <h3>Sections</h3> <p>For Alpha 4, we would like to introduce sections just for Triage @@ -1524,6 +1545,30 @@ <h2><br> </h2> <h2>Alpha 5 Dashboard</h2> +<h3 style="color: rgb(51, 51, 255);">Auto-Triaging events that are +created directly on the Calendar</h3> +<ul style="color: rgb(51, 51, 255);"> + <li>For example, events created in the future (ie. after Today) are +set to LATER.</li> + <li>Events created for Today are set to NOW.</li> + <li>Events created in the Past are set to DONE.</li> +</ul> +<ul style="color: rgb(51, 51, 255);"> + <li>If it is 3PM and you create an event for 10AM Today, the event +should be set to DONE.</li> + <li>If it is 3PM and you create an all-day or anytime event for +Today, the event should be triaged as NOW.</li> + <li>If you create a multi-day event that starts before Today, but +ends either Today or after Today, the event should be set to NOW.</li> + <li>If you create a multi-day event that starts Today but ends after +Today, the event should be set to NOW.</li> +</ul> +<p style="color: rgb(51, 51, 255);">All the above is dependent on if +and how the user sets alarms on these items.</p> +<p><span style="color: rgb(51, 51, 255);">Users can manually change the +triage status at any time in the detail view of the event.</span><br> +</p> +<br> <h2>Beta Dashboard</h2> <p>The full spec for our Beta dashboard is still evolving. Much of this will be defined once we get something in front of users to look at. In
_______________________________________________ Commits mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/commits
