Thanks for a wonderful tutorial. I liked the focus you provided on refreshing (and the Color.random trick :) ) and it was great to compare the old and new ways. Observation is a breath of fresh air for an old programmer like me - I've had to struggle with c# bindings and NotifyPropertyChanged events and performance was always a visible issue with nested classes. You have a knack for anticipating the questions your audience has for sure :)
Great video, helped me. I did the migration of my app (around 30k lines of code) to the new Observation framework yesterday evening and I realised that Binding is probably meant to stay. At least, I currently don't see how Binding can be completely replaced.
🏆Outstanding! This inspired me to convert my swift playground project but now I'm stuck figuring how to add a "minimum deployments" section to the general tab of the projects file 😢
Although this is another good tutorial Prater, it still relies on NavigationView, which is to be deprecated. Right now I am trying to meld both your NavigationStack video (A Full Tour of NavigationStack , NavigationLink and navigationDestination - SwiftUI tutorial 2022) and this workflow of keeping views updates and when to use persistent data.
I have a rather “intricate” app and I find it so difficult to manage the states. For example, what if I have a class that has an array of structs as one of the properties and this struct has another property that should be an observable class (because some of its properties are going to be edited by the user)? Should everything become an observable class…?
Is there an advantage to creating an EnvironmentKey vs passing the object with ```.environment(object)``` and accessing it with ```@Environment(Object.self) var object``` ?
Please read again. I asked about .environment(SomeObjectName.self) not .environmentObject. The Apple examples I've seen do not create EnvironmentKeys.@@indiekiduk
This is great. I love the diagrams that make the iOS 17 data flow clear and show the difference between pre iOS 17
Happy that you like the diagrams ;)
Amazingly Clear, as always.
Great tutorial. Very well explained. Thank you so much!
Thanks!
Nice of you.
Thanks for a wonderful tutorial. I liked the focus you provided on refreshing (and the Color.random trick :) ) and it was great to compare the old and new ways. Observation is a breath of fresh air for an old programmer like me - I've had to struggle with c# bindings and NotifyPropertyChanged events and performance was always a visible issue with nested classes. You have a knack for anticipating the questions your audience has for sure :)
Your tutorials are really straightforward and thoroughly explained. Thanks.
Great lesson! Subbed!
Great, thanks Karin ❤
Thanks for your effort Karin 👍
Excellent as always! 🙂
Thank you so much 😀
Great video, helped me. I did the migration of my app (around 30k lines of code) to the new Observation framework yesterday evening and I realised that Binding is probably meant to stay. At least, I currently don't see how Binding can be completely replaced.
It’s more efficient and easier to preview if you pass book.title into the View init in instead of book
You're the best!
Great content, keep it coming please.
More to come!
What you want to express is that we can simplify the design pattern of MVVM to the design pattern of VM?😮
🏆Outstanding! This inspired me to convert my swift playground project but now I'm stuck figuring how to add a "minimum deployments" section to the general tab of the projects file 😢
Although this is another good tutorial Prater, it still relies on NavigationView, which is to be deprecated.
Right now I am trying to meld both your NavigationStack video (A Full Tour of NavigationStack , NavigationLink and navigationDestination - SwiftUI tutorial 2022) and this workflow of keeping views updates and when to use persistent data.
I have a rather “intricate” app and I find it so difficult to manage the states. For example, what if I have a class that has an array of structs as one of the properties and this struct has another property that should be an observable class (because some of its properties are going to be edited by the user)? Should everything become an observable class…?
Update for Swift 6?
🔥
Is there an advantage to creating an EnvironmentKey vs passing the object with ```.environment(object)``` and accessing it with ```@Environment(Object.self) var object``` ?
Yes EnvironmentKey is for a controller/manager object and .environmentObject is for a Combine pipeline object with published properties.
Please read again. I asked about .environment(SomeObjectName.self) not .environmentObject. The Apple examples I've seen do not create EnvironmentKeys.@@indiekiduk
@@indiekidukloll that’s basically the same
Thanks!
Thanks!
Thanks!
Thanks!