Replies: 2 comments 5 replies
-
In an ideal world we would have feature parity to make building UIs fluently beautiful. As you say it is a huge undertaking to do it, we have discussed whether we could make use of source generators to reduce that workload (no clue if it really does). I guess we hoped that we had built an initial set to get people building apps and then new requirements would slowly trickle in from the community. Are you able to share the common issues that you are creeping into in case there are things we could quickly achieve or even show you alternatives? |
Beta Was this translation helpful? Give feedback.
-
Closed and answered |
Beta Was this translation helpful? Give feedback.
-
Is it reasonable to hope/assume that eventually(?) it will be possible to recreate any XAML UI with the equivalent in C# using fluent syntax markup?
I've tried to convert a few things already and keep running into issues where there isn't a fluent method for a property and so I'm forced out of the simple fluent syntax and have to create a temporary variable so that I can assign other properties and then add that to a fluently defined collection or container.
I get I might be doing it wrong but this currently feels very incomplete as I'm frequently forced out of the fluent way of defining things.
Is having fluent ways of setting all properties something that makes sense?
I guess that it'd be a lot of work to have methods for ALL properties but before I even look at how much work that might be, I'm curious if this is even worth investigating.
Beta Was this translation helpful? Give feedback.
All reactions