Yeah, I agree, as it is, I can't see any reason why I would use it, but I
could see it being useful with some modifications such as:
1) Being able to create redirects (which seems to already be on the
todo-list)
2) Being able to specify extra kwargs to pass to a view so that it would be
possibl
As an outsider with very little data (so you can ignore this if you
strongly disagree), I sort of agree with the notion that "WONTFIX" could be
sending a different signal that it is being used for.
WONTFIX to me would mean, "We acknowledge that this is an annoyance for
some people, but we're no
So a former co-worker with some help/guidance from me developed a component
system on top of Django that sounds sorta like what you are all talking
about. It's very complicated and I'm still not sure whether it was
ultimately a good idea to use or not, but it does make some things very
simple (
lows a specific formula so it can be
automatically updated on ajax requests: `cmp__id`
{% endcomment %}
{% comment %}
Similarly, you can grab the rendered html from the component by
asking for `component_name` from the dictionary of rendered html
Speaking only for myself and the component framework we built here, I don't
think I would expect it to ever be rolled into Django itself.
However, the framework we made does work without any modifications to
Django and works just fine alongside existing function and classed based
views. This me
