|
From: Ken M. <mo...@pt...> - 2003-08-20 08:58:25
|
These aren't really MAJOR CHANGES (as described in the "Developer's
Etiquette" document), but I have a general question about protocol that I
want to ask before committing these changes, so I am listing them below in
case someone wants to comment.
I have been in the habit of commenting my changes by surrouning new lines
with
# KM
:
# END KM
and commenting out existing lines with
# DIST (existing line goes here)
This turns out to be VERY useful to me because I can easily find the lines
that I have changed and can easily revert back to what used to be there when
things don't work as planned. I noticed also that Greg and Gustav have done
similar things in the past, and that has also been helpful in my opionion
since it is more convenient than using diff to compare two revisions of the
file. Clearly we want to eventually remove such commenting before the code
goes into the main AIM distribution, but my question is whether or not we
should commit changes to the develop_2_1 version with such comment lines or
not.
Personally, I think we should commit such lines except in cases where the
comments would get out of hand, like when searching and replacing something
globally in all files, for example. Then when the develop_2_1 version is
ready to be released, we could just grep out all of the extra comment lines.
The alternative would be for everyone to eliminate any such comment lines
before committing the changes so that no such comments appear in the
develop_2_1 code. How do the rest of you feel about this?
Anyway, here are the changes I've made that I propose to commit:
Aug 19, 2003
------------
PROPOSAL
I propose to commit the following changes
* Globally rename Latex to aim/LaTeX as described in previous postings by
Greg Gamble and myself to accomodate Maple 9 (affects 15 files)
* Minor tweak to `Class/Typefunction` to fix a problem that occurs in Maple
9
* Several changes to Aim.mpl, Util.mpl, aim/Question.mpl and aim/Quiz.mpl to
do the following:
+ Fixed the Mark Summary table so it uses the correct links when the quiz
is focused
+ Removed the focus option from the question toolbars when the Trying a
quiz in aim/Question.mpl (since there is already a "Try Separately" link)
+ Fixed a minor formatting bug in aim/Question.mpl
+ Changed the background color for the teacher's answer and solutions to
make it easier to quickly distinguish between viewing solutions and working
on an active quiz while focusing and unfocusing and reloading quizzes (see
below)
+ Added the aim/HTMLColoredPage method to aim/Util.mpl to allow us to set
the background color for the entire html page. Initially I was going to use
this to distinguish solutions pages from active quiz pages, but it was
overkill. :) Thus this function currently is not used for anything, but I
left it in there in case we decide to add such options in the future.
+ Changed the behavior of AIM with regard to showing solutions as follows:
The only way for a student to get a new version of a quiz is if he (a)
is attempting the quiz for the first time or (b) requests a new version by
clicking on the New Version link.
In particular, if the student elects to show solutions to a quiz, he
will continue to see the solutions to the quiz he just completed no matter
what he does until he clicks New Version. This allows a student, for
example, to view solutions on one machine, then switch to a different
machine to print them out (or view some of the solutions, then go for lunch,
and then return and read the rest of them).
When viewing solutions, the focus option now focuses on the given
question and shows its solution instead of generating a new quiz and
focusing on that newly generated question. This allows a student to print
the solution to just one question instead of printing the solutions to the
entire quiz.
-----------------------------------------
Ken Monks - Professor of Mathematics
University of Scranton
Scranton, PA 18510
email: mailto:mo...@sc...
web: http://www.scranton.edu/~monks
-----------------------------------------
|
