Hello!
I came across this repo while doing research for a hobby project of mine. I meant to revive the Xamarin.Flutter project and continue working on it at least to make enough improvements to the Dart -> C# transpiler useful as a base for hand-porting the flutter framework to C#.
The original Xamarin.Flutter project was abandoned by its original author @adamped, so my fork here represents the latest code. I've only had time to fix a few bugs in the transpiler so far:
https://github.com/JeroMiya/xamarin.flutter
I'd love to join forces and collaborate on this project, though my goal for Xamarin.Flutter was to get a working version of the UI framework in a Xamarin application, as opposed to a Unity one. One problem I would have using your code as a base for a Xamarin compatible rendering engine outside of Unity is licensing. Looks like you're using a Unity specific license (maybe that's required for third party Unity plugins/scripts?). If so, I was wondering if you'd be able to separate out the core library (making it a .net standard class library with no Unity dependencies) from the Unity specific rendering pieces, and then relicense that core framework code using the same license as Flutter? You could still license the Unity specific parts with the Unity license as needed of course. This would allow me to use your core code as a base and add the Xamarin code to get it working outside of Unity.
I'm working on the project as a hobby, so progress is slow, but let me know if we can collaborate. I'm not confident the Dart-to-C# transpiler will ever be able to transpile Dart code 100% of the time correctly (I think a Dart-to-CIL compiler backend would have better luck, if I had the skillset). My goal was always to get it to transpile about 80-90% of the flutter code correctly to make the hand-porting process easier, especially as new versions of Flutter come out. However, if I could work together with a common core framework using your hand-ported code as a base, I could refocus my efforts on a Xamarin compatible rendering engine, and I think this would result in a working Flutter implementation for Xamarin MUCH earlier!
Hello! I came across this repo while doing research for a hobby project of mine. I meant to revive the Xamarin.Flutter project and continue working on it at least to make enough improvements to the Dart -> C# transpiler useful as a base for hand-porting the flutter framework to C#.
The original Xamarin.Flutter project was abandoned by its original author @adamped, so my fork here represents the latest code. I've only had time to fix a few bugs in the transpiler so far: https://github.com/JeroMiya/xamarin.flutter
You mentioned looking into the project in this issue and noticing it was abandoned: https://github.com/UnityTech/UIWidgets/issues/318
I'd love to join forces and collaborate on this project, though my goal for Xamarin.Flutter was to get a working version of the UI framework in a Xamarin application, as opposed to a Unity one. One problem I would have using your code as a base for a Xamarin compatible rendering engine outside of Unity is licensing. Looks like you're using a Unity specific license (maybe that's required for third party Unity plugins/scripts?). If so, I was wondering if you'd be able to separate out the core library (making it a .net standard class library with no Unity dependencies) from the Unity specific rendering pieces, and then relicense that core framework code using the same license as Flutter? You could still license the Unity specific parts with the Unity license as needed of course. This would allow me to use your core code as a base and add the Xamarin code to get it working outside of Unity.
I'm working on the project as a hobby, so progress is slow, but let me know if we can collaborate. I'm not confident the Dart-to-C# transpiler will ever be able to transpile Dart code 100% of the time correctly (I think a Dart-to-CIL compiler backend would have better luck, if I had the skillset). My goal was always to get it to transpile about 80-90% of the flutter code correctly to make the hand-porting process easier, especially as new versions of Flutter come out. However, if I could work together with a common core framework using your hand-ported code as a base, I could refocus my efforts on a Xamarin compatible rendering engine, and I think this would result in a working Flutter implementation for Xamarin MUCH earlier!