From: Peter C. <Pet...@me...> - 2006-06-13 11:23:57
|
> From: Matthew Buckett > QuestionnaireFacility did move from=20 > org.bodington.servlet.facilities to=20 > o.b.assessment and that is why 1.1 is so late on. Ah, OK. That explains that. Why, out of interest, when there are no other facilities in there? - Peter |
From: Peter C. <Pet...@me...> - 2006-06-13 11:45:03
|
> From: Alexis O'Connor > For reasons=20 > I forget I now, it was driving me nuts having to split up the work on=20 > the questionnaire between its facility and other classes between=20 > different directories, so I moved it to be with all the other=20 > questionnaire classes. OK, so for unclear reasons we've lost the revision history of QuestionnaireFacility.java. Folks, if we're going to do this, can we please do it via SF's documented facility for *moving* RCS files, and can we mail round the list beforehand in case anyone has uncommitte changes to the old version of the file? I accept that it requires human contact, but at least it preserves revision information. - Peter |
From: Colin T. <col...@ou...> - 2006-06-13 11:54:31
|
Peter Crowther wrote: > Folks, if we're going to do this, can we please do it via SF's > documented facility for *moving* RCS files, and can we mail round the > list beforehand in case anyone has uncommitte changes to the old version > of the file? I would expect that to show up when you did an update (before committing)? -- ____________________________________ Colin Tatham VLE Team Oxford University Computing Services http://www.oucs.ox.ac.uk/ltg/vle/ http://bodington.org |
From: Matthew B. <mat...@ou...> - 2006-06-13 11:58:36
|
Peter Crowther wrote: >> From: Alexis O'Connor >> For reasons >> I forget I now, it was driving me nuts having to split up the work on >> the questionnaire between its facility and other classes between >> different directories, so I moved it to be with all the other >> questionnaire classes. > > OK, so for unclear reasons we've lost the revision history of > QuestionnaireFacility.java. Technically we haven't lost it, just that it is attached to a file that is now deleted. If nothing else having a commit comment saying that the file moved from another package helps. > Folks, if we're going to do this, can we please do it via SF's > documented facility for *moving* RCS files, and can we mail round the > list beforehand in case anyone has uncommitte changes to the old version > of the file? I accept that it requires human contact, but at least it > preserves revision information. http://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1#limitations I'm not sure how you missed a file moving? The problem with moving the file and its history in CVS is that although you get the history, checking out versions before the move mean they no longer work. -- -- Matthew Buckett, VLE Developer -- Learning Technologies Group, Oxford University Computing Services -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/ |
From: Alexis O'C. <ale...@ou...> - 2006-06-13 11:38:45
|
Peter Crowther wrote: >> From: Matthew Buckett >> QuestionnaireFacility did move from >> org.bodington.servlet.facilities to >> o.b.assessment and that is why 1.1 is so late on. > > Ah, OK. That explains that. > > Why, out of interest, when there are no other facilities in there? > > - Peter > (Adam gave me strict instructions to ignore this list, but I guess on this occasion he'll let me off ;-) ). I have to confess to introducing yet another tool packaging style :-(. The "purest" style is that adopted by the logbook and announcements, where each tool goes in it's own package with it's own corresponding facility. Many facilities go in org.bodington.servlet.facilities (which is where the questionnaire one was too). A lot of the classes to do with assessment tools go in the org.bodington.assessment package. For reasons I forget I now, it was driving me nuts having to split up the work on the questionnaire between its facility and other classes between different directories, so I moved it to be with all the other questionnaire classes. At the time it struck me as a half-way house between being in a common directory (least desirable) to being in it's own package (most desirable). Presumably, the long-term solution would be for each assessment tool (short-answer paper, MCQ, peer assessment, etc) to be in it's own package a la logbooks / announcments (?). Alexis |