On 11-Sep-06, at 4:46 AM, Tamara D. Snyder wrote:
> Many of you have lots more experience at this sort of thing than I
> do. What do you think? Should I use the django provided auth system
> with my student database as a backend, or should I create my own
> thing?
create your own - generaly
The system I'm using now has a database table with the students'
names, id numbers, majors, emails, etc. and it is very easy to import
a text file with all that info right into the table. When the
semester is over I just save the grades to another text file and then
clear out the table an
On 11/09/2006, at 9:16 AM, Tamara D. Snyder wrote:
>
> Hi All,
>
> There is a web application I would like to write for a class I teach
> at the university. I would like my students to be able to log in and
> do something ("homework" if you like).
>
> I'd like to reuse the application next seme
On 9/10/06, Tamara D. Snyder <[EMAIL PROTECTED]> wrote:
> I'd like to reuse the application next semester, with a different set
> of students. And I naturally don't want my students to have any
> access at all to the admin site.
The included backend should be sufficient for what you've described
You should just use the Django auth system. It's fairly easy to use and
it provides mechanisms for protecting views that you would have to
duplicate anyway. If the default User object is too skimpy for you, you
can add to it using UserProfiles or just create a table and link to the
User.
BTW, I'm
Hi All,
There is a web application I would like to write for a class I teach
at the university. I would like my students to be able to log in and
do something ("homework" if you like).
I'd like to reuse the application next semester, with a different set
of students. And I naturally don'
6 matches
Mail list logo
