Family - Text

This page unifies related iced::widget APIs for the Text family.

# API surfaces

• Module: iced::widget::text
• Constructor: iced::widget::text

# Surface summaries

# Module

Draw and interact with text.

# Constructor

Creates a new Text widget with the provided content.

# Verified constructor signature

pub fn text<'a, Theme, Renderer>(
    text: impl IntoFragment<'a>,
) -> Text<'a, Theme, Renderer>
where
    Theme: Catalog + 'a,
    Renderer: Renderer,

# Example References

• ref/examples/clock/src/main.rs
• ref/examples/custom_shader/src/scene/camera.rs
• ref/examples/custom_shader/src/scene/pipeline.rs
• ref/examples/editor/src/main.rs
• ref/examples/stopwatch/src/main.rs
• ref/examples/tooltip/src/main.rs

# Inline Examples (from rustdoc)

# Constructor example

use iced::widget::text;
use iced::color;

enum Message {
    // ...
}

fn view(state: &State) -> Element<'_, Message> {
    text("Hello, this is iced!")
        .size(20)
        .color(color!(0x0000ff))
        .into()
}

# Related

• Families
• Modules
• Constructors
• Elements

# Use this when...

• You want one page that links module, constructor, and element surfaces.
• You are deciding which API surface to start from.
• You need a practical map for this widget domain.

# Minimal example

// Typical flow:
// 1) Start with constructor usage.
// 2) Move to module docs for style/state details.
// 3) Use element docs for type-level control.

# How it works

Family pages connect related docs so you do not miss capabilities that are split across constructor/module/element pages.

# Common patterns

// Build with constructor APIs first,
// then refine behavior/styles through related module and element docs.

# Gotchas / tips

• Family routes normalize naming; module/function/struct names may differ slightly.
• Prefer this page as your entrypoint when learning unfamiliar widgets.
• Follow example references here before inventing integration patterns.