Individual Status Reports for the Sphinx project team:

Name: Alex Mikitik http://www.users.qwest.net/~mikitikalex/alex/index.html

Date: 03-11-02

Accomplishments for last week:

- Got Jtree working & customized to project data. (No functionality)
- Marked backend for restructuring

Objectives for next week:
- Check out Jgraph (something that looks like the Mapper, and usable!)
- Add button functionality to Outliner

- Clean up Outliner code

Issues/Bugs
- “Links” implementation structure in backend

Name: Geoff Dugwyler http://academic.evergreen.edu/d/duggeo11/xml/

Date: 03-11-02

Accomplishments for last week:
- Revised data structure of backend (mapNodes now direct children)
- Got swing GUI to display appropriate node names from map data file.
- Updated newProject method to create directory structures & appropriate files.

Objectives for next week:
- Complete basic prototype of Outliner in Swing (for presentation)
- Work with Steve to integrate backend to his working Cocoa GUI

Issues/Bugs
- Need to finish backend functionality: non-tree links
-

Name: Steve Lynch http://www.oblivion.net/~retro/sphinx

Date: 03-11-02

Accomplishments for last week:

- Presented OSX Cocoa to the class
- Made the frame work for Outliner in Cocoa with backend code iimported

Objectives for next week:
- Get backend to work with Outliner
- Present again

Issues/Bugs
- The backend causes my code to die fast, have a lot of clues why, but exact cause isn’t isolated yet

Name: Randy Keller http://academic.evergreen.edu/k/kelran21/tech_comp

Date: 03-11-02

Accomplishments for last week:
- Restructured and scheduled team meetings to be more productive
- Prepared and presented OS X demo to class

Objectives for next week:
- Prepare for and give Sphinx demonstration to class
- Research junit.org
- Run at least one test suite for backend

- Download, print, and thoroughly understand newest version of code
- Update scope document, web site documentation
- Create updated paper prototypes for presentation
- Contact Apple resource with questions
- Talk to Gabe about how Runcilbe code is put together

Issues/Bugs
- Must understand the code and why things are done the way they are
-

Sphinx Project Progress Report http://academic.evergreen.edu/k/kelran21/sphinx

Meeting Attendance:

Monday: Randy, Geoff, & Alex

Tuesday: Randy, Geoff, Alex, & Steve

Wednesday: no meeting

Thursday: Randy, Geoff, Alex, Steve, & Kate

Friday: Randy, Geoff, Alex, & Steve

Issue 11: We need to evaluate the course this project is taking. We all need to be working together using the same technologies. (swing/pc vs Mac/Cocoa)

Status: We will discussed this on Tuesday, Feb. 19^th and did not arrive with a solution or plan, or any milestones or deliverables. We discussed this again on Monday, Feb. 25^th. Kate encouraged us to make a firm decision by Friday, March 1^st. We will consult Isaac, and meet as a team in the ACC Thursday & Friday night at 5:00 pm to have a work party. We will each evaluate the pros & cons of Swing –vs- Cocoa to help us with the decision. As of Friday March 8^th, we are all working on the Swing version to get ready for presentation to class

Issue 13: Need to prepare for Project demonstration (week 10)

Status: Need to identify what we are going to present to class and how.

Issue 14: Meetings need to be more useful and meaningful. We need to brainstorm on immediate solutions or things to accomplish, identify short-range tasks and commit to completion dates for these tasks.

Status: Randy and Alex had a long conversation and Alex came up with some good ideas for a new strategy. Alex will identify and assign short-term tasks. Meetings have been well attended, well received, and productive.