Added some considerations wrt adding filtering support.

diff --git a/README b/README
index 6a161f5ef31651595b2d599040812321afa4fa99..41b5afce4caf4c16cddd7547adfd69bdcad946ba 100644 (file)
--- a/README
+++ b/README
@@ -599,4 +599,16 @@ We need to think about how we make the functionality available to
 templates.\r
 \r
 Another feature that would be important is the ability to limit the valid\r
-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.\r
+\r
+Use django-filters:\r
+    - would support html output\r
+    - would not work at all with our planned QueryTable\r
+    - conflicts somewhat in that it also allows ordering\r
+    \r
+To autoamtically allow filtering a column with filter=True, we would need to\r
+have subclasses for each model class, even if it just redirects to use the \r
+correct filter class; \r
+\r
+If not using django-filter, we wouldn't have different filter types; filters \r
+would just hold the data, and each column would know how to apply it.
\ No newline at end of file