Coming from a software engineering PoV it's refreshing to see someone actually following good coding practices in their youtube videoes. It's sadly more rare than common to stumble upon quality rather than quantity.
This seems much more robust and nicer. Is there anytime where a MVVM would not be ideal and instead utilize a different UI pattern? Like if most of my game uses MVVM would it be a stupid idea to make one component not utilize it? Im not sure if this is the type of pattern to apply foundation to all ui or just most of UI.
Thank you very much for this amazing video. This is pure gold. I am completely new to Unity and I had to watch it several times before I understand it all. Now, I see the power of the MVVM model and I better understand how we can leverage on your Custom Event System to make everything work. But there's still one point I don't fully get : In 7:15, you mentioned that the Event Data could be passed by another Model. Would you please expand on this point ? Thank you in advance.
Thanks! Glad you find it useful! The same way we told the slider or the text what to display, we could tell the button what value it holds (one solution). Another solution would be to just listen for the button and have another ViewModel or Model listen for the button and that Model knows the value. Here we took a shortcut to store logic data on the actual button.
Coming from a software engineering PoV it's refreshing to see someone actually following good coding practices in their youtube videoes. It's sadly more rare than common to stumble upon quality rather than quantity.
Thanks. Appreciate it!
I absolutely love these fully modular and scalable systems with little to no inheritance and I'm all for more videos like this
Alright! 😃
finally made it through a follow along with the 3 tutorials, super dense but packed full of great info. Time to integrate into my game!
Nice! Glad it’s helpful! Yes it’s packed, future tutorials will be a bit lighter ^^
That was awesome. Really great job. You have a talent for clarity. Appreciate it.
Thanks! Happy it works!
I have also been fully converted to the event based workflow, it's wonderful, still need to get better at using scriptable objects though
This seems much more robust and nicer. Is there anytime where a MVVM would not be ideal and instead utilize a different UI pattern? Like if most of my game uses MVVM would it be a stupid idea to make one component not utilize it? Im not sure if this is the type of pattern to apply foundation to all ui or just most of UI.
For most if the traditional UI, this is nice. For specific Gameplay UI, maybe you need a more direct MVC approach sometimes.
Thank you very much for this amazing video. This is pure gold. I am completely new to Unity and I had to watch it several times before I understand it all. Now, I see the power of the MVVM model and I better understand how we can leverage on your Custom Event System to make everything work. But there's still one point I don't fully get :
In 7:15, you mentioned that the Event Data could be passed by another Model. Would you please expand on this point ? Thank you in advance.
Thanks! Glad you find it useful!
The same way we told the slider or the text what to display, we could tell the button what value it holds (one solution). Another solution would be to just listen for the button and have another ViewModel or Model listen for the button and that Model knows the value.
Here we took a shortcut to store logic data on the actual button.
Thanks a lot for your quick reply ! Much appreciated ! Can't wait for the next video@@this-is-gamedev
My only complaint is your capitulation to the peanut gallery. In your video about MVVM, you use the singleton ThemeManager. Seems wrong.
:D Can be changed to an SO and this will then be consistent with the rest
Thank you for the information 🫡