[PATCH yew-widget-toolkit v2] widget: add 'div' macro

[PATCH yew-widget-toolkit v2] widget: add 'div' macro

[Dominik Csapak]

this is just a simple wrapper around the `Container` widget, but it's
very useful in situations where bare strings are used in a flex layout,
since e.g. a `Row` with multiple children that are all strings won't get
a proper flex layout (since they're not elements)

So instead of writing
```
Row::new()
    .with_child(Container::new().with_child("Text1"))
    .with_child(Container::new().with_child("Text2"))
```

one can now write
```
Row::new()
    .with_child(div!("Text1"))
    .with_child(div!("Text2"))
```

which is much shorter and more readable.

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
changes in v2:
used the correct use statement in the prelude section

 src/lib.rs           |  1 +
 src/widget/macros.rs | 34 ++++++++++++++++++++++++++++++++++
 src/widget/mod.rs    |  2 ++
 3 files changed, 37 insertions(+)
 create mode 100644 src/widget/macros.rs

diff --git a/src/lib.rs b/src/lib.rs
index d3ac6ea..a759350 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -358,6 +358,7 @@ pub mod prelude {
     #[doc(hidden)]
     pub use yew::prelude::*;
 
+    pub use crate::div;
     pub use crate::props::CallbackMutScopeExt;
     pub use crate::props::ContainerBuilder;
     pub use crate::props::CssBorderBuilder;
diff --git a/src/widget/macros.rs b/src/widget/macros.rs
new file mode 100644
index 0000000..fc4e05f
--- /dev/null
+++ b/src/widget/macros.rs
@@ -0,0 +1,34 @@
+//! Helper and utility macros to make some often used patterns more ergonomic
+
+/// A macro to wrap some elements or strings in a `<div>`.
+///
+/// Expands to `Container::new().with_child(param1).with_child(param2)...`
+///
+/// Examples:
+/// ```
+/// # use pwt::widget::Container;
+/// # use pwt::div;
+///   // must be used, either directly or via pwt::prelude::*
+///   use pwt::props::ContainerBuilder;
+///
+/// # fn main() {
+///   let div = div!("Some Text");
+/// # drop(div);
+///
+///   // is the same as
+///   let div = Container::new().with_child("Some Text");
+/// # drop(div);
+///
+///   // you can also specify multiple elements
+///   div!("Text1", "Text2");
+///
+///   // or components
+///   div!(Container::new());
+/// # }
+/// ```
+#[macro_export]
+macro_rules! div {
+    ($($arg:expr),* $(,)?) => {
+        $crate::widget::Container::new()$(.with_child($arg))*
+    };
+}
diff --git a/src/widget/mod.rs b/src/widget/mod.rs
index 0df2cbf..1998332 100644
--- a/src/widget/mod.rs
+++ b/src/widget/mod.rs
@@ -85,6 +85,8 @@ pub use list::{List, ListTile, ListTileObserver};
 #[doc(hidden)]
 pub use list::{PwtList, PwtListTileObserver};
 
+pub mod macros;
+
 mod mask;
 pub use mask::Mask;
 #[doc(hidden)]
-- 
2.47.3

Re: [PATCH yew-widget-toolkit v2] widget: add 'div' macro

[Thomas Lamprecht]

On 02/04/2026 15:43, Dominik Csapak wrote:
> this is just a simple wrapper around the `Container` widget, but it's
> very useful in situations where bare strings are used in a flex layout,
> since e.g. a `Row` with multiple children that are all strings won't get
> a proper flex layout (since they're not elements)
> 
> So instead of writing
> ```
> Row::new()
>     .with_child(Container::new().with_child("Text1"))
>     .with_child(Container::new().with_child("Text2"))
> ```
> 
> one can now write
> ```
> Row::new()
>     .with_child(div!("Text1"))
>     .with_child(div!("Text2"))
> ```
> 
> which is much shorter and more readable.

Yes, but why a macro and not a normal method for this? Macro's are a bit
opaque, totally fine if there is a benefit for adding them, but here I
cannot see a big blocker against adding an e.g. TextContainer wrapper or
an Container::new_with_text (might need better naming, but just to relay
the idea), especially if that's your main use case. Or for a more generic
use case we could add a "Container::new_with_child" constructor or also
a wrapper type (SimpleContainer::new(child)).

And it isn't exactly a plain div, as then one could just use the html!
macro from yew, so the name as is, is IMO not totally ideal. If we go
the macro way (what's Dietmars opinion on this?), I'd favor to call it
container! to better reflect that it uses the pwt container class.