Overview
This document details new features in which a user can navigate around the Scooby web application to view events from their Chandler calendar.
Background
TBD.
0.2 Release
Goals and Objectives
The goal is be able navigate to different views to see the events on a Chandler calendar in the Scooby web application.
High Level Use Cases
- Instead of seeing the 'path name' on a dropdown box in Scooby, a user wants to see the 'display name' of the calendar. The 'path name' is not apparent to the user and my cause confusion.
- The user is attending a wedding September 8, 2006, five months ahead. Typing in the {mm/dd/yyyy} will help navigate to the exact date opposed to selecting the arrows at the top of the week view multiple times to view the correct date.
- A Minature Calendar will also help provide preview to the month ahead. For example if the user needs to see what day the wedding is in Septermber, five months ahead.
Requirements
Viewing Multiple Calendars: In Scooby 0.1 a user can move between calendar
1 and calendar 2 using a drop down box. Currently the 'path name' is displayed
instead of the 'display name' in the dropdown box.
Sidebar: Currently there is a sidebar in Chandler that displays all the collections. When selecting a collection in Chandler, the calendar canvas switches the focus of the events (overlayed on top of each other) to the selected collection. The sidebar in Chandler also displays the minical. (See description below.) The side bar for Scooby 0.2 will display the beginnings of the same features in Chandler.
Jump to date: An empty field with the title 'jump to date' allow users to type in the {mm/dd/yyyy}. This will bring up the week of that exact date.
Miniature Calendar (minical)
The minical will not be released in time for Scooby 0.2. The development for
the basic framework will commence during this timeframe. The user
can preview the month days/weeks/month ahead without having to select the
arrow buttons multiple times to view the specific date.
The following is a description for the basic functionality needed for a minature calendar in a target user's release.
- A miniature view of the current month and the month ahead will always be displayed on the web application. Location of the minical on the web application is tbd.
- Clicking on a specific date will have three states. A mouse rollover state: the specific date is highlighted. After three seconds if the mouse stays still in the hover state, a tool tip may appear displaying a message, ie. "Click here to jump to the date". A pressed state: where the specific date is highlighted in a differnt color/outline to indicate the date has been selected. The selected state: the entire week is selected with the specific date within the week.
- The specific date on the 'week view' of the calendar canvas is lightly highlighted. The minicall will have the week 'lightly' highlighted and the 'current day' will have a 'strong' highlight color.
Hiding the minical: A preference to hide/show the minical on the web application. This may preserve space on the web application.
Hover detail: A mouse hovering over the minical on days with events will bring up information on the event without jumping to that date/week or refreshing the page/week view area.
Assumptions
There are no assumtions at this time.
UI Details
The 'path name' should be invisable to the user. The 'display name' of the calendar needs to be consistent to the the calendar 'display names' in Chandler.
Open Issues
In Scooby 0.1, the drop down box does not appear until you have more then one calendar. Once you have more then one calendar, then the location of this drop down box is currently located on the top left of the screen.
- Will need to have visual on where this 'functionaltiy' should be
located and if the UI for switching between calendars should be a drop down
box in Scooby 0.2.
Code Design
[John/Matthew to add info here] This section must be completed by the developer. Schematic of any kind (class hierarchy, object relationship) is welcome.
Use this code style for code example or anything that needs to be typed on a command line.
Special Considerations
QA / Test
Any info that will be useful for testers.
API / Developer Platform
Security
N/A.
Internationalization / Localization
N/A.
Accessibility
UI must be accessible (Section 508).
Build / Install
[John/Matthew to add info here] New info that coders need to know introduced by that feature. List here known dependencies in particular.