Menu
▾
▴
onebook-core — Day to day design and development traffic
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(59) |
Oct
(198) |
Nov
(142) |
Dec
(102) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(64) |
Feb
(174) |
Mar
(204) |
Apr
(127) |
May
(65) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Gabe J. <joh...@cs...> - 2002-08-26 01:20:47
|
Hey teem. I just finished putting some bandaids on OneBook in preparation for Dan to begin using it tomorrow. He's going to be teaching 2 classes with it this semester, with about 140 students banging on it. Drink something and toast to good luck. -gabe |
|
From: Andrew S. <And...@Co...> - 2002-05-25 18:03:16
|
Eric just brought to my attention the fact that I did not formally collect money for the book. It cost $12 per person, and Joel is the only one who paid. Eric suggested that I give you all my address so you can send checks. :-) Andrew Strotheide 980B Milo Cir Lafayette, CO 80026-8806 See everyone around! Andrew P.S. - How's the job search for everyone? |
|
From: <sa...@yq...> - 2002-05-10 23:57:21
|
You're done! Congratulations! bruce |
|
From: <sa...@yq...> - 2002-05-10 23:56:22
|
We turned in the final release to Dan--Dan, can you ping Bruce
and tell him we're not lying?
Not necessary ... just needed someone to tell me you did it.
thanks
bruce
|
|
From: Gabe J. <joh...@cs...> - 2002-05-10 23:53:36
|
sa...@yq... wrote: > final release to sponsor -- let me know when you've done this (due May 7) We turned in the final release to Dan--Dan, can you ping Bruce and tell him we're not lying? > contact info - johnson minick (due May 9) I will remain joh...@cs... for the forseeable future. -gabe |
|
From: <sa...@yq...> - 2002-05-10 04:57:42
|
I think there may be a slight problem with the Sponsor Final release. As
far as I know, it is sitting in Dan's mailbox. Gabe said he thought Dan
might have had to leave again for a family emergency. The Book and our
final release CD were both put into Dan's mailbox. If anyone knows more
information about this, or if i've gotten thing horribly mixed up, feel
free to speak up.
I just needed to know that you've provided it to him.
thanks
bruce
|
|
From: LUNSFORD J. L. <Jam...@Co...> - 2002-05-10 04:45:00
|
I think there may be a slight problem with the Sponsor Final release. As far as I know, it is sitting in Dan's mailbox. Gabe said he thought Dan might have had to leave again for a family emergency. The Book and our final release CD were both put into Dan's mailbox. If anyone knows more information about this, or if i've gotten thing horribly mixed up, feel free to speak up. Jamie On Thu, 9 May 2002 sa...@yq... wrote: > > Since I will have to complete final grades this weekend, > I will need these items by Saturday 8am if you would like > to get credit for any of them. > > final release to sponsor -- let me know when you've done this (due May 7) > peer evaluation - minick (due May 9) > contact info - johnson minick (due May 9) > > bruce > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > onebook-core mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onebook-core > |
|
From: <sa...@yq...> - 2002-05-10 02:53:36
|
Since I will have to complete final grades this weekend,
I will need these items by Saturday 8am if you would like
to get credit for any of them.
final release to sponsor -- let me know when you've done this (due May 7)
peer evaluation - minick (due May 9)
contact info - johnson minick (due May 9)
bruce
|
|
From: Gabe J. <joh...@cs...> - 2002-05-10 01:22:53
|
joel dice wrote: > Just a quick update - Andrew and I met with Bruce this afternoon, had him > sign both copies of The Book (it looks great), and left one with Bruce and > one in Dan's mailbox. Did Dan get his CD? i think dan went back to chicago--a family member is very sick or something... -gabe |
|
From: <Eri...@Co...> - 2002-05-09 21:51:30
|
Bruce, Here are our contribution summaries. For more detail about volume of code changes and when they happened, check out ucsub.colorado.edu/~minick/onebook/whoDidWhat.html which, I believe, is endorsed as not blatantly wrong by the group. Those numbers are meant as a compliment to our summaries and peer reviews and don't mean a whole lot on their own. Andrew's Contribution Summary: 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. Joel Dice's Contribution Summary Code: Most of the code I wrote was for the Browser. This includes code added 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. Gabe's Contribution Summary: I played the role of code-monkey early on and was responsible for enough things that I don't really remember what all I worked on. From memory, a list includes: * Primitive tree debugging: I wrote a lot of JUnit code and didn't stop debugging until that bar was green. * File transfer: doing file I/O with HTTP is a bear, but I did find some tools out there (from O'Reilly at servlets.com) for uploading files. File download was a more esoteric problem to solve because our files are not just being sent over from the file system; they are all protected with ACLs and must be written to the output stream by custom code. * Statistics interface: The hard part about the statistics interface was the dynamically generated GIF that formed the most useful part of this page. Once our (very badly written) grading scheme was set, I used this to generate statistics. The UI for this page is pretty good. * UI redesign & implementation (with Joel): Joel and I redid the navigation and made the interface somewhat more coherent. This involved rewriting some of the primary pages. I think I did assignments, announcements, and handouts. In general, I handled most of the freaky weird problems (like dynamically generating a GIF or creating servlets for file transfer) and let the general programming up to the others. I also started and finished the user reference manual (with lots of Joel in the middle). Jamie Lunsford's Contribution Summary Code: I only did some code this semester. The major things I wrote were the Excel Dump of grades, Edit Class, Grading Plan, the current grade, and the original course list. Most of these I contributed the original code, and it was modified slightly later. Testing: I wrote tests for and tested about 8 of the final 20 or so test suites. I also submitted about 10 bugs that I found through doing these tests. Documents: I was in charge of the Pre-Beta Code Review. I looked through all the files to determine which needed more commenting and sent out information about which files still needed work. I also commented about a third to a half of the files myself. I printed up the code and bound it. I was also in charge of the User Tutorial, which I wrote completely, along with all the changes. I took all the screenshots shown in the tutorial, along with a bunch of others that probably never got used. And I wrote 8 of the test suites. Presentations: I helped finalize the slides for the final presentation. I also helped with the demo planning and helped seed the demo database. I also drew the pretty modular decomposition picture on the whiteboard. Debugging: I submitted and/or fixed a large number of UI bugs. Most of them were just little things that weren't the way they were supposed to be, but I did fix a couple of bugs that took you to the Apache error instead of our error page. Eric Minick's contribution summary Code: I wrote a bunch of code this semester, though not as much as some. My main contributions were the Calendar; the PortalBean which backended the Portal, Section Portal, Calendar, Assignment List, Handout List and Announcement List pages; and bringing a consistent format to the above pages. I did a lot of the original work on a couple of those pages as well. Testing: I was the test boss, and did some work to organize the test effort. Early in the semester I brought JUnit regression testing into the game, which helped early but wasn't very significant once the back-end solidified. I also organized the Test Plan, wrote the introductory sections and farmed out tasks to the rest of the team to write tests and execute them. I also did my share of that work. Documents: I had a lead role in the Test Plan, but otherwise only chipped in here and there in the docs. Presentations: For the final presentation, I churned out the first draft of the slides with a little help. I helped out with the demo planning as well. Debugging: I fixed my share of bugs, but I don't think any were spectacular. I also managed our bug list, prodded people to fix bugs and assigned bugs that weren't owned. |
|
From: joel d. <di...@co...> - 2002-05-09 21:44:16
|
Just a quick update - Andrew and I met with Bruce this afternoon, had him sign both copies of The Book (it looks great), and left one with Bruce and one in Dan's mailbox. Did Dan get his CD? - Joel |
|
From: Andrew S. <And...@Co...> - 2002-05-09 21:42:10
|
The books are out of our hands. Bruce signed them today at 2:30 and we left one with him and put the other in Dan's mailbox. Andrew |
|
From: <Eri...@Co...> - 2002-05-09 21:30:18
|
I agree that the numbers are not the whole story. I just didn't want to be responsible for saying what the whole story was. I hope that with the graphs and tables, our contribution summaries and peer reviews will have better context. In other words, we each describe our own numbers as part of our contribution summary and if we want to say, "Joel was constantly doing work." we can look at the graph and see he doesn't touch 0, and point that out that at least every 3 days or so, he dropped in a little code. I think my description of the graphs is fairly conservative and says they don't show the whole picture. If there's any other general stuff, you'd like me say, let me know. |
|
From: Andrew S. <And...@Co...> - 2002-05-09 18:56:49
|
I think it'd actually be pretty cool to put a short statement in abut what the statistics gleaned from sourceforge are really good for. For example, though midway through the semester it shows me as having 10000 lines of code added, that isn't accurate, because although 1/3 was javadoc and stuff, about 2/3 of that was header code. So my graph is skewed funny because of the weight of that one week, so contributions of a few hundred lines get easily lost in the bottom of the graph. I'm just thinking it may be helpful to point out issues like this when you link to the statistics, so it seems they're more adequately introduced. I think we're all in agreement that they're definitely useful, if understood in the correct context. Andrew |
|
From: Andrew S. <And...@Co...> - 2002-05-09 18:52:55
|
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. |
|
From: <Eri...@Co...> - 2002-05-09 17:47:36
|
I'm only missing Andrews, here's what I want to turn in (hopefully with his added). Anyway, I'm stating that you guys are endorsing the numbers and graphs I gathered, so please take a look. Here are our contribution summaries. For more detail about volume of code changes and when they happened, check out ucsub.colorado.edu/~minick/onebook/whoDidWhat.html which, I believe, is endorsed as not blatantly wrong by the group. Joel Dice's Contribution Summary 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 hirarchies. 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. Gabe's Contribution Summary: I played the role of code-monkey early on and was responsible for enough things that I don't really remember what all I worked on. From memory, a list includes: * Primitive tree debugging: I wrote a lot of JUnit code and didn't stop debugging until that bar was green. * File transfer: doing file I/O with HTTP is a bear, but I did find some tools out there (from O'Reilly at servlets.com) for uploading files. File download was a more esoteric problem to solve because our files are not just being sent over from the file system; they are all protected with ACLs and must be written to the output stream by custom code. * Statistics interface: The hard part about the statistics interface was the dynamically generated GIF that formed the most useful part of this page. Once our (very badly written) grading scheme was set, I used this to generate statistics. The UI for this page is pretty good. * UI redesign & implementation (with Joel): Joel and I redid the navigation and made the interface somewhat more coherent. This involved rewriting some of the primary pages. I think I did assignments, announcements, and handouts. In general, I handled most of the freaky weird problems (like dynamically generating a GIF or creating servlets for file transfer) and let the general programming up to the others. I also started and finished the user reference manual (with lots of Joel in the middle). Jamie Lunsford's Contribution Summary Code: I only did some code this semster. The major things I wrote were the Excel Dump of grades, Edit Class, Grading Plan, the current grade, and the original course list. Most of these I contributed the original code, and it was modified slightly later. Testing: I wrote tests for and tested about 8 of the final 20 or so test suites. I also submitted about 10 bugs that I found through doing these tests. Documents: I was in charge of the Pre-Beta Code Review. I looked through all the files to determine which needed more commenting and sent out information about which files still needed work. I also commented about a third to a half of the files myself. I printed up the code and bound it. I was also in charge of the User Tutorial, which I wrote completely, along with all the changes. I took all the screenshots shown in the tutorial, along with a bunch of others that probably never got used. And I wrote 8 of the test suites. Presentations: I helped finalize the slides for the final presenation. I also helped with the demo planning and helped seed the demo database. I also drew the pretty modular decomposition picture on the whiteboard. Debugging: I submitted and/or fixed a large number of UI bugs. Most of them were just little things that weren't the way they were supposed to be, but I did fix a couple of bugs that took you to the Apache error instead of our error page. Eric Minick's contribution summary Code: I wrote a bunch of code this semester, though not as much as some. My main contributions were the Calendar; the PortalBean which backended the Portal, Section Portal, Calendar, Assignment List, Handout List and Announcement List pages; and bringing a consistent format to the above pages. I did a lot of the orginal work on a couple of those pages as well. Testing: I was the test boss, and did some work to organize the test effort. Early in the semester I brought JUnit regression testing into the game, which helped early but wasn't very significant once the back-end solidified. I also organized the Test Plan, wrote the introductory sections and farmed out tasks to the rest of the team to write tests and execute them. I also did my share of that work. Documents: I had a lead role in the Test Plan, but otherwise only chipped in here and there in the docs. Presentations: For the final presentation, I churned out the first draft of the slides with a little help. I helped out with the demo planning as well. Debugging: I fixed my share of bugs, but I don't think any were spectacular. I also managed our bug list, proded people to fix bugs and assigned bugs that weren't owned. |
|
From: <sa...@yq...> - 2002-05-09 05:11:16
|
- One "it's" that should have been an "its", but otherwise a very nice
reference! Good job!
|
|
From: Andrew S. <And...@co...> - 2002-05-08 21:39:16
|
Joel, I stopped by today to drop it off, but he wasn't there. I can try again tomorrow at 2. Wanna meet on the 5th floor near his office? Andrew On Wed, 8 May 2002, joel dice wrote: > Andrew, when are you planning to take the copies of The Book to Bruce, if > you haven't done that already? I'd like to be there too, if possible, to > see how it turned out and to pay my share of the cost. He has office > hours tomorrow from 2:00 to 4:00 - would 2:00 work for you? Anyone else > interested in being there? > > - Joel > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > onebook-core mailing list > one...@li... > https://lists.sourceforge.net/lists/listinfo/onebook-core > |
|
From: joel d. <di...@co...> - 2002-05-08 20:02:35
|
Andrew, when are you planning to take the copies of The Book to Bruce, if you haven't done that already? I'd like to be there too, if possible, to see how it turned out and to pay my share of the cost. He has office hours tomorrow from 2:00 to 4:00 - would 2:00 work for you? Anyone else interested in being there? - Joel |
|
From: joel d. <di...@co...> - 2002-05-08 19:08:50
|
On Wed, 8 May 2002, Gabe Johnson wrote: > I have the CD in my hand. Joel, I noticed in the book zipfile > there were all sorts of blahBlah~ files that didn't seem to serve > a purpose so I deleted them. I put Java, MySQL, Tomcat, the two > jar files (oreilly and mm), and WinCVS on the CD as well. I'm > going to go bring it to Dan right now and then he can email bruce > & tell him he got it. Thanks. The blahBlah~ files are due to my previously poor understanding of the a2ps and zip utilities. When a piece of source code changed and I regenerated the *.ps files using a2ps, I thought it would just overwrite the previous versions, but it made backups of the old versions (ex. grades.jsp.ps~). So after I blindly zipped everything up and Andrew pointed out all the backups cluttering things up, I went back and deleted them and ran "zip -r book.zip book/", thinking zip would overwrite the old book.zip. Of course, I was wrong again - it just *updated* book.zip, leaving the backups in there. So they were still there when you grabbed it. Anyway, a version without the backups is available in the usual place, not that it matters now. - Joel |
|
From: Gabe J. <joh...@cs...> - 2002-05-08 18:47:37
|
I have the CD in my hand. Joel, I noticed in the book zipfile there were all sorts of blahBlah~ files that didn't seem to serve a purpose so I deleted them. I put Java, MySQL, Tomcat, the two jar files (oreilly and mm), and WinCVS on the CD as well. I'm going to go bring it to Dan right now and then he can email bruce & tell him he got it. -gabe |
|
From: joel d. <di...@co...> - 2002-05-08 18:45:23
|
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 |
|
From: Gabe J. <joh...@cs...> - 2002-05-08 15:33:35
|
Eri...@Co... wrote: > Sounds great guys! Let me know how much I owe you. Also, contribution > summaries would be a good thing. Gabe's Contribution Summary: I played the role of code-monkey early on and was responsible for enough things that I don't really remember what all I worked on. From memory, a list includes: * Primitive tree debugging: I wrote a lot of JUnit code and didn't stop debugging until that bar was green. * File transfer: doing file I/O with HTTP is a bear, but I did find some tools out there (from O'Reilly at servlets.com) for uploading files. File download was a more esoteric problem to solve because our files are not just being sent over from the file system; they are all protected with ACLs and must be written to the output stream by custom code. * Statistics interface: The hard part about the statistics interface was the dynamically generated GIF that formed the most useful part of this page. Once our (very badly written) grading scheme was set, I used this to generate statistics. The UI for this page is pretty good. * UI redesign & implementation (with Joel): Joel and I redid the navigation and made the interface somewhat more coherent. This involved rewriting some of the primary pages. I think I did assignments, announcements, and handouts. In general, I handled most of the freaky weird problems (like dynamically generating a GIF or creating servlets for file transfer) and let the general programming up to the others. I also started and finished the user reference manual (with lots of Joel in the middle). -gabe ps CD is on the way |
|
From: <Eri...@Co...> - 2002-05-08 07:44:27
|
Sounds great guys! Let me know how much I owe you. Also, contribution summaries would be a good thing. eric |
|
From: joel d. <di...@co...> - 2002-05-08 06:14:24
|
On Tue, 7 May 2002, Andrew Strotheide wrote: > > The book is finished. We even have Dan's signature on both copies. > Is he supposed to hold on to his copy or not? I wasn't really sure > cause I thought he might want it with Bruce's signature after Thursday > too, so I still have it and will give it back to him after Bruce signs > off. > Great job, Andrew. From the "The Book" assignment: "You should produce a copy for your project manager and a copy for your sponsor, as well as any other copies you want. You should have all copies signed by your sponsor and then turned in to your project manager by the deadline. If complete and correct, your project manager will sign all copies, keep one of them, and return a copy for you to deliver to your sponsor, along with any other copies you might have produced." So we need to have Bruce sign both copies by Thursday @4:00 PM. - Joel |
3 messages has been excluded from this view by a project administrator.
