Re: [onebook-core] Contribution Summaries

[joel d. <di...@co...>]

Here it is, Eric.  Thanks.

Code: Most of the code I wrote was for the Browser.  This includes code
addded to most of the primitives to make them browseable, as well as an 
extensive UI for creating, browsing, and editing instances of those 
primitives.  Additionally, I implemented delete() methods for all the 
primitives, including reference-counting code in the case of directories, 
and implemented cycle avoidance for the Group, Directory, and Document 
hierarchies.  I also wrote our custom tag library, including a set of tags 
implementing the embedded help system.  Finally, I worked with Gabe to 
engineer a partial redesign of the overall UI, specifically writing the 
Grades interface and most of the new navigation bar.

Testing: I wrote and ran JUnit tests for most of the code I added to the 
primitives, and wrote 3 suites covering the browser for the Test Plan.

Documents:  I wrote the Developer's Manual and contributed heavily to the 
User Reference Manual.  In addition, I compiled and created the materials 
necessary to compose a complete version of The Book.  Finally, I wrote a 
lot of Javadoc.

Presentation: I helped finalize the final presentation slides to a minor 
extent.  I also helped plan the demonstration for that presentation and 
seed the database for it.

Debugging: I fixed or helped to fix several major primitive- and
database-level bugs, plus several UI bugs.  These included the infamous
primitive-cache-database bug, which was fixed using reflection, the
problem of comparing a course section's term to the current term, the
problem of associating the members of a group with the course section(s)
that group is enrolled in and the grades that group has received, and the 
problem of storing descriptions longer than 255 characters in the 
database.

 - Joel