Hey Patrick -- On Tue, Jul 7, 2009 at 1:04 AM, patrickk <[email protected]> wrote:
> > [snip] > > there´s a lot more to say here, but I´m not sure if this is somehow > related to your work - not sure if you only work on the inline-stuff > or the admin-interface overall. Both my GSoC project and future interests lie in improving the overall usability of the admin interface, so feel free to pitch away. > besides the index-page, someone should take a look at the html/css. > the programming is a mess in certain places (e.g., every input-field > on the change-form has a class, but decimalfield and floatfield don > ´t). moreover, the naming of the css-classes doesn´t seem to be well > thought out. I'll take a look at the decimalfield and floatfield classes. If there are other major inconsistencies, let me know and/or file a bug. > something which is related to inlines: currently, with stacked-inlines > you´re having "comment #1 ...", "comment #2 ..." and so on on the left- > hand side. IMHO, you should display __unicode__ there (I hope you know > what I mean). because with 20 comments listed there, one has to click > through all items to actually see what´s in there ... > one more thing: it currently says "Add a choice" - I´m not sure if > this should be "Add a Choice" in order to be translated correctly. It actually *is* the __unicode__ of the model -- I just happened to specify __unicode__ for comments as "Comment #%(id) @ %(time)". All good stuff. Thanks! Zain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
