Struct ymc::top_app_bar::TopAppBar

pub struct TopAppBar { /* fields omitted */ }

The top-app-bar component

Documentation

Trait Implementations

impl Component for TopAppBar

type Message = Msg

Messages are used to make Components dynamic and interactive. Simple Component’s can declare their Message type to be (). Complex Component’s commonly use an enum to declare multiple Message types.

type Properties = TopAppBarProps

Properties are the inputs to a Component and should not mutated within a Component. They are passed to a Component using a JSX-style syntax.

fn create(props: Self::Properties, link: ComponentLink<Self>) -> Self

Components are created with their properties as well as a ComponentLink which can be used to send messages and create callbacks for triggering updates.

fn update(&mut self, msg: Self::Message) -> ShouldRender

Components handle messages in their update method and commonly use this method to update their state and (optionally) re-render themselves.

fn change(&mut self, props: Self::Properties) -> bool

When the parent of a Component is re-rendered, it will either be re-created or receive new properties in the change lifecycle method. Component’s can choose to re-render if the new properties are different than the previously received properties. Most Component’s will use props with a PartialEq impl and will be implemented like this:

fn view(&self) -> Html

Components define their visual layout using a JSX-style syntax through the use of the html! procedural macro. The full guide to using the macro can be found in Yew’s documentation.

fn rendered(&mut self, first_render: bool)

The rendered method is called after each time a Component is rendered but before the browser updates the page.

pub fn destroy(&mut self)

The destroy method is called right before a Component is unmounted.