Generic Views and Custom Views
July 26th, 2006 posted by Bender Rodríguez
**brief overview of our use of generic and custom views**
for the CMS Editor, i have used generic views for the most part to handle the CRUD operations. this is adequate for layouts and snippets, since we only deal with one data model (one table). with pages, however, we must work with both the pages table and the page_parts table. so i created a custom view for the create page process, but used a generic view for the edit process. this will have to change, since we need the ability to edit, not just the content of the page, but also the title and path, as well as the parent page, since we will need the ability to reorganise the structure of any given branch on the site. and we will want to have the option of changing the layout, the status, and adding or deleting page parts.
one note on the delete view. this is a custom view also, and is based on the django admin delete manoeuvre, which is really very cool and will provide the inspiration for creating a tree like editor like you see in RadiantCMS. when you choose to delete an object, like a page, you are directed to a confirmation page that will tell you if there are any child objects that will be deleted as well. so, for example, if you wanted to delete the "about" page, you will see a list of child objects that will be deleted as well: the about body; the staff page and staff body; etc.
0 Comments,
0 trackbacks
(
Trackback URL)