Agreed! BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@Eugene.Berezin
4 жыл бұрын
How about binding? One of the benefits of MVVM that you can create binding and update your view reactively.
@rebeloper
4 жыл бұрын
Best comment on this video :) I just did not have the time to explain bindings. Reactive programming may be confusing for starters :) BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@captainmichaelj2321
3 жыл бұрын
Exactly the tutorial I was looking for, thanks so much for the great video :)
@rebeloper
3 жыл бұрын
You're very welcome! BTW what do you think of my latest video on Flexible Header in SwiftUI: kzitem.info/news/bejne/tZeCp2eQe51njaQ
@casadogaspar
2 жыл бұрын
This is the best explanation I ever saw about the theme. Make it so simple for beginners understand it by comparison.
@rebeloper
2 жыл бұрын
Glad it helped. MVC and MVVM can be tricky to understand. BTW now you can have a Slide in Menu easily in SwiftUI: kzitem.info/news/bejne/mo2BvIx-oHd3iG0
@samuelpmilanez
4 жыл бұрын
Thanks for the video. I will integrate a new project and the architecture is Clean MVVM; your video was amazing for my compreension.
@rebeloper
4 жыл бұрын
Glad it was helpful! If you liked this video you will love *Swift Encryption with Crypto Manager* : kzitem.info/news/bejne/sXmBt2p-kXt3omk
@SourovDattacse
4 жыл бұрын
Thanks for your video. However, I did not understand the separation of concern using a view model. Getting Puzzled
@rebeloper
4 жыл бұрын
Short story: make sure that your views only display, your controller only controls the views and everything else is moved out of them. It may be confusing at first, but practice makes perfect. BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@cagriporti
3 жыл бұрын
Thanks for the explanation!
@rebeloper
3 жыл бұрын
No problem! BTW do you like the Previews in SwiftUI? Find out everything you have to know about Previews here: kzitem.info/news/bejne/066c2pmomKl-i34
@jhngolan
3 жыл бұрын
I already implemented MMVM architecture in Java MVVM hopefully can implemented it in IOS Swift after knowing detail of Xcode, newcomer in Apple Gadget , thank you Mr for the nice explanation
@rebeloper
3 жыл бұрын
You are welcome, Johan! BTW if you liked this video you will love my newest tutorial *Google Maps Swift: How to Implement Google Map in iOS* kzitem.info/news/bejne/sXyiuqV7a5Wcmn4
@MrBrunomalo1
3 жыл бұрын
In your example, is not the same thing that create a utility class wich receive a skillLevel and return a levelname ?
@rebeloper
3 жыл бұрын
Yes, classes are also okay. If you enjoyed this video I suggest taking a look at Fira Code: kzitem.info/news/bejne/x4uhn5yChYKnpKQ
@BigCarso
3 жыл бұрын
Where did you get this definition of MVVM from? It seems quite different to the original idea from windows
@rebeloper
3 жыл бұрын
Don't really know where from, it's just is in the iOS community. BTW if you did like this video I think you will enjoy "How to Publish an App to the App Store": kzitem.info/news/bejne/2qGfqmmtqqmEmGk
@BigCarso
3 жыл бұрын
Hmm I think your example was too simple to really show the benefit of MVVM. Without databinding or the mediator pattern all you have is a simple mapping function.
@indomitabletr1834
Жыл бұрын
Sir, can you add also MVP and VIPER architectures?
@rebeloper
Жыл бұрын
Noted. Till than take a look at my lates video about 30 Xcode Keyboard Shortcuts You NEED to Know: kzitem.info/news/bejne/pI2grn1pr4x9hqA
@mohamednidhalmrad1228
3 жыл бұрын
Thanks for your video. ✅ 1/but when we have logic in cell and in its viewController. we one ViewModel contains all the logic or create one for the cell and another for viewController. "/ when we have for example three viewController that contains the three steps of creating something. we make one ViewModel instantiated in each ViewController or we make three different ViewModels class (first ViewModel, second view model, their ViewModel)
@rebeloper
3 жыл бұрын
I would go with one view model moved through the 3 view controllers. BTW if you enjoyed this tutorial make sure you take a look at my latest video about Progress Indicator Examples: kzitem.info/news/bejne/z36omJyeZn2Yh6A
@ОлесяУкраинская-т1д
4 жыл бұрын
Cool video!Thx!
@rebeloper
4 жыл бұрын
Glad you liked it! BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@urbanmavericksg
2 жыл бұрын
good explanation
@rebeloper
2 жыл бұрын
Thanks and welcome! Making MONEY just got EASIER on the App Store (and you didn't even know it!) 👉 kzitem.info/news/bejne/mHeMvmiocZuHYKA
@abdullahshahid6637
Жыл бұрын
But what is Clean Architecture?
@rebeloper
Жыл бұрын
Sorry the video did not give you an answer.
@alexzvarich
4 жыл бұрын
Amazing!
@rebeloper
4 жыл бұрын
Thank you! Cheers! BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@davidnitzsche-bell5418
3 жыл бұрын
10:10 couldn't you just create computed properties, name and level, in the model and put the logic in there? Then, for both the MVC and the MVVM, filling in the TableViewCell would be the same two lines.
@rebeloper
3 жыл бұрын
Yes, but I would not be talking about MVVM. BTW if you did like this video make sure to take a look at how to create a MEME generator in SwiftUI: kzitem.info/news/bejne/sq-ut2pobYx-bGk
@davidnitzsche-bell5418
3 жыл бұрын
@@rebeloper Thank you for answering. Let me rephrase.... I'd like to see a case where MVVM would be 'required' or noticeably better; a case where using computed properties simply wouldn't work. I ask because I'm still trying to really understand the difference between the "C" in MVC and the "VM" in MVVM. So far, no video I've seen really does that.
@kishannakum104
4 жыл бұрын
💥💥💥💥
@rebeloper
4 жыл бұрын
💥💥💥💥 indeed! BTW check out my latest video about building your very own *Custom Frameworks in Swift* : .kzitem.info/news/bejne/0JCi1X2pf2N5Z5w
@abelhancco4349
Жыл бұрын
nice
@rebeloper
Жыл бұрын
Thanks, Abel. Here's the easiest realtime app I’ve ever built 👇 kzitem.info/news/bejne/1Xx3mWSmaqmQqYY
@Neographic84
3 жыл бұрын
Rebeloper thanks always for your tutorials they are very clear and help the whole community a lot! Thank you! I need help .. I have a struct struct TimeSelModel { let hour: String let minute: String } ------------------------------------------------------ I recover data this way because I need to view some data in section 0 of my collectionview and other data in section 1 struct TimeSelData { static func dataSec (section: Int, _ completion: @escaping (Result ) -> ()) { if section == 0 {completion (.success (dataSec0))} else {completion (.success (dataSec1))} } } let dataSec0 = [ TimeSelModel (hour: "09", minute: ": 30"), TimeSelModel (hour: "17", minute: ": 00") ] let dataSec1 = [ TimeSelModel (hour: "12", minute: ": 00"), TimeSelModel (hour: "19", minute: ": 00") ] --------------------------------------------------------------- I use the data this way inside my controller private var section: Int = 0 var data: [TimeSelModel] = [] private func fetchData () -> Void { TimeSelData.dataSec (section: section) {(result) in switch result { case.success (let data): self.data = date case.failure (let error): print (error.localizedDescription) } } } func collectionView (_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int { self.section = section return data.count} func collectionView (_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell { let cell = collectionView.dequeueReusableCell (withReuseIdentifier: TimeSelCell.cellID, for: indexPath) as! TimeSelCell cell.dataModel = data [indexPath.item] return cell } It doesn't work I don't get the right data for the sections of my collectionView .. Using your example in your tutorial how can I achieve my goal of displaying different data for 2 different sections of a collectionView?
@rebeloper
3 жыл бұрын
Explaining this in a comment is hard. I can help you in a mentoring session: rebeloper.com/mentoring BTW take a look at my latest video: SwiftUI Animation kzitem.info/news/bejne/22quyaRtipuGpXo
@Neographic84
3 жыл бұрын
@@rebeloper thanks Rebeloper it's interesting ! if i have big problems i create a session with you! thank you
@rebeloper
3 жыл бұрын
Awesome Fabio. Looking forward to the sessions when you need them. Do you like SwiftUI? Check out my latest Live Stream on SwiftUI Button Styles: kzitem.info/news/bejne/y7CCyK1sbJt4qX4
@svitlanagrytsai4190
3 жыл бұрын
Thanks for the explanation!
@rebeloper
3 жыл бұрын
Glad it was helpful! If you enjoyed this video you might want to take a look at my lates video: Chart in iOS in SwiftUI -> kzitem.info/news/bejne/lI5o3qqdh6ido3o
Пікірлер: 48