[LON-CAPA-users] disabling PRT
rlight
lon-capa-users@mail.lon-capa.org
Fri, 10 Sep 2004 09:42:00 -0400
As I read Ray's question, he just doesn't want students to try printing when
the PRT doesn't work properly, not necessarily trying to print via screen
capture.
When I had a problem with a couple of problems that didn't print, I just put
a warning (I forget where, but I think in the title of the problem) that it
didn't print properly and not to try. One could do that with a whole
problem set.
However, I agree with Ray, having the option in PARM to turn off PRT would
be preferable.
Robley
*************************************************************
Robley J. Light Professor Emeritus, Chemistry and
Biochemistry
Department of Chemistry Phone: (850) 644-3844
and Biochemistry Email: rlight@chem.fsu.edu
Florida State University Fax: (850) 644-8281
Tallahassee, FL 32306-4390 Home Page:
http://chemweb.chem.fsu.edu/editors/rlight
> -----Original Message-----
> From: lon-capa-users-admin@mail.lon-capa.org
> [mailto:lon-capa-users-admin@mail.lon-capa.org] On Behalf Of
> Todd Ruskell
> Sent: Thursday, September 09, 2004 7:00 PM
> To: lon-capa-users@mail.lon-capa.org
> Subject: Re: [LON-CAPA-users] disabling PRT
>
> Ray,
>
> On Thu, 2004-09-09 at 15:52, Ray Batchelor wrote:
> > Hi Todd,
> > The endgame is this:
> >
> > Running online quizzes; only one try each question;
> But here students could still use the browser print function
> or do a screen capture.
>
> > for some problems there
> > are always issues with the PRT and therefore I just don't
> want to be
> > bothered with it (for example problems with multiple
> in-line textline
> > boxes inside a table and with images). In this particular
> instance we
> > are already discouraging the students from printing.
> Hiding the PRT
> > option would simplfy this and make problem creation less
> tedious. A
> > possible practical solution is to hard code in a "No PRT"
> argument to
> > the <problem>? The reason I say this is because if they really are
> > unprintable then we don't really want anyone printing them.
>
> I can certainly see this argument. Apparently I haven't
> created fancy-enough problems :/.
>
> > The question is: "Should all resources be functional wrt to
> PRT? or is
> > there a category of resources which could be intended as web-only."
> > Which makes me realize that I could have coded everything inside
> > <web> </web>tags, but it was not obvious to me at the time
> that this
> > is what I would always want (nor is it now).
> >
> > On the other hand allowing people to switch off PRT from
> within PARM
> > would allow all users to decide whether they want PRT available in
> > their course resources.
> >
> > Comments?
> Given your arguments, I'd go with author control, so each cc
> wouldn't have to determine whether or not a resource would
> blow up when printed.
> Can resources like movies be PRTed? What happens? I've never tried.
>
> But being of two minds, I would argue that a truly compliant
> resource would be both web and print compatible. Just how
> compatible, I'm not sure. ie: In print mode a simple
> message "Cool video clip here" or some such would, I suppose,
> technically be compatible.
>
> Or maybe a compromise. Stuff that looks "printable", ie:
> problems, web pages, graphics, really should be print
> compatible, while other resources, like movies, shouldn't.
>
> I'll stop rambling now.
>
> Todd
>
>
> --
> Dr. Todd Ruskell
> Lecturer, Department of Physics Office: Meyer Hall 326
> Colorado School of Mines Phone: 303-384-2080
> 1523 Illinois Street Fax: 303-273-3919
> Golden, CO 80401
>
> _______________________________________________
> LON-CAPA-users mailing list
> LON-CAPA-users@mail.lon-capa.org
> http://mail.lon-capa.org/mailman/listinfo/lon-capa-users
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.755 / Virus Database: 505 - Release Date: 9/8/2004
>
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.755 / Virus Database: 505 - Release Date: 9/8/2004