3 posts tagged with "overrides"

Rhino's UI is intentionally "open"—you can keep the defaults, or you can surgically replace any piece of the interface. The mechanism that makes this possible is overrides. In this three-part series, we'll walk through why and how to override, what you can (and can't) swap, the safest workflow for copying base components, and the sharp edges to avoid.

This first part covers the foundations: understanding what overrides are, when to use them versus composing with existing components, and establishing a safe, repeatable workflow.

In Part 1, we covered the foundations of Rhino's override system—what overrides are, when to use them, and the basic workflow. Now we'll dive into the tricky parts: overriding behavior (not just markup), leveraging paths for fine-grained control, and real-world patterns that work in production.

In Part 1 and Part 2, we covered the foundations and advanced patterns of Rhino's override system. Now let's put it all together with a complete walkthrough: we'll override the application shell and replace the default table view with a beautiful card-based grid.

This walkthrough demonstrates the copy-adapt-wire workflow in practice with real, production-ready code you can use in your own projects.