Sent first e-mail about the project to Ryan Walsh and Caitlin Sullivan
Talked to Kernighan about feasibility of project.
We are now officially a group of four!
First Meeting. Decided on basic features
Met Joseph Perla to discuss implementation of SCG.
Discussed our upcoming meeting with Kernighan.
Met with Kernighan for the first official "project meeting". Installed Subversion
Installed Apache. Decided on Platform Level Architecture
Submitted Project Proposal with database structure
Found the Registrar's Magic Text Files
Experimented with various prerequisite expressions specifications. Some conceptual changes in design.
Met with John Grieb and got course table specifications
Group meeting. Discussed the use of separate pursuit codes in addition to group codes. Designed and agreed on user interface. Split up tasks based on newest block diagram.
Meeting with Haakon.
Preliminary Interface Specifications
Figured out (a) way to implement cross listings. Discussed the interface requirements of the GUI and the php interface of database access. Sketched preliminary class definition for database functions, and created a proof-of-concept rudimentary drag-n-drop implementation. Started coding! Work going on in import scripts, GUI and report generator
Created the prototype directory structure. Added a very rudimentary version of the the Pursuit.php interface as an example that we can work off of.
Preliminary creation script working. First database working! Database specifications updated.
Came up with a format for specifying groups and program requirements. Meeting with Haakon. Haakon wants back-end finished as soon as possible(?).
Started work on the php interfaces
Basic GUI template up
Initial version on report generator working
Initial Searching working
Prototype Presentation. Nearly complete database interface framework with most of the important accessor methods implemented, a basic functional set of scripts for data import, a working drag-and-drop interface to the course schedule, a basic keyword search, and a working report generator that produces so far pretty unreadable simplified prerequisite expressions.
GUI meeting after prototype. Discussed various design issues including the search bar.
Switched to POST. Database entry automated (without repetition of rows). Added crude processing indicator.
GUI restructuring: now all schedulepane functions separated to schedulepane.js
Database structure changed so that pursuits are part of groups with their own code so each pursuit has a primary group. Decided to revise language for prerequisite expressions
New version of report generator uploaded in preparation for major improvements in the future. Input/output format has changed. Output format now supports subexpression groups, clean syntax error handling, display of utilized pursuits, and multi-line printing of simplified expressions. PrereqReport.php needs to be changed significantly to conform with the new standard.
Realized Registrar's Prerequisites were very badly defined
Report Generator working!
Started testing with users
Tables now can have pursuits with the same code but different titles (except for groups, memberships). Fixed GUI so that it always displays two columns. People with lower resolution can just maximize their screen, and no more "pushing" of the schedulepane by the searchpane.
Work done on documentation