Moving primary Morphir development to morphir-dotnet #165
DamianReeves
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
@stephengoldbaum , @AttilaMihaly , @psmulovics ... have you all had a chance to look at the above. This is far from an exhaustive list. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Within the Morphir project we have expressed a desire to expand Morphir to other platforms, including:
There has been quite a bit of discussion around how we can have one central repository from which we target other platforms. The attached PDF represents the proposal I gave for using .NET, F#, and Fable during our Biweekly meeting on April 6, 2023.
We will use this thread both for discussion and to organize our thoughts on next steps and an action plan to execute on.
Morphir With Dotnet.pdf
In order to move the work here we need to port parts of
morphir-elm
but we also will want to add some other things. Here is a list of some things I think we should tackle and/or explore:morphir-dotnet
without needing to rewrite to start, using WASM also means we have no dependency on NodeFootnotes
https://moiraesoftware.github.io/myriad/ ↩
https://sleepyfran.github.io/blog/posts/fsharp/ce-in-fsharp/ ↩
Beta Was this translation helpful? Give feedback.
All reactions