classy-python / ccbv Goto Github PK

Because of this commit: 150dc61

Perhaps by appropriately indenting the MRO?

ie. 1.5b2

From cbv/models.py:132:

models.Max('module__project_version__version_number')

I was interested in seeing the actual source code for a View. Would be nice to link from the footer.

We have travis running (#66), so now we need ALL OF THE TESTS!

https://github.com/refreshoxford/django-cbv-inspector/graphs/contributors

We have multiple parents for some models. We need an efficient way to traverse this tree.
The way we do it here is grossly inefficient: 9519a5b#L0R89

Perhaps django-mptt ? -- can it cope with multiple parents?

http://ccbv.co.uk/projects/Django/1.4/django.views.generic.edit/FormView/#dispatch

Should open up the dispatch method so I can send it to someone.

As per Django, it would also be nice if a clickable ¶ appeared so we could easily get the permalink.

even better, I'd link to link direct to lines of the code within the method (like on Github).

For example on page http://ccbv.co.uk/projects/Django/1.4/django.views.generic.list/ListView/ I can't get to "django.views.generic.list".

Note the word "implmenting".

It would be cool to be able to drop this into any django 1.3, 1.4 or 1.5 project and have it generate the documentation.

Django 1.5 support would be nice

Is there a nice way of indicating the file name where we show the new line numbers added with #70? Must play nicely with #37

ie instead of

from django.views.generic.edit import DeleteView

we could have:

from django.views.generic import DeleteView

shown at the top of the page.

Only the direct parents of a class are shown.

...and are especially broken where there is no docstring. eg http://ccbv.co.uk/projects/Django/1.4/django.views.generic.dates/MonthMixin/

Closely related to issue #1.

eg for TemplateView:

in views.py:

from django.views.generic import TemplateView

class HomeView(TemplateView):
    template_name = 'home.html'

in urls.py:

from django.conf.urls import patterns, url
from views import HomeView

urlpatterns = patterns('',
    url(r'^$', HomeView.as_view(), name='home'),
)

An extended example could show how to add extra context, or dynamically choose the template..

See #30

paginator_class = Paginator should be on MultipleObjectMixin.
response_class = TemplateResponse should be on TemplateResponseMixin.

ie. 1.5b2

From cbv/models.py:132:

models.Max('module__project_version__version_number')

Related to #41

It would be nice if people actually found the website ;)

Currently there is only Django 1.4a.

Since class based views came out in 1.3 it would make sense to include that, 1.3.1 and at least 1.4RC1 as options.

...and display them together in MRO.

Design for this will need some thought.

Users spend a lot of time on the site bouncing around worthless pages. They are to be removed. Lists are boring, and many users drop off the site before finding the real content.

We need to take users straight to where they want to go.

...by adding https://github.com/jezdez/django_compressor

There's something up with the Generic box.

We get a lot of international traffic. (Especially from Russia! Привет!) It would be nice to reward that with i18n support.

Make it fit the style of the site, and have a link back to the home page or something.

Currently in the form:
response_class = <class 'django.template.response.TemplateResponse'>

Looks a bit unformatted.

Would probably be a change in get_value.

That way, we can make reliable fixtures for each version of django.

When looking at methods on a class whose MRO gives it a few super classes for the given method it's hard to tell which comes first. Probably not the most useful change since you can't jump in the middle of the methods that are called, but would be useful.

Can we automate this once #39 is complete?

Having merged #52, some docs links are now broken/missing:

[
    (u'1.4', u'GenericViewError'),
    (u'1.3', u'GenericViewError'),
    (u'1.5', u'GenericViewError'),
    (u'1.5', u'BaseDetailView'),
    (u'1.5', u'BaseCreateView'),
    (u'1.5', u'BaseDeleteView'),
    (u'1.5', u'BaseFormView'),
    (u'1.5', u'BaseUpdateView')
]

The button in the hero-box on the home page should link straight to the view, as all the Views are linked to from there (In descendants).

We should do a fuzzy match on the class name, and redirect to the correct class in the latest version.

@mattack108's new line numbers don't seem to play nicely with firefox:

Having both 1.3.1 and 1.4 is great, but for people working towards the next version of Django having a version rebuilt periodically off master would be awesome too :-)

& then add latest as a version in the urls.