Files
faceclaw/app/app.css
T
James Babcock b99aa85964 Move phone screen connection status and warnings to the top bar
<details>
<summary>Prompts Used</summary>
On the main page, there's a triple-dot menu. Its icon is currently black-on-dark (this is true on both a light-mode device and a dark-mode device; the top bark has a dark background in both cases). Make that icon white instead.

We have a connection-status indicator on the main page, that says "Disconnected" or "Connected" or "Reconnecting". Let's move this onto the top-bar, as white text, right-aligned next to the triple-dot menu.

We have several problem-status warnings, eg for not having battery-optimization permission, that appear on the main page in the form of a large button below the screen preview. Let's convert all of thes into a yellow triangle ! icon that appears on the top bar, in between the connection-status indicator and the triple-dot menu. Tapping it will open a modal that shows the message that was previously shown, with a button to do the suggested action.

> All three changes are in, and the project builds and typechecks cleanly. Here's what I did:
>
> **White overflow icon** — The root cause is that NativeScript builds its toolbar programmatically, so the `theme` overlay in `NativeScriptToolbarStyle` (an XML-inflation-time attribute) never applied, and the overflow icon fell back to the light activity theme's dark `textColorSecondary`. I added an `actionOverflowButtonStyle` with a white `android:tint` to `AppThemeBase` in `App_Resources/Android/src/main/res/values/styles.xml`, so the icon is white on every page's bar (they all share the dark #424242 background), in both light and dark device themes.
>
> **Connection status in the top bar** — The ActionBar now has a custom titleView (`main-page.xml:5`): "Faceclaw" on the left, and a right-aligned white status label next to the menu. Since the old status string could be a whole sentence ("Reconnecting after ...", "Failed: ..."), the bar shows a short label derived from the connection phase — Connected / Connecting / Reconnecting / Disconnected / Charging / Disconnecting / Failed — and tapping it opens an alert with the full status message, so failure details aren't lost. The old status label below the controls is removed.
>
> **Warnings → ⚠️ icon + modal** — The three inline warning blocks (Even-app conflict, firmware, battery optimization) are gone from the page body in both portrait and landscape. A yellow warning-triangle emoji now sits between the status label and the overflow menu whenever any warning is active. Tapping it opens an in-page modal (same overlay pattern as the existing text-setting editor) titled "Attention needed", listing each active warning with its original message and action button, plus a Close button. The modal closes when you take an action, and auto-closes if the last warning clears while it's open. One side effect: the landscape layout previously showed the firmware warning without its install button — in the modal it now has the button like everything else.
>
> Worth an on-device check: the overflow-icon tint (theme change, so a full reinstall rather than hot reload), and that the titleView labels sit vertically centered against the toolbar height.
<hr>
Thanks. That all looks good, except there are some stylign issues on the warning modal. On a wide tablet, the modal is full-width, which is too wide. When the device is dark-mode, the "Attention needed" title is white-on-light-gray. The title and the warning text need some left/right padding between them and the edges of the modal.

> All three styling issues are fixed and the build is clean:
>
> - **Too wide on tablets**: the modal's width now comes from a `warningsModalWidth` getter in the view model — screen width minus the margins on phones, capped at 480 DIPs on tablets — and it's centered horizontally. It re-computes on orientation change along with the other layout metrics.
> - **White title in dark mode**: the theme's `.ns-dark .h2` rule was beating my `.warnings-modal Label` rule on specificity. I added a `.ns-dark .warnings-modal Label` selector so all text in the modal stays dark-on-light in both modes (the modal deliberately keeps its light look, matching the text-setting modal).
> - **Missing edge padding**: NativeScript ScrollViews don't apply their own padding to their content, so the `padding: 16` on the modal was silently doing nothing. It now lives on an inner `warnings-modal-content` StackLayout; the border/background/margin stay on the ScrollView.
>
> One note: the text-setting editor modal (`system-name-modal`) uses the same `h2`-on-light-background pattern, so its title likely has the same white-on-light problem in dark mode — I left it alone since you only flagged the warnings modal, but it'd be the same one-line fix if you want it.
</details>
2026-08-25 23:09:21 -07:00

463 lines
8.5 KiB
CSS

@import '@nativescript/theme/css/core.css';
@import '@nativescript/theme/css/default.css';
Page {
background-color: #ffffff;
color: #222222;
}
ActionBar {
background-color: #424242;
color: #ffffff;
}
ActionItem {
color: #ffffff;
}
/* The main page's custom titleView: title left, connection status and the
* warning triangle right-aligned beside the overflow menu. */
.action-bar-title {
color: #ffffff;
font-size: 18;
font-weight: bold;
vertical-align: center;
}
.action-bar-status {
color: #ffffff;
font-size: 14;
margin-right: 12;
vertical-align: center;
}
/* The emoji brings its own yellow; the padding widens the tap target. */
.action-bar-warning {
font-size: 18;
padding: 4 6;
vertical-align: center;
}
TextField {
background-color: #ffffff;
color: #222222;
}
/* Without this, the theme's .ns-dark rules recolour the text white while the
* white background above sticks, rendering white-on-white fields.
* Order matters: .system-name-modal TextField must stay after this rule so the
* deliberately light modal wins the equal-specificity tie in dark mode. */
.ns-dark TextField {
background-color: #2e2e2e;
color: #f0f0f0;
}
.system-name-modal TextField {
background-color: #ffffff;
color: #222222;
}
Button.-primary {
font-size: 18;
}
/* Body/explanatory text in the onboarding flow; the theme default is too
* small to comfortably read paragraphs of legalese, especially on tablets. */
.body-text {
font-size: 18;
}
/* The logo art is black-on-transparent; tint it light in dark mode so it
* doesn't vanish into the dark page background. */
.ns-dark .onboarding-logo {
tint-color: #e6e6e6;
}
/* License / privacy-policy links in the onboarding disclaimer footer. The
* padding widens the tap target beyond the small text. */
.footer-link {
color: #3b6fd6;
font-size: 15;
text-decoration: underline;
padding: 4 8;
}
.ns-dark .footer-link {
color: #8ab0ff;
}
.footer-link-separator {
color: #777777;
font-size: 15;
padding: 4 0;
}
/* Bundled project docs (phone-ui/document-page). LICENSE and PRIVACY are
* hard-wrapped plain text, so keep the size modest to limit rewrapping. */
.document-text {
font-size: 13;
}
/*
* Stands in for the lens preview when showing it would be misleading (silent
* mode, or a disconnect explained by a flat battery). Sized by the view model
* to the preview's own box so the form doesn't reflow, and kept dark so it
* reads as "where the preview goes" rather than as a page-level banner.
*/
.display-preview-message {
background-color: #222222;
color: #ffffff;
padding: 16;
}
.display-preview-message Label {
font-size: 18;
text-align: center;
}
.system-name-modal {
margin: 16;
padding: 16;
background-color: #f6f6f6;
color: #222222;
border-color: #222222;
border-width: 1;
border-radius: 8;
}
/* Modal behind the action bar's warning triangle: the problem-status warnings
* that used to sit inline on the main page, each with its fix-it button.
* The width is set from the view model (near-full-width on phones, capped on
* tablets); the padding lives on the content stack because a ScrollView does
* not apply its own padding to its content. */
.warnings-modal {
margin: 16;
background-color: #f6f6f6;
color: #222222;
border-color: #222222;
border-width: 1;
border-radius: 8;
}
.warnings-modal-content {
padding: 16;
}
/* The modal stays light in dark mode; the .ns-dark pairing outguns the
* theme's dark-mode recolour of Label/.h2 so the title doesn't go
* white-on-light-gray. */
.warnings-modal Label,
.ns-dark .warnings-modal Label {
color: #222222;
}
.warnings-modal-item {
margin-bottom: 12;
}
/* The phone's controller for the glasses (phone-ui/remote-controls.xml). */
.remote-controls {
margin: 0 8 0 8;
}
.display-controls {
margin-bottom: 6;
}
.mode-button {
font-size: 13;
padding: 6 10;
margin-right: 6;
}
.brightness-icon {
font-size: 16;
margin: 0 4 0 4;
color: #444444;
}
.auto-toggle Label {
font-size: 13;
margin-right: 2;
}
.touchpad {
height: 230;
background-color: #1f1f1f;
border-radius: 14;
border-width: 1;
border-color: #3a3a3a;
color: #f0f0f0;
margin-top: 2;
}
.pad-focus {
font-size: 20;
color: #ffffff;
}
.pad-dpad-button {
width: 46;
height: 46;
margin: 6;
padding: 0;
font-size: 16;
border-radius: 23;
background-color: #333333;
color: #e8e8e8;
}
.pad-dpad-down {
margin-bottom: 30;
}
.pad-legend {
font-size: 11;
color: #8a8a8a;
margin-bottom: 8;
}
.action-row {
margin-top: 6;
}
.action-button {
margin: 2;
font-size: 14;
}
.ring-row {
margin-top: 4;
}
.ring-label {
font-size: 12;
color: #666666;
margin: 0 6 0 4;
}
.ring-button {
width: 44;
height: 36;
margin: 1;
padding: 0;
font-size: 13;
}
/*
* Pairing scan list (phone-ui/pairing-page). Rows are Repeater items: product
* art (or a colourway swatch) on the left, decoded SKU + proximity + serial in
* the middle, a chevron/check on the right.
*/
.pairing-instructions {
color: #555555;
font-size: 14;
}
.pairing-status {
font-size: 14;
margin-left: 8;
}
.pairing-section {
font-size: 16;
font-weight: bold;
margin-bottom: 4;
}
.pairing-empty {
color: #777777;
font-size: 14;
padding: 8 0;
}
.pairing-row {
background-color: #f4f4f4;
border-color: #dddddd;
border-width: 1;
border-radius: 10;
padding: 10;
margin-bottom: 8;
}
.pairing-row-selected {
background-color: #e6f0ff;
border-color: #3b6fd6;
}
.pairing-row-incomplete {
background-color: #fafafa;
border-color: #e6e6e6;
}
.pairing-art {
vertical-align: center;
}
.pairing-title {
font-size: 16;
font-weight: bold;
color: #222222;
}
.pairing-badge {
font-size: 11;
font-weight: bold;
color: #2a5bc4;
background-color: #dbe6fb;
border-radius: 9;
padding: 1 7;
}
.pairing-variant {
font-size: 13;
font-weight: bold;
color: #333333;
}
.pairing-proximity {
font-size: 12;
color: #666666;
}
.pairing-proximity-immediate {
color: #2a5bc4;
font-weight: bold;
}
.pairing-serial {
font-size: 12;
color: #666666;
font-family: monospace;
}
.pairing-arms {
font-size: 12;
color: #444444;
}
.pairing-warning {
font-size: 12;
color: #a33a1f;
margin-top: 4;
}
.pairing-swatch-label {
font-size: 11;
color: #555555;
}
.pairing-chevron {
font-size: 22;
color: #444444;
margin-left: 6;
}
.pairing-selection {
background-color: #eef4ff;
border-radius: 10;
padding: 10;
}
Button.pairing-link {
background-color: transparent;
color: #2a5bc4;
font-size: 14;
border-width: 0;
}
/*
* Permissions screen (phone-ui/permissions-page). Cards reuse the pairing-row
* / pairing-title / pairing-badge look above; these add the explanation body
* and the already-granted checkmark.
*/
.permissions-description {
font-size: 13;
color: #555555;
margin-top: 2;
}
.permissions-check {
font-size: 24;
color: #2e7d32;
margin-left: 10;
}
/* Continue with required permissions still missing: looks disabled but stays
* tappable (the tap raises an are-you-sure prompt instead of being ignored). */
Button.permissions-primary-dimmed {
opacity: 0.45;
}
/*
* Dark-mode pairing page. The cards keep their light-mode look above; here
* they go dark-gray, and every text colour set above gets a light counterpart
* so nothing renders dark-on-dark (the instructions) or dark-on-a-dark-card.
* Order matters: the -selected/-incomplete rules must follow .pairing-row so
* they win at equal specificity.
*/
.ns-dark .pairing-instructions {
color: #b0b0b0;
}
.ns-dark .pairing-empty {
color: #999999;
}
.ns-dark .pairing-row {
background-color: #2e2e2e;
border-color: #4a4a4a;
}
.ns-dark .pairing-row-selected {
background-color: #333c4c;
border-color: #5b8def;
}
.ns-dark .pairing-row-incomplete {
background-color: #282828;
border-color: #3c3c3c;
}
.ns-dark .pairing-title {
color: #f0f0f0;
}
.ns-dark .pairing-badge {
color: #a8c4f5;
background-color: #2a3b5e;
}
.ns-dark .pairing-variant {
color: #cccccc;
}
.ns-dark .pairing-proximity {
color: #a0a0a0;
}
.ns-dark .pairing-proximity-immediate {
color: #7da7f5;
}
.ns-dark .pairing-serial {
color: #a0a0a0;
}
.ns-dark .pairing-arms {
color: #c0c0c0;
}
.ns-dark .pairing-warning {
color: #e08a66;
}
.ns-dark .pairing-swatch-label {
color: #aaaaaa;
}
.ns-dark .pairing-chevron {
color: #bbbbbb;
}
.ns-dark .pairing-selection {
background-color: #2e2e2e;
}
.ns-dark Button.pairing-link {
color: #7da7f5;
}
.ns-dark .permissions-description {
color: #b0b0b0;
}
.ns-dark .permissions-check {
color: #7bc47f;
}