Winter Quarter 1996 January 23, 1996 Document Author: Eugene Liang Project Sponsor: Gregory Abowd

Yakko Wakko and Dot Profile Team: Manager: Harry Marlin Architect: Tom Moss Programmer: Mark Canup Programmer: Roy Rodenstein Programmer: Anind Dey Technical Writer: Eugene Liang

Purpose of the Project History Page

The Project History page is used to keep track the progress of the project. It notes the progress that were made and also records the significant decisions that were made in the project meeting.

January 12, 1996

• Decided on the project topic: Java Calendar

• Responsibilities are divided among the group members:
  • Project Manager - Harry Marlin
    
  • Architect - Tom Moss
    
  • Technical Writer - Eugene Liang
    
  • Programmer - Mark Canup
    
  • Programmer - Roy Rodenstein
    

• Met with Anind Dey (anind@cc.gatech.edu) and discussed the essential elements for the Calendar Project that we need to implement. We decided that four modules are essential for the project:
  • Be able to view the calendar in monthly format. Roy Rodenstein is assigned to implement the monthly viewer module.
  • Be able to parse the .dayplan file in the user's account and display the schedule on the browser. Mark Canup is assigned to implement the parsing module.
  • Be able to view the calendar in hourly format. Anind Dey is assigned to implement the hourly viewer module.
  • Be able to overlay multiple schedules and display open time slots available for meeting. Currently no one is assigned to implement this module.

• Decided that Anind Dey will work with us and be the third programmer for the project.

• Decided on a weekly meeting time: Tuesday at 13:00.

• Anind Dey informed us of the Java repository: http://www.gamelan.com/

• Received the project plan comments from Dr. Abowd. The comments can be found in
  http://www. cc.gatech.edu/computing/SW_Eng/JavaCalendar/Archive/ plan_comments.html

• Mark Canup worked on exception-handling. Status: "If you run the applet from "appletviewer," the URL can be a file:// but naturally when run from Netscape 2.0b6, it said that it is an insecure file and cannot read type; however, you still can access anything in the public_html directories wheather it is HTML or not. Try http://www.prism.gatech.edu/~rr83/testing.

• Roy Rodenstein worked on graphical interface. Status: "Java is flaky. I got a grid similar to Sunil's (month view, 30/31 buttons, one for each day), but then the next time I ran it, nothing showed on the screen, with no changes made. It was quite annoying. Anyway, if I can get the buttons to _show up_ I think I am in good shape as for the rest - calling y'all's modules."

• Discuss the differences between the functional requirements and non-functional requirements. We decided that even though we might not be able to write to the client's machine, we will still put "editing dayplanner" as one of the functional requirements since this function is something that all dayplanner should have.

• Mark spend most of time writing the DayPlanData code. Did not realize that he needed it to be in multiple fiels. Correct the problem.

• Mark spoke with Dr. Abowd regarding the problem with the daily display.

• Decide that the daily display should contain two sections, one section that lists the time that someone has scheduled, and another section that shows all the appointments for that date. The two windows will be linked such that if a user click on the time, the "free-text" area will scroll to the explaination of events that's happening at that time.

• Anind shows us a version of the daily display; however, there does not exist the seperate window functionality we desired.

• At the meeting, decide that Mark will work on the Overlay display. Discussed that the overlay display will contain a edit user button that allows the user to add and delete multiple calendar.

• Decide that Anind will work on the pop-up window that chooses the multiple calendar. The window should contain the previously selected people for the user to add and delete.

• Mark worked on the Bar graphs and have things communicate with one another. Decided on the color scheme.

• Prototype ready for demo. Still contain some bugs that needs fixing. One problem that exists is that the YWD Dayplanner is unable to add new users to the list of overlays. The problem only occurs in the Netscape 2.0 browser. Otherwise, the program work fine AppletViewer.

• We wish to allow the user to edit the YWD Dayplanner. This will probably not be implemented until the Netscape security system allows writing to the client side.

Top	Plan	Req Doc	Design Doc	Prototype	History	Revision

---

Last modified: January 19, 1996 by Eugene Liang (eugene@cc.gatech.edu)