mirror
/
django-simplecms
kopia lustrzana https://github.com/rtts/django-simplecms
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność
django-simplecms/example/app/views.py

28 wiersze
751 B
Python
Czysty Zwykły widok Historia

Move ContactForm back to cms package. Where should it live?
2020-01-06 11:51:10 +00:00
from cms.forms import ContactForm
A new templatetag 'includesection' now renders a section with its own context, as provided by the polymorphic subsection's registered view. Also, I'm trying to move all the website-related cruft from cms into the example project, so that only the Page and Section models with their own "admin" views will remain.
2020-01-05 02:36:23 +00:00
from cms.views import SectionView, SectionFormView
Minor
2020-01-02 19:30:24 +00:00
from cms.decorators import register_view
New machinery for registering custom views Each custom section can now have their own associated custom SectionView. SectionView subclasses behave just like Django's generic views, except they return Section objects instead of http responses. The updated PageView takes care of compositing all rendered sections into the final response. Nice!
2020-01-02 18:32:15 +00:00
from .models import *
A new templatetag 'includesection' now renders a section with its own context, as provided by the polymorphic subsection's registered view. Also, I'm trying to move all the website-related cruft from cms into the example project, so that only the Page and Section models with their own "admin" views will remain.
2020-01-05 02:36:23 +00:00
@register_view(TextSection)
class TextView(SectionView):
template_name = 'app/sections/text.html'
@register_view(ButtonSection)
class ButtonView(SectionView):
template_name = 'app/sections/button.html'
@register_view(ImageSection)
class ImageView(SectionView):
template_name = 'app/sections/image.html'
@register_view(VideoSection)
class VideoView(SectionView):
template_name = 'app/sections/video.html'
New machinery for registering custom views Each custom section can now have their own associated custom SectionView. SectionView subclasses behave just like Django's generic views, except they return Section objects instead of http responses. The updated PageView takes care of compositing all rendered sections into the final response. Nice!
2020-01-02 18:32:15 +00:00
@register_view(ContactSection)
A new templatetag 'includesection' now renders a section with its own context, as provided by the polymorphic subsection's registered view. Also, I'm trying to move all the website-related cruft from cms into the example project, so that only the Page and Section models with their own "admin" views will remain.
2020-01-05 02:36:23 +00:00
class ContactFormView(SectionFormView):
New machinery for registering custom views Each custom section can now have their own associated custom SectionView. SectionView subclasses behave just like Django's generic views, except they return Section objects instead of http responses. The updated PageView takes care of compositing all rendered sections into the final response. Nice!
2020-01-02 18:32:15 +00:00
form_class = ContactForm
success_url = '/thanks/'
A new templatetag 'includesection' now renders a section with its own context, as provided by the polymorphic subsection's registered view. Also, I'm trying to move all the website-related cruft from cms into the example project, so that only the Page and Section models with their own "admin" views will remain.
2020-01-05 02:36:23 +00:00
template_name = 'app/sections/contact.html'