Kenneth McDonald wrote: > I have a list of records, and I'd like the user to be able to delete > any given record by pressing a button. My current strategy is to have > each record in its own form (so that pressing the submit button for > that form would delete the record), and have each form contain a > hidden field identifying the corresponding record via a unique key so > that I know which record to delete. However, this is very crude, and > no doubt indicative of the fact that I'm still just starting to learn > Django. What would people suggest as better alternatives? Feel free to > point me to documentation--I don't mind doing the reading, it's just > finding the relevant material that's a problem (there's so much of > it :-) ).
I don't think that's bad, all depends on how you want UI to work. Other options would be putting them in a ChoiceField and using Select (dropdown) RadioSelect (radio buttons) or some custom widget. The choice field options will have only one delete button but require user to select which record to delete. That may or may not be a better ui than multiple delete buttons. -- Norman J. Harman Jr. Senior Web Specialist, Austin American-Statesman ___________________________________________________________________________ You've got fun! Check out Austin360.com for all the entertainment info you need to live it up in the big city! --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
