Even easier than I thought, apparently.
Who am I to suggest that perhaps my answers need to be reset?
(We will farewell the FlyingFish system at the end of semester with great sadness - well, not really, but the new WebCT system is sure to be almost as bad.)
2 comments
dinusha :: Sunday, March 12th
hey dude, saw this when i was stalking Sheeba's flist. Be careful with this. The nasty little faculty has gone and changed the scenarios on one of the long answer questions, even though your old answer is still the same.
Jason Stirk :: Monday, March 13th
But WebCT is such a wonderful and robust system, just chock full of insights into usability, stability and good ol' aesthetics! I don't understand how you can say such negative things about it!?! :boggle:
Yeah, who the hell am I trying to kid. Good luck's all I can say.
Re: FlyingFish, the manual linked from the Wiki is pretty cool - parts of it are more a commentary on system design than a technical guide. Such perls as :
"By now you are probably familiar with UDB files that have no file extension. For historical reasons (because of errors I made early on), the assessor.txt file really is a UDB but it is stored with the .txt suffix. Sorry. Anyway, here is the assessor.txt file for the Statics example:"
and
"This UDB file is also unusual in that it has C++-style comments, i.e. // to start a comment. I must emphasise that comments of this kind are NOT a standard UDB feature. I broke the rules for assessor.txt files because I felt comments were essential to help keep track of all the keys in the file. The file breaks one final UDB convention because the order of lines in the file is somewhat important, as we shall see."
