Usage

After you have read the QuickStart you can now head into the special configuration. This chapter is split into four sections. Views are the center of configuration. Here you define which form to use, how templates are located and under which route it should be available. Views also needs Forms. These define the associated model and configure which fields are displayed. Finally, if the default templates don’t suit you (e.g. you want to integrate your own style or you don’t use Mako), you can visit the Templates section to see how to change the default templates.

There are also some Examples that show possible applications. You can refer there to see how your goal can be realized in pratice. To change the global behavior of the library refer to Configuration. This is useful if the default global application behavior does not suit you.

• Configuration
  • Static View URL Prefix
• Views
  • Add a New View
  • Configuration
    • View & Route Setup
    • The Info Dictionary
  • API
    • CRUDView
    • ViewConfigurator
• Forms
  • Add a New Form
  • Configuration
    • Fieldset Templates
  • Inline Forms / One-To-Many
  • Many-To-One & One-To-One
  • Extra Forms
    • CSRF
  • Fields
• Templates
  • Changing a Single Template
  • Create a Complete Theme
    • Keeping Some Templates from the Default Library
  • Supporting Different Template Engines
• Utility Functions
  • API
• Adding Actions to Forms
  • Introduction
    • What are actions?
    • How do you configure actions?
    • So how do I create an action exactly?
    • And how do I add it to a view?
  • Advanced Techniques
    • Handling Errors
    • Returning Values From Actions
    • Actions as Methods on the View
    • Currently Unspported Features from Django
• Help Topics
  • Transition From Django
    • ModelAdmin Configuration Options
  • FAQ
• Examples