On Mon, Oct 25, 2010 at 2:23 PM, Giancarlo Razzolini <grazzol...@gmail.com> wrote: > James, > First of all thank you for the fast response. I'll take a look into the > admin forms widgets. I'm already looking for third party applications field > types and widgets to see if I find one that does what I want. I was even > considering creating views on the underlying database to accomplish this. I > think that django should implement on the forms a better way to show granular > output. My django application is completely user dependent, and only let a > user to view/add/edit/remove information that belongs to him. Only the > superuser can deal with all objects. I was using a custom for to accomplish > that, but since I'm using a ManyToMany relation, it was a lot of work to > validate it myself and save the relationship. I guess I'll have to turn back > to it if I can't use the admin form you mentioned. Thank you again. > My regards, > Giancarlo Razzolini
No problem. For anything user-facing, I'd recommend not using admin forms. You might be able to get away with it, but it seems each time you add some business logic (permissions, validation, etc) it makes it less and less a fit with the built-in forms. It's relatively trivial to create your own forms, so it shouldn't be too hard to ignore the admin pages. It's just annoying to have to do the work to create templates, logins, etc. But depending on your requirements, you'll probably find that it's easier to just create your own forms. You'll still have to figure out the widget issue, but at least you'll have better control over the validation. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
