Struct MenuSpec 

pub struct MenuSpec {
    pub items: Vec<MenuItemSpec>,
}

The desktop app’s identity and native-integration vocabulary, re-exported from the desktop core so app code never names a shell crate: DesktopConfig (the whole declaration — app name, reverse-DNS id, window icon, menu bar, last-window-close policy — handed to App::desktop, run_desktop_config or app!’s desktop = { .. } argument), MenuSpec/MenuItemSpec/MenuRole (the platform-independent native menu tree a per-OS shell translates into an NSApp menu bar or an HMENU), DesktopIconData (decoded, tightly-packed RGBA8 — decoding a PNG/ICO/ICNS is the caller’s job), and DEFAULT_APP_NAME (the window title a config that names nothing still gets).

frust-shell-desktop‘s IconData is re-exported renamed: the facade already carries frust-widgets’ IconData, an in-UI vector icon, and the two are unrelated (one is a BezPath a widget paints, the other is the window/taskbar bitmap the OS shows). The Desktop prefix matches DesktopConfig, whose with_window_icon is its only consumer.

use frust::{DesktopConfig, MenuItemSpec, MenuRole, MenuSpec};

let file = MenuSpec::new()
    .with_item(MenuItemSpec::item("file.open", "Open…").with_accelerator("CmdOrCtrl+O"))
    .with_item(MenuItemSpec::separator())
    .with_item(MenuItemSpec::role(MenuRole::Quit));

let config = DesktopConfig::new()
    .with_app_name("Huddle")
    .with_app_id("dev.frust.huddle")
    .with_menu_spec(MenuSpec::new().with_item(MenuItemSpec::submenu("File", file)));

Desktop-only, unlike the menu_events read side: these types are defined in frust-shell-desktop, which is not in a mobile build’s or a wasm32 build’s dependency graph at all (see this crate’s Cargo.toml). Code shared with a mobile or wasm32 target keeps a DesktopConfig behind its own #[cfg(not(any(target_os = "android", target_os = "ios", target_arch = "wasm32")))] — or, more simply, writes it inline in app!’s desktop = { .. } argument, which the macro already emits only on the targets that have it. A native menu, as a platform-independent tree: the top-level value is the menu bar (whose items are conventionally MenuItemSpec::Submenus), and the same type describes each submenu below it.

Nothing here is rendered by Frust — a per-OS shell translates it into the host’s own menu API, and reports an activation back through frust_reactive::push_menu_event keyed by the activated item’s id.

Fields

items: Vec<MenuItemSpec>

The menu’s items, in display order.

Implementations

impl MenuSpec

pub fn new() -> MenuSpec

An empty menu.

pub fn with_item(self, item: MenuItemSpec) -> MenuSpec

Append one item, builder-style.

pub fn is_empty(&self) -> bool

Whether the menu has no items — a shell installs nothing at all rather than an empty menu bar.

Trait Implementations

impl Clone for MenuSpec

fn clone(&self) -> MenuSpec

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for MenuSpec

fn fmt(&self, f: &mut Formatter<'_>) -> Result<(), Error>

Formats the value using the given formatter.

impl Default for MenuSpec

fn default() -> MenuSpec

Returns the “default value” for a type.

impl Eq for MenuSpec

impl PartialEq for MenuSpec

fn eq(&self, other: &MenuSpec) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for MenuSpec