Views Editor

The Views Editor connects your database tables to the outside world. A "view" in Pytigon isn't just a Python class — it's a complete configuration that bundles together: what data to show, how to show it, which URLs to expose, and what actions to allow.

View Types

Pytigon's generic views cover the most common patterns:

View Type	Purpose	Template Used
List	Show multiple records in a table	`[model]_list.html`
Detail/Edit	Show or edit a single record	`[model]_edit.html`
Add	Create a new record	`[model]_add.html`
Delete	Confirm and delete a record	`[model]_delete.html`
Tree	Hierarchical list with expand/collapse	`[model]_tree.html`
Sublist	Nested list within a parent record	`[model]_sublist.html`
Action	Custom server-side action	Dynamic

View Configuration

Through the Views Editor form, you configure:

Data Source

Model — The Django model (table) this view operates on
Filter — Default query filter applied to the queryset
Sort — Default sort field and order
Base filter — Parent record filter (for sublists)

Display Options

Columns — Which fields to show, in what order
Column widths — Percentage or pixel widths
Clickable fields — Fields that link to detail/edit views
Row actions — Buttons per row (edit, delete, custom actions)
List actions — Buttons for the whole table (add, export, custom)

URL Configuration

URL pattern — The URL path for this view
URL name — Django URL name for reverse resolution
Parameters — Dynamic URL parameters (e.g., record ID, filter values)

Permissions

View permission — Who can see this view
Add permission — Who can create new records
Edit permission — Who can modify existing records
Delete permission — Who can delete records
Custom action permissions — Who can trigger specific actions

URL Patterns

Pytigon generates URL patterns following this structure:

[app_name]/table/[TableName]/                                    → List view
[app_name]/table/[TableName]/list/                               → AJAX list data  
[app_name]/table/[TableName]/[base_filter]/[filter]/[target]/[view_type]/
[app_name]/table/[TableName]/[id]/edit/                          → Edit form
[app_name]/table/[TableName]/add/                                → New record form
[app_name]/table/[TableName]/[id]/delete/                        → Delete confirmation
[app_name]/table/[TableName]/action/[action_name]/               → Custom action

The target segment controls output format: - No target = HTML - pdf = PDF document - xlsx = Excel spreadsheet - json = JSON data - odf = Open Document Format - csv = CSV export

View Actions

Custom actions can be defined for list views and row views:

Table Actions (list level)

Act on selected rows
Import/export data
Run batch operations
Generate reports

Row Actions (record level)

Edit, delete, copy individual records
Navigate to related records
Trigger workflow transitions
Run custom business logic

Actions are defined in the view configuration and implemented as methods on the model class or the view class.

Context Variables

Every rendered view receives a rich context including:

title             — Page title
filter            — Active filter from URL
base_filter       — Base filter from URL (parent record ID)
app_name          — Current application name
table_name        — Current table name
doc_type          — Output format (html, pdf, xlsx, etc.)
form              — Filter/search form instance
uuid              — Unique ID for this rendering
readonly          — True if in read-only mode
show_title_bar    — Whether to show the title bar

Use these in your templates to build adaptive, context-aware interfaces.