-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a MAUI target #747
Comments
Yes, absolutely. For the time being, I don't think we can do anything about it. MAUI is currently a clone of Xamarin.Forms, and I'm guessing a lot will change until the targeted release of November 2021. Regarding the "single project - several platforms", I'm hoping the F# tooling in the various IDEs will follow the C# tooling because that will be the major blocking point for a Fabulous.MAUI. Aside from that, Fabulous is mostly reading to accept a new framework like this one. |
An interesting link showing what MAUI could be: dotnet/maui#28 |
Excited to see how this could influence Fabulous!! Maybe Fabulous could shift away from having to just clone wrapping forms elements? Go a bit more in the direction of Comet and having it's own syntax. |
@PureWeen It will be interesting to see what this restructuring will enable! Comet seems to share a lot of similarities with Fabulous, except that Fabulous don't provide its own abstraction over what a control is. Comet is a lot like Xamarin.Forms on this point. So, depending on the actual implementation of MAUI, I think Fabulous will still need to clone wrap the various controls so we can provide our own syntax and diffing logic, while not having to reimplement all the platform renderers. |
Interesting, it seems that peoples are pretty sure that fabulous will implement MAUI. dotnet/maui#115 (comment) |
Have any decisions been made on whether or not we are getting MAUI support in Fabulous? |
@JustinWick Fabulous will support MAUI. You can see the progress here https://github.com/TimLariviere/Fabulous-new Once we figure out everything, I hope to make a compatibility layer to more easily migrate from Fabulous v1 to v2. Anyway we're still at a very early stage. If you want some insights on Fabulous v2: |
@TimLariviere That is fantastic news! |
@TimLariviere .NET MAUI RC2 is released now ; How much work would it take to plug Faboulus on it ? |
@JbmOnGitHub Plugging a new framework to Fabulous is pretty straightforward. It's mainly about writing wrappers for the new framework to be usable in the view function. This is time consuming but fairly easy to do. With MAUI though, there is a difficulty to solve first. Once it's done, we will be able to start adding wrappers to all controls and we will release preview versions of |
@TimLariviere The fabulousfx/FSharp.Mobile.Templates Readme lists MAUI already as a target. Does this indicate that one can build Fabulous apps with MAUI already, or has it only been added for future use? When I try to compile the MAUI project I get:
|
@ChristophSchmidpeter You can't use Fabulous with Maui yet. Regarding the error you're seeing, it has been reported here: fabulous-dev/FSharp.Mobile.Templates#21 |
@TimLariviere Thank you for the info and great to hear that support is already underway :) |
Maui is now supported. Please see https://github.com/fabulous-dev/Fabulous.MauiControls |
It is the next evolution of Xamarin.Forms targetting all of .NET. https://github.com/dotnet/maui
We should investigate before the .NET 6 release on how to support it.
The text was updated successfully, but these errors were encountered: