Changes between Version 7 and Version 8 of ListColumns

Timestamp:

Oct 27, 2010, 10:38:43 AM (14 years ago)

Author:

Alex Kamedov

Comment:

--

ListColumns

@@ -3 +3 @@
 Related ticket: #8054 Move method properties for admin list customization to ModelAdmin
 
-This ticket adds:
+Ticket goals are:
 
- * beautifully API to admin change list customization
+ * to change list_display syntax;
+ * add to list_display_links the same items type support as list_display has (Now Django allows to use in list_display_links only model fields, properties or methods).
 
- * ability to customize and localize 3rd-party application without fork it
+The current approach for customising list_display seems contrary to the spirit of newforms-admin. Method properties such as .short_description, .boolean and .allow_tags rarely belong in the model definition.
 
- * ability to apply custom template filters on field value or model method returned value without any magic
-
- * ability to specify witch field will be used in order for column based on model method
+In fact, I noted that these options, for customising the look of the list column, duplicate filter functionality. .allow_tags is exactly |safe; |boolean could be a filter provided by django.contrib.admin.templatetags. The case is much more convincing when you take into account user-defined filters: if I already have a filter for presenting values for user consumption, I should not need to provide a model method to replicate or apply that filter.
 
 
@@ -82 +81 @@
         bar_column,
         admin.ListColumn('foo', header='Foo Description', filter='boolean_icon'),
-        'baz',
+        admin.ListColumn('baz', filter='truncatewords:"2"|slugify'),
         'bonk',
         admin.ListColumn('ends', filter='timeuntil', header="Ending in"),
@@ -90 +89 @@
 
 }}}
+
+In the example
+
+{{{
+admin.ListColumn('baz', filter='truncatewords:"2"|slugify'),
+}}}
+
+would render exactly the same as
+
+{{{
+{{row.baz|truncatewords:"2"|slugify}}
+}}}
+