Changes between Version 21 and Version 22 of DjangoDesign
- Timestamp:
- Feb 9, 2010, 4:17:57 AM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DjangoDesign
v21 v22 46 46 === Dashboard "Placeholders" === 47 47 48 Grappelli sets a very interesting precedent with regards to adding the concept of "bookmarks", etc. to the admin's index page. I've seen and used numerous projects (such as bartTC's [http://github.com/bartTC/django-memcache-status django-memcached-status]) that add elements to that page. Currently, they place themselves at the top of the app list. Given a few of these, the situation gets ugly fairly quickly. Even if Grappelli's concepts, like bookmarks, never make it to the admin, a block reserved for these types of widgets should be reserved. (BV) 48 Grappelli sets a very interesting precedent with regards to adding the concept of "bookmarks", etc. to the admin's index page. I've seen and used numerous projects (such as bartTC's [http://github.com/bartTC/django-memcache-status django-memcached-status]) that add elements to that page. Currently, they place themselves at the top of the app list. Given a few of these, the situation gets ugly fairly quickly. Even if Grappelli's concepts, like bookmarks, never make it to the admin, a block reserved for these types of widgets should be reserved. (BV) Isn't this solved by the non-CRUD functionality as described below? (AB) 49 49 50 50 === Non-CRUD functionality === … … 56 56 In order to make the admin-interface customizable, flexible and extensible, a set of predefined HTML-blocks and styles are important. The HTML-structure should be defined horizontally (by using a grid as well as some flexible items) and vertically (by defining a set of nested items with a certain hierarchy). (PK) 57 57 58 == List Filters == 59 60 List filters should be able to span relationships. 61 62 The ability to write custom filterspecs is extremely powerful but largely undocumented and limited in important ways. They currently require editing the model definition which limits their use on 3rd party and contrib apps. They are also tied to a specific field which makes it tricky to use them to filter on reverse relationships. 63 64 == Changelist == 65 66 The ability to display columns that span relationships would avoid the need to create model attributes that exist just for the sake of the admin. 67 68 Despite the obvious memory/performance issues there are many cases where the ability to sort by non-db fields in the changelist is extremely useful. One drawback is that this will complicate pagination. 69 70 The ability for admin users to hide and add columns in the changelist and for those changes to persist per user. The list of all available columns should be specified in the ModelAdmin along with an initial set to display. 71 58 72 == Tool Changes == 59 73 60 Changes to the tool set that Django provides that would make life easier as a Django-based designer, such as changes to the template language. 74 Changes to the tool set that Django provides that would make life easier as a Django-based designer, such as changes to the template language. 61 75 62 76 == Valuable external resources == 63 77 64 78 * [http://code.google.com/p/django-grappelli/wiki/djangoissues Issues in Django] identified (and partly solved) by the Grappelli project 79