I was recently working with django's syndication framework, and noticed 
that it felt clunky in a lot of ways. For example, I can only access the 
request and the kwargs for the function during the get_object method; if I 
want to do anything more complicated with them - for example, say I want to 
limit the items returned based on a tag that's in a GET parameter - there's 
not much that I can do. (I've chosen to return a dictionary from get_object 
containing the actual object and any variables that I want to have passed 
around to all the different methods.)

It seems like this would be a great place to dogfood the new CBVs; they 
could bring a lot of elegance to the framework. (For example, the whole 
'dynamic attribute' feature would be unnecessary.) This is obviously 
something that can be done as a third-party app first; I'm just curious 
whether this is something that (generally speaking) people would be 
interested in seeing. I tried checking the tracker and google for previous 
discussions about this, but didn't find anything.

--Stephen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/ZCKJd55-p4kJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to