Using new classbased generic views in contrib.databrowse

Hi,

Do you think it is relevant to rewrite databrowse to use the new class-
based generic views ?
I'm motivate to work around this and submit a patch, but want first to
discuss about what to do..
IMHO, contrib.databrowse (using class-based views) can provide a
reusable/extendable "base" for rapid development.

Do you use databrowse ? and how (extending the classes ? , or just by
providing your own the template ?)
a JSON/CSV/XLS output could be useful too in databrowse (theses two
last formats could also become core.serializers btw.)

Michael

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.