From 768bbc14f778b032a8d7e9ed45f6fa800183389b Mon Sep 17 00:00:00 2001 From: Michael Elsdoerfer Date: Fri, 23 Oct 2009 03:11:24 +0200 Subject: [PATCH] Added some considerations wrt adding filtering support. --- README | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/README b/README index 6a161f5..41b5afc 100644 --- a/README +++ b/README @@ -599,4 +599,16 @@ We need to think about how we make the functionality available to templates. Another feature that would be important is the ability to limit the valid -values for a filter, e.g. in the date example only years from 2000 to 2008. \ No newline at end of file +values for a filter, e.g. in the date example only years from 2000 to 2008. + +Use django-filters: + - would support html output + - would not work at all with our planned QueryTable + - conflicts somewhat in that it also allows ordering + +To autoamtically allow filtering a column with filter=True, we would need to +have subclasses for each model class, even if it just redirects to use the +correct filter class; + +If not using django-filter, we wouldn't have different filter types; filters +would just hold the data, and each column would know how to apply it. \ No newline at end of file -- 2.26.2