day-cli 0.0.6

Declarative app development API using native UI toolkits
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41

//! {{title}} — a [Day](https://daybrite.dev) app. `root()` is the whole UI, shared by every
//! platform; each navigation destination lives in its own module under `pages/`.

use day::prelude::*;

mod pages;
use crate::pages::*;

day::routes! {
    /// The app's sections, typed (https://daybrite.dev/docs/navigation): each variant's key is
    /// what deep links, dayscript, and `current_route()` speak, and the `.item(Section::…)`
    /// declarations below are compile-checked against this enum.
    pub(crate) enum Section {
        Home => "home",
        Controls => "controls",
        Canvas => "canvas",
        Items => "items",
    }
}

pub fn root() -> AnyPiece {
    install_locales("en", &[("en", include_str!("../locales/en/app.ftl"))]);
    // A sidebar selector bound to a Signal<Option<Section>> (`None` = nothing selected — the
    // collapsed list on mobile). Desktop shows sidebar + detail side by side; mobile shows a
    // list that pushes the detail. Deep links and dayscript address sections by key.
    let section = Signal::new(None::<Section>);
    selector(section)
        .style(SelectorStyle::Sidebar)
        .title(tr("app-title"))
        .item(Section::Home, tr("nav-home"), home_page)
        .item(Section::Controls, tr("nav-controls"), controls_page)
        .item(Section::Canvas, tr("nav-canvas"), canvas_page)
        .item(Section::Items, tr("nav-items"), items_page)
        .id("nav")
        .any()
}

// Mobile / embedded entry points — each macro expands to nothing off its own platform.
day::ios_main!("{{title}}", root);
day::android_main!(root);
day::arkui_main!(root);