[rafram]

Not text editing context menus like any native app.

As I said, Iced looks awesome. But it's also, as you said, experimental. Using an experimental library for a DE could be a huge mistake, no matter how promising the roadmap is. Ideally you'd wait for the project to ship some of the non-negotiable things on the roadmap (accessibility, system menus, RTL text, keyboard navigation...) before tying your fortunes to it.

[airstrike]

I think native context menus are out of scope for iced and probably to be addressed upstream by winit. patches welcome.

at the risk of sounding like a fanboy, I encourage you to try to use iced as a library first to see how powerful it is in terms of performance, ergonomics and overall just the quality of its design. hecrj is a prolific coder and I'm confident I'm not alone in this assessment. I'm pretty bullish on the path ahead for the library given those fundamentals, and I can't speak for the COSMIC team but I imagine that assessment probably overlaps with theirs.

[rafram]

I mean text editing context menus (right-click a text field -> Undo, Redo, Cut, Copy, Paste). Iced, or at least Halloy, doesn't have those at all.

[airstrike]

You can definitely implement all of that in iced. The `text_editor` widget offers cut, copy, paste off-the-shelf and undo/redo would be a matter of keeping a stack of the "input changed" messages and popping off changes to undo/redo them.

The library is pretty low level so there's a bit of legwork that the developer needs to do in order to implement things that you get for free in, say, a browser. It's a tradeoff, but I think one that tends to provide more advantages than disadvantages.