thanks for your reply Jacob. Am 30.11.2006 um 15:27 schrieb Jacob Kaplan-Moss:
> > On 11/30/06 6:51 AM, patrickk wrote: >> we had this problems recently: >> 1. it´s currently not clear which columns are searched when using the >> search-field in the admin-list. that´s sometimes very strange, >> especially when using model-methods. >> 2. it´s not possible to have multiple search-fields, each one >> searching different columns. this is very restrictive IMHO. > > While those are certainly good, valid criticisms, I should point > out that > there are equally valid criticisms of multiple search fields. The most > prevalaent one, and the one we thought about when making a single > search > field, was the "which box am I supposed to search in?" problem. > > Remember: the admin is designed for non-technical users; many > people who use > it on a daily basis have no idea what a "model" or a "field" is, > and to them a > bunch of search boxes can just be intimidating. I see your point (somehow). Still, having the _possibility_ to have multiple search-fields, it´s still the designers/programmers decision whether to use them or not. Moreover, I don´t see why multiple search-fields have anything to do with the knowledge of models and/or fields. Note: We're currently having about 15 people/editors using the Django Admin-Interface and the lack of search-options is probably the most critized issue (I know that this is a very personal experience ...). > > Again, it's not that your criticisms aren't good -- they are! -- I > just want > to point out that we've considered the trade-offs here. > >> since my last post concerning the admin-interface didn´t provoke any >> reactions, I´m not quite sure whether this issues are interesting for >> the django-developers. > > In general, I prefer the admin interface to be more "top down" than > the rest > of Django. I can go more into depth about my philosophy here if > anyone's > interested, but it really boils down to the fact that open source > *design* > doesn't work nearly as well as open source *code*. So I beg your > forgiveness > while we keep the admin cards close to our chest. I´m very interested in your philosophy. offtopic: I´ve just been watching the screencast for the Symfony Admin Generator and I was really impressed with the flexibility. At the risk of changing the thread-issue I´m listing some (very personal) advantages of the Symfony Admin Generator here: 1) multiple search-fields (yes, again). 2) flexibility: since Symfony generates a single HTML-page for every list and form, it´s very ease to (re)design a page. In Django, there ´s HTML-Code generated within the views (which is very strange, IMHO). 3) the configuration is not in the models-file. IMHO, the models-file is the wrong place. 4) validation error-messages can be overwritten without using the language-file (you are able to do that in the configuration-file). patrick > > Thanks, > > Jacob > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
