You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 31, 2021. It is now read-only.
I read your fsharp-wpf-mvc-series and you actually have got Mvc.Compose methods in this library as well, and all works fine for composition, but what about interoperability?
Maybe I am wrong but in your samples I could not find any example of such interoperability. In C# projects we use Event Aggregators, how could I achieve similar feature in FSharp.Desktop.UI?
Controllers encapsulate operations pipelined by events associated with views. In interoperability among different modules/views basically controllers already implement operations which are required in interoperability operation.
What are your thoughts? Some kind of EventAggregator or similar like in your controller approach some kind of event translator and controller/model selector?
I read your fsharp-wpf-mvc-series and you actually have got Mvc.Compose methods in this library as well, and all works fine for composition, but what about interoperability?
Maybe I am wrong but in your samples I could not find any example of such interoperability. In C# projects we use Event Aggregators, how could I achieve similar feature in FSharp.Desktop.UI?
Controllers encapsulate operations pipelined by events associated with views. In interoperability among different modules/views basically controllers already implement operations which are required in interoperability operation.
What are your thoughts? Some kind of EventAggregator or similar like in your controller approach some kind of event translator and controller/model selector?