A different Form of navigation
summary
Shows using HTML forms as the primary navigation state: carry a form’s selections across full page requests and also instantiate a form from a link by storing serialized forms in the database. Uses the django-modelqueryform package to build model-driven query forms against a 150 GB dataset (≈130 million records, 47 fields), produces maps and stratified views, and caches long queries so a 2–3 minute report can be served from cache in ~5 seconds. Implements binding, hidden forms, and thresholds to avoid leaking small counts.
AI-written summary · about
chapters (10)
- 0:00Introduction to forms
- 1:11Problem with data tools
- 2:35Case study RiskScape
- 5:24Form context across pages
- 8:35Reusable search framework
- 11:45Link-initiated forms
- 13:55Caching and metrics
- 15:43Resources and Q&A
- 16:54Security considerations
- 20:24Browser limitations
related talks
53mDjango: a Data Shovel With a Future
18mBuilding theatlantic.com homepage’s WYSIWYG admin with...
36mWhat's New in Newforms-Admin?
23mSolving Problems With Django Forms
26mBuilding Dynamic Dashboards With Django and D3
23mOptimizing your webapp by using django-debug-toolbar
26mA Related Matter: Optimizing your webapp
27mGood form: How Django’s form rendering improved during the 4.x series