...
Instructions for accessing and starting up our computer prototype
Our prototype is web-based and can be found here: CalendarShare
Platform and Software Requirements:
Browser: Google Chrome 10
Resolution: Maximized (tested at 1680x1050)1280 x 800
Implementation Details
Fully implemented:
- Creating, editing, and deleting of events
- Creating, editing, and deleting of deadlines
- Adding Creating, editing, and deleting notes
- Accurate calendar navigation with correct month layout
Incompletely implemented:
Not implemented:
- and ability to select a particular day
- Event creation/editing forms that restrict user input to a valid range.
- We have not yet implemented account management the login/account management stuff.
- Remembering your ....There are no canned responses – everything is generated dynamically and saved as long as you don't reload a pagenavigate to a different month
Not implemented:
- We have not yet implemented an account management interface. Therefore, all users will see "Hello, Guest" in the corner along with "Log Out" text that is static.
- We have not yet implemented a visual representation for the backward propagation of deadlines. For example, if a user asks to be reminded about a deadline 7 days before it occurs, we would like to have a colored line on each of the 7 days before the deadline. This will be present once we have a backend.
- Persistency of calendar data. All events and deadlines that are created in a single month will be present in the application. When a user navigates to a different month, events and deadlines disappear. This will be fixed with a backend. Notes are persistent until a user refreshes the webpage. When a user refreshes the page, all data is lost. This will be fixed when we create a backend to store the user's calendar data with his/her account information.
Scope Reductions
Due to the loss of a group member, we eliminated some features of our design.
...