I have been researching few (web) application frameworks and considering our projects, Django outperforms all of them easily, reflecting exactly what we were going to build (well, no need to build now).
After playing around with some test applications I noticed a few things, there wasn't a way to represent a model's field (especially m2m fields) with multiple checkboxes in the administration interface. This was weird because there already was a form field (CheckboxSelectMultipleField) to render them. Though it was easy to extend this functionality, by creating a 'checkbox_admin' argument, I didn't like the idea of patching it in after every django update. So I searched the tickets and found out there was also someone else interested in the idea. But then it hit me, ticket was closed with resolution 'wontfix' (http://code.djangoproject.com/ticket/2004). I am curious, why? Another issue was with "BooleanFields". I noticed they always hit the history even if not changed. Someone else had noticed this too and already posted a ticket (http://code.djangoproject.com/ticket/1511). Pretty easy to fix but has been open for 4 months? These are very small fixes/enchantments but still kind of frustrating to apply them yourself after updating django. So my question is, what is the reason to ignore this kind of tickets? By the way, is there going to be an automatic 'detail' view for objects + "Can view <object>" permission in the administration interface? Would come in handy (again relatively easy to extend yourself, but...) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
