From: Michael G. <ga...@ma...> - 2008-06-27 00:52:53
|
On Jun 26, 2008, at 8:40 PM, Davide P. Cervone wrote: >> I see your point. The counter argument is that >> setOrientation.pg is being put in modelCourse and is likely >> to be available on every course on the server. > > I don't see that as a counter argument. I think setOrientation.pl > should be kept with the problems that call it rather than putting > it in the location of general-purpose macros. If you are > duplicating setOrientation in every course, then duplicate > setOrientation.pl as well. If you are really worried, then make a > link to a common area instead. > OK. I've thought some more about it and I agree. I'll put parserOrientation.pl in setOrientation in modelCourse and take it out of pg/macros. >> (It's the one set I build for each new user on our hosted and >> hosted2 servers. I use >> it instead of set 0. ) > > We use it that way here, as well. As I recall, there may be some > Union-specific information in the last problem (something about our > Calculus Help Center). I haven't checked to see if you have edited > them or not. > I believe I did but I'll double check. >> There is no space crunch, but duplicating setOrientation.pl >> everywhere seems >> inelegant. > > No more inelegant than duplicating the problem files, eh? > True. >> Another argument (on the other side) is that including it in every >> template directory >> would give them an opportunity to modify macros -- much as they can >> modify the questions in setOrientation. > > Certainly true. > > Davide > Take care, Mike |