[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 62738] Make sure the students cannot access the editor to see
From: Klas Kalass <klas.kalass () gmx ! de>
Date: 2003-08-15 23:20:45
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=62738
------- Additional Comments From klas.kalass@gmx.de 2003-08-16 01:20 -------
Subject: Re: New: Make sure the students cannot access the editor to see the answers of a test
Am Freitag, 15. August 2003 23:56 schrieb Anne-Marie Mahfouf:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=62738
> Summary: Make sure the students cannot access the editor to see
> the answers of a test
> Product: keduca
> Version: unspecified
> Platform: unspecified
> OS/Version: Linux
> Status: NEW
> Severity: wishlist
> Priority: NOR
> Component: general
> AssignedTo: klas@kde.org
> ReportedBy: annma@kde.org
>
>
> Version: 1.2.0 (using KDE 3.1.9)
> Compiler: gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
> OS: Linux (i686) release 2.4.21-0.13mdk
>
> If I make a test for my students, they could always open it with the Keduca
> editor and see the answers. It would be nice better if you had a format for
> the editor and then another for the test app itself. With the server "is
> it"/"will it be" possible to do stuff like students connecting to my
> central server, fill in their names, and then I get their scores in the
> end?
Do you refer to the "gallery" feature here? That feature is not a server and
will not prevent a smart kid from gaining access to the actual answers.
Making keduca client/server is probably the way to go, but that is a very long
way. Making a slightly different format would not buy you much: if your
students are at least a little bit smart, then they will soon figure out how
to open the test in a text editor...
The only way to protect abuse would be to not transfer the answers to the
client computer. An alternative could be to encrypt the files, but again: The
source code is open and there is nothing to prevent a pupil from hacking
keduca so it can save the file in plain text.
So I reccon we really have to go the client/server way here. I am actually not
so fond of that idea, because that would lift keduca from a KDE project to a
web project with a KDE editor frontend, I fear. And I don't think it is
appropriate for a KDE edu app to have its main functionality in a (java?)
webapp or even webservice.
>
> I hope this does not sound too confusing, this is from a user and I want to
> make sure his request is noted.
>
> The concern is explained in the title. If this is already implanted, maybe
> the doc could be updated and all that explained. Thanks a lot for the good
> work.
I would be happy if you like to discuss this in private mail, and maybe can
send me a list of "requirements".
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic