Unity Dev tries .NET MAUI
ฝัง
- เผยแพร่เมื่อ 19 ก.ย. 2023
- Hi everyone. This video is more of a focused tutorial. I'm exploring alternatives to Unity for simple games and general app development. So I'm trying out .NET MAUI.
Here is a link to the GitHub repo: github.com/dotnet/maui
For most apps using MAUI, using the MVVM pattern is generally the recommended choice instead of having code inside event handlers. It helps decouple data from the UI with automatic updates when the data changes, but requires more ceremony to set up.
Thanks for the info!
I've worked on an app with Avalonia UI and MVVM(guess not a good implementation though).
Im curious what you mean that you wouldnt use event handler for button events.
How else would other elements be notified, even with MVVM?
@@ZeroSleapButtons (and most controls) in .NET MAUI have a Command property that binds to an ICommand implementation in your view model, and then in your view model you define a function to call when the command is invoked. Completely removes the need for event handlers in your .xaml.cs files.
@@ZeroSleap You use binding.
You bind Button's Command property to command in view model.
To notify View about view model changes you implement INotifyPropertyChanged interface in view model.
@@Soularchitector Ah damn i totally forgot about that.
Been some months since i last did an app with mvvm.
Thanks!
This was a pleasant surprise! Pretty neat little engine, albeit for a niche use-case.
please don't use your niece
@@aqlord Lol. Niche! I meant niche!
Love your content, man. As a fellow Unity developer, I'm considering Godot or Unreal. It's very sad what Unity has done.
+1 sub, keep it up
Try Monogame instead of Godot.
Once you get several engines under your belt along the course of this series, I think it would be interesting to see a two-part on making the same game across all the engines you use - one part for 3D, one part for 2D.
I don't mean the same concept and similar mechanics, I've seen that done before, I mean same assets, same mechanics, everything as close as it can get to being 1-1 except for the language the scripting is written in, with the work you spent with each editor on screen at the same time, possibly including a timer as well, so the viewer can see where each editor was strong and where they were weak in the process, alongside clarifications about what you liked, what you didn't, where you struggled, the bits that confused you, etc. about each engine.
That would be an incredible comparison between the flexibility, workflow style, workflow efficiency, and end user performance between a huge number of engines, perhaps the most 1:1 direct comparison even possible not only when comparing dev workflow, but actual final product performance (and possibly stability).
I'm really enjoying the series so far, and hope you keep finding and/or thinking of new engines to toy with.
Inspiring video. Thanks you!
Great video! Have all the engagement!
Hey, I like this series. Do you think you could cover some of those C# frameworks like MonoGame and FNA.
Stride/Flax rather than FNA. FNA is mostly for porting XNA, so not really focused on new projects if I'm not mistaken. Flax is worth a look though if you have time :)
Yep, Yep, I agree! If you google ".NET game engines", Microsoft has a list of all of them. So maybe a TH-cam series to determine which of those are worth considering for Unity developers. MonoGame, Stride, Evergine, Unigine, Flax. What are the pros and cons. And maybe judge them based on some categories that are important. Business model, export platforms, 2D and 3D support, do they support modern graphics APIs (vulkan, dx12, metal), is it production ready, are they user friendly, do they force you to show the splash screen. That kind of stuff. And then the final verdict.
This reminds me very much of WPF, which was also quite neat
nice. I'm making UI heavy stuff now and found this interesting. Nice to be in a C# environment like that but i scare i will bump into things i just can't do but want to do down the line like more involved animations etc. For now, i lean towards Godot. Had a look at Stride and found it interesting but too immature on the UI side of things IMO. My reason for not committing to Godot yet is no IOS ports with C# at this point in time. They say on the blog that android can be done (with some patches to Mono ... ) but no IOS is a bit of a bummer. So i keep looking for alternatives
i am still very cautious with maui because xamarin was such a mess and maui is basically xamarin evolved. Currently using flutter for my personal apps (no games) and i am very happy. The fact that flutter draws its self maybe could make it more flexible if you create your own controls ( i have never done this so dont know how difficult this is)
All the CSS talk got me thinking how centering actually worked... been a while since I've done anything with CSS.
I think something like this worked:
.RandomDIV {
position: absolute;
top: 50%;
left: 50%;
height: 25%;
width: 35%;
transform: translate(-50%, -50%);
}
not sure if someone said it already but as someone who has used XAML the "x:Name" is optional
you could easily have typed *Name = ""* and got the same result
XAMLs great for desktop application development. For the most part.
Hopefully more people will get introduced to it now. They have tried thriceish already and its not really caught on but its a really good idea and works really well for a broad range of applications.
Gaming ... not really one but for a gain that doesn't involved custom drawing yeah its perfect.
re the question: I have not tried MAUI but its building ontop of tried and testing tech both with WPF and Xamarin so its probably going to be more mature out the gates than most frameworks.
Do a series on ue5 !
Unreal engine looks really easy for sure, the same way i organize tasks in my C# codes, is just the same things are did in unreal
i'll try learning godot as well, i'd like to become a cross-engine plugins developpers
Personally I prefer Unreal simply because it's here since a long time, so it means more features, a lot of tutorials, documentation, etc...
Godot is an engine I keep an eye on, I think it has a bright future.
Try Monogame instead of Unreal.
If you plan on making primarily 2D content, stay away from Unreal. Unreal is primarily a 3D engine and in no way facilitates the creation of 2D content like Unity does. While you can create 2D stuff with it, it's gonna be a miserable experience all the way through.
@@BrunodeSouzaLino I know, this is why I use Unreal, bcs I make only 3D contents !
Another engine you might want to look into: FNA, the XNA reimplementation library.
I wanna see how MAUI stacks up vs Avalonia UI for example.
Personal experience: Avalonia is years ahead of MAUI in every single aspect.
I'm currently porting a MAUI project I have to Avalonia, since MAUI doesn't support Linux out of the box... but even global styling, custom Controls, the support for realtime visualization of Controls and Views inside the IDE and the fact that it comes with ReactiveUI or MVVM toolkit (yes, you can install this apart for MAUI, but it already comes with Avalonia projects)
And OMG! The Avalonia Dev Debug Tools is AMAZING!🔥
All around a great tool.
try Unigine engine. There is c# api and components
Try Flax Engine next time!
You should know almost all MS efforts in this area get deprecated/abandoned very quickly. Anyone reading this remember "I told you so".
I mean no they dont. They just dont tend to get much support from devs for some reason.
Win forms was shit and lasted almost 10 years. Silverlight was ... not the one. WPF is actually pretty good and 16 years and still going strong. Xamarin especially Forms was a mixed bag and mostly a half assed community attempt at what MAUI is. MAUI might also be pretty good.
So yeah they last 10ish years which is not exactly quickly Unity has only been around for 20ish years and if things keep going the way they are wont last much longer.