Every chapter in a project must use the same user interface design. This ensures a consistent look and feel for the user.
By Pawan Nayar · from the LLOS AI Learning record
Every chapter in a project must use the same user interface design.
This ensures a consistent look and feel for the user.
A developer must use the same viewer shell for every chapter. This means using the same layout for elements on the screen. It also means using the same types of panels and how they look. Tooltip designs, animations, and other visual elements must also be the same. A contract document, like `CH1_UI_CONTRACT.md`, lists all these design rules.
A developer is building an educational application with multiple chapters. The developer uses the design from chapter one for all other chapters. This means all chapters have the same menu style and button appearance. If the developer creates a new button style for chapter two, the application will look inconsistent.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
Do not use standard browser pop-up boxes like `confirm()`, `alert()`, or `prompt()`. Instead, use custom modal windows that match the application's design.
A good design uses a three-layer system. The first layer is an icon strip.
A new design must use the exact layout proportions of a proven design. The proven design has been refined over many hours.
The user interface for Chapter 1 is the master design. All other chapters must use this design.
Every chapter in a project must use the same user interface design. This ensures a consistent look and feel for the user.