[onebook-core] My summary

[Andrew S. <And...@Co...>]

Same deal as with everybody else... if this looks wrong, feel free to
speak up!  :)


Standard Code:  
My contribution to the code base was not as significant as those of some
other members, but major pieces I added include:
   * System-wide date representation, conversion, integration, and
storage
   * Complete groups functionality
   * ACLs

JavaScript:
Probably the biggest-bang-per-line contributions, code wise, were the
JavaScript functions I built to enhance the interface.  The list of what
I can remember is as follows:
   * Implementation of selection and tabbing functions throughout
   * Select all/none code
   * Slick interface for passing onLoad() functions into the JSP
template
   * Window focus and tabbing correction
   * text field/text input length control
   * Date passing from calendar

Validation and Formatting:
During the iterative process of source-code approval, I spent a very
significant amount of time formatting source code, updating JavaDoc, and
validating HTML output.  Source code modifications include adding the
team header to every file in the project, formatting everything to fit
within 80 columns, standardizing the layout of HTML and Java files so
they met certain code conventions, and standardizing variable naming use
in files.  During the same process, I also individually checked every
line of JavaDoc in each of the Java files of OneBook to make sure all
was correct.  If documentation was missing, I added it.  If it was
mismatched or out of date, I rewrote or corrected it.  In terms of code
validation, though it was not a formal process, I used the W3C's code
validation engine to check much of OneBook's code for compliance.  Our
goal was HTML 4.01 Transitional support, so I used that template with
their program to check the output generated by the JSP engine.  I found
and fixed many overlapping tags, mismatched begin/end tags, and other
problems of that sort.  

Testing/Help/Documentation:
I was responsible for the help, test suites, and final testing of the
Grading, Calendar, Portal, Groups, and Course Home Page interfaces.
This work included writing test cases and results for each of the
pieces, and creating all of the online help text for each section.

Debugging:
One of my favorite activities was to pick up an active bug from our
bug-list on Sourceforge and find a way to fix it.  Bugs I fixed include:
   * Select all/None in grading interface
   * Tab-order/Tab-Selection in grading interface
   * ACL functions in group interface
   * Name multiplicity in groups and users
   * JavaScript quirks in the calendar
   * Date display and processing across the project
   * The infamous Assignment sans file creation bug
   * Login field setFocus for sign-on
   * processInfoHandout, processCourseSection page URL redirection
   * Group creation intricacies

Presentation:
I contributed to the grammatical and formatting accuracy of the final
presentation, and also calibrated the projector and computer to display
the UI's colors correctly in the L3D so we could actually read the
on-screen text.

The Book:
I helped the team to round up the most up-to-date copies of documents
for the book, and was eventually the person who took it from a ZIP-file
of a2ps-formatted code segments and Word documents (thanks, Joel!), to a
printed, finalized form.  Preparing the book at that level also included
correcting formatting and layout errors for all of the documents, and
unifying the presentation of each one.