glasses-ui

G2 glasses UI layouts are built on a fixed 576x288 canvas using text containers, image containers, and lists. The system enforces per-page container rules, event-capture layers, and manages rendering through page lifecycle methods like createStartUpPageContainer and rebuildPageContainer.

G2 glasses UI pages enforce strict per-page container rules, including maximum container counts, event-capture layer requirements, borders, and positioning constraints. These rules ensure consistent content-driven UIs on the constrained 576x288 display without rendering conflicts.

Manage G2 app container lifecycles using methods like createStartUpPageContainer, rebuildPageContainer, textContainerUpgrade, updateImageRawData, and shutDownPageContainer. These methods handle page rendering, text updates, image workflows, and proper container teardown.

Yes, image containers in G2 glasses UI layouts can be updated dynamically using the updateImageRawData method. This supports image workflows and event handling patterns within the 576x288 canvas constraints.

The best way to start prototyping a G2 glasses UI is to create a starter page on the 576x288 canvas with at least one text container and one image container. This establishes the structured container definitions needed for further event handling and lifecycle management.

G2 glasses UI layouts fail to render consistently when per-page container rules are violated, such as exceeding maximum containers or ignoring event-capture layer requirements. Applying proper lifecycle methods like rebuildPageContainer ensures precise rendering on the constrained display.