From: Dominik Csapak <d.csapak@proxmox.com>
To: yew-devel@lists.proxmox.com
Subject: [yew-devel] [RFC yew-comp/yew-widget-toolkit 0/4] make RenderFn's return type generic
Date: Wed, 10 Dec 2025 11:48:47 +0100 [thread overview]
Message-ID: <20251210104856.1698157-1-d.csapak@proxmox.com> (raw)
This series changes the RenderFn type to have a generic return type, which can replace our TextRenderFn
and allows us to do more things with it.
I send this as a preparation for some cleanups I want to do, but for those
to work better, we need this way of defining RenderFn.
Sending as RFC, since I'm not fully convinced this is a good idea,
especially extending the builder_cb macro this way, but I could not come
up with something better.
The first patch in pwt is just updating the tests to new rustc output,
can be applied independently, but is necessary to let the tests
run currently.
proxmox-yew-widget-toolkit:
Dominik Csapak (3):
pwt-macros: update tests to work for newer rustc
pwt-macros: builder: allow multiple generic types in callback variant
props: make RenderFn's return type generic
pwt-macros/src/builder.rs | 19 ++++-
pwt-macros/tests/builder/invalid_type.stderr | 2 +-
pwt-macros/tests/widget/wrong_crate.stderr | 6 +-
src/props/mod.rs | 5 +-
src/props/render_function.rs | 81 +++-----------------
src/touch/material_app.rs | 10 +--
src/widget/catalog_loader.rs | 6 +-
src/widget/desktop_app.rs | 6 +-
src/widget/meter.rs | 6 +-
src/widget/theme_loader.rs | 6 +-
10 files changed, 50 insertions(+), 97 deletions(-)
proxmox-yew-comp:
Dominik Csapak (1):
rrd: replace TextRenderFn with new generic RenderFn
src/rrd/graph.rs | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Summary over all repositories:
11 files changed, 54 insertions(+), 101 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
yew-devel mailing list
yew-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/yew-devel
next reply other threads:[~2025-12-10 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 10:48 Dominik Csapak [this message]
2025-12-10 10:48 ` [yew-devel] [PATCH yew-widget-toolkit 1/3] pwt-macros: update tests to work for newer rustc Dominik Csapak
2025-12-10 10:48 ` [yew-devel] [PATCH yew-widget-toolkit 2/3] pwt-macros: builder: allow multiple generic types in callback variant Dominik Csapak
2025-12-10 10:48 ` [yew-devel] [PATCH yew-widget-toolkit 3/3] props: make RenderFn's return type generic Dominik Csapak
2025-12-10 10:48 ` [yew-devel] [PATCH yew-comp 1/1] rrd: replace TextRenderFn with new generic RenderFn Dominik Csapak
2025-12-11 9:35 ` [yew-devel] applied: [RFC yew-comp/yew-widget-toolkit 0/4] make RenderFn's return type generic Dietmar Maurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251210104856.1698157-1-d.csapak@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=yew-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox