|Convincing IT services||topic started 6/1/2004; 9:28:21 PM
last post 6/4/2004; 1:52:06 PM
|Dennis Keeler - Re: Convincing IT services
6/4/2004; 1:52:06 PM (reads: 1243, responses: 0)
|Thanks for the very useful feedback. IT Services has asked that I
evaluate both MapleTA and Webwork2 for awhile this summer. (MapleTA has
been upgraded since I used it in the Fall, so maybe I'll like it better
than I did.) If we go with Webwork, we'll definitely go straight to
version 2, as both IT Services and I were impressed with the new
interface. And I definitely like the ability to avoid Java (see below);
that's a big advantage of Webwork2 over MapleTA in my view.|
As you requested, Mike, I've attempted to test various the Webwork 1.9 previewer with various Mac OS X browsers. FYI, my system has gone through all updates, so I'm at Mac OS 10.3.4 and Java 1.4.2. For consistency, I used
<http://webwork.math.rochester.edu/SampleCourse/>;, Set 0, Question 2, typing 2*cos(t)^2 in the second blank. After rebooting, I found:
Firefox 0.8 (Mozilla variant) - no problem
Camino 0.8b (Mozilla variant) - no problem
Safari 1.2.2 - worked fine, though output was in a different font, thinner and more pixellated; also Ans 1, Ans 2 were written with the number under Ans
Mozilla 1.6 - the previewer left a blank area for *cos . So the output looked like
2 (t)2 (superscript 2). Pressing Preview Again got the right output.
For the next test, I had to quit Mozilla 1.6, since Netscape 7.1 won't run at the same time.
Netscape 7.1 - same behavior as Mozilla 1.6
Internet Explorer 5.2.3 - on the first try, I got 2 (t)2(superscript 2). Hitting Preview Again, I got a blank white rectangle. By typing something for Ans 1 (specifically 3^2) and hitting Preview Again, the correct output came to both rectangles.
I quit Netscape, restarted Mozilla. The previewer then gave a rectangle with "Loading Java Applet..." in the middle, and hitting Preview Again did not remedy the situation.
I've rebooted since, and I've had the 2 (t)2 problem with Firefox 0.8 also. It seems that as the Java applet gets used multiple times, under multiple browsers, it starts to malfunction.
Thanks again for the help. -Dennis