The Birth of the Page Controller
Why page-level control became necessary and how the first PageController design appeared.
Why page-level control became necessary and how the first PageController design appeared.
The problem of removing event handlers when closures change function identity, and the pragmatic registry solution inside Cotomy.
Entity structure and UI controls are often bound through fragile string matching. This article explores the structural gap and Cotomy’s mitigation approach.
How I handled dynamic HTML input in CotomyElement, where parsing breaks, and why the boundaries became strict.
Why the constructor overloads capture my real design intent: locality, scoped CSS, and practical DOM ownership.
Why Cotomy standardizes query-string search, AJAX submit, and shared form contracts to control long-term cost in business systems.
How CotomyApi is used in real screens: HTTP methods, options, exception mapping, key collisions, and explicit UI updates.
How CotomyElement handles value, text, and what actually gets sent in POST requests.
Practical DOM patterns with CotomyElement: selection, traversal, state checks, sizing, and scroll-driven behavior.
Why Cotomy keeps page lifecycle and cross-form coordination in CotomyPageController instead of scattering ready logic across screens.