Klarth
Klarth
CC#
Created by jjsutton on 2/19/2025 in #help
Struggling to setup Bindings dynamically for my UserControl (WPF TextBox)
new FrameworkPropertyMetadata("", FrameworkPropertyMetadataOptions.BindsTwoWayByDefault) or something close.
9 replies
CC#
Created by jjsutton on 2/19/2025 in #help
Struggling to setup Bindings dynamically for my UserControl (WPF TextBox)
No description
9 replies
CC#
Created by jjsutton on 2/19/2025 in #help
Struggling to setup Bindings dynamically for my UserControl (WPF TextBox)
No description
9 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Most of them are 1:1 with System.Reactive though there are some new operators, too.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Well, once each input stream has pushed at least one item.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
And you'll see it emits a new item (containing the latest value of each input) each time one of the input streams pushes a new item.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Like if you don't understand what CombineLatest does, you can always look at https://github.com/Cysharp/R3/blob/main/tests/R3.Tests/OperatorTests/CombineLatestTest.cs
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
The unit tests seem really clean and concise. Which helps understanding how certain features work.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Yeah, observables are awkward. I need to invest time into R3 basics at some point. Largely same thing, but different implementation. https://github.com/Cysharp/R3
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
I assume the pattern can be smarter with pooling (and the limitations that would come from that) and make MVU reasonable with said enforced pattern. But that's a lot of invested time. Time that I prefer the pattern architect to put in, not me.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Not entirely related, but Avalonia allows you to bind directly to observables. Though it's still a one-way road.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
No idea. I saw the pattern and I'm not willing to put real time behind unproven stuff in .NET, especially if it has obvious flaws (object churn).
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
In case you need inspiration. I still personally just don't like it. 🤷‍♂️
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Well, the Avalonia PropertyStore (system which manages bindings, setter priorities, etc) is built around observables. So you can do a lot with reactive programming.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Of course, other XAML frameworks aren't implemented as native, so you only get part of those benefits.
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
Well fine then Modix, embed the whole thing. :harold:
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
39 replies
CC#
Created by MechWarrior99 on 1/18/2025 in #help
Would a Declarative Reactive UI be too expensive?
So if you're using UWP (or presumably WinUI3), then there are a lot of perf improvements you're losing by moving your UI into C#.
39 replies