Re: To Use or Not to Use the admin backend

On Tue, 4 Sep 2012 08:14:37 +0300, Frankline <fraogongi@gmail.com>
declaimed the following in gmane.comp.python.django.user:

> An example use case is if I need an admin backend with features for reports
> and graphs, aside from other site configurations.
>
Caveat: I have minimal experience with actual coding of Django
applications (I'd started a book catalog in my spare time at work, back
when Django transitioned from 0.9x to 1.x, but never got past the admin)

To me, the Django "admin" is a brute-force means of maintaining the
database, meant for skilled users... Things like "reports and graphs"
aren't part of the "admin" itself but more restricted applications
available to an "admin"-class user. In my never-finished book catalog,
searching for books, checking books out or in might be regular user
(maybe not even a "logged in" user per se, but open to anyone); but
adding, deleting, editing books, or maintaining a list of "admin" users
would be restricted functions. The base "Admin" interface would be
reserved for correcting errors that happen during development/update of
the regular interface pages.

{You may now throw the tomatoes}
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.