Adrian

@chriseidhof this helped me a lot in understanding the layout process of SwiftUI's views. One great discovery was that I was able to identify a significant bug in the original framework, which I reported and Apple already fixed (view dimensions caching bug).

@chriseidhof here is my HStackLayout: github.com/UndefinedAlgor… The actual algorithm was based on what @DaveAbrahams could tell me. There are 3 steps to determine the flexibility. 2 parts are cached. Propose 0 and infinity on the main axis, the last step is the remaining space.

@chriseidhof just found the HStack related blog post on objc.io. I did re-implement a huge chunk of SwiftUI's layout system including alignment APIs, which does support custom alignment keys just like the original. However for stacks I'm missing layout priority.

@natfriedman Is there a mobile app roadmap somewhere? I‘m highly interested when projects will be in the queue.

Our mobile elves have been hard at work crafting powerful new code review features for the GitHub apps. Pretty amazing what you can do from your phone now. (Note: these are middle-earth elves, not Keebler elves. No disrespect to Keebler – great cookies!)

@bzamayo @_inside Not even iOS is ready. iPadOS will make speakers on iPad Pro 2018 start produce random crackling noise. (I think it‘s a HW design flaw which got patched with iOS back in days after initial release, but iPadOS 14 broke this again.) It‘s my second unit with that issue.

iOS 14 tomorrow. I’m not ready. No one is ready.

@phausler Result: Am I nothing to you?

Failure is always an Optional

@SwiftUILab One nit about the article. Drop the VStack in your honey grid and rephrase the paragraph. Stacks cannot and will never underflow its children. That would completely break their behavior. The overflowing happens with `frame` modifier, not the VStack.

@DevAndArtist_ Sorry, there was a typo:

Did you know you can build a honeycomb with LazyVStack and little effort? New article "Impossible Grids with SwiftUI" is out now. I cover grid basics first, and then we take it one step further. The honeycomb is just one example. Enjoy! 🐝 #iosDev #SwiftUI swiftui-lab.com/impossible-gri…

@SwiftUILab Sorry it took me days to come back to this. I will check your example later and compare it to mine which behaved differently. 🧐

@SwiftUILab Just today I tried nesting scroll views and used a lazy stack. The scroll position is lost on reappearance. Yesterday I managed to keep a hosting controller alive, however its root view‘s state will have a band new state due to the issue that the hierarchy was detached.

@SwiftUILab Are you sure about the state restoration part of lazy api‘s? In general everything that is removed and readded will start with a brand new state. Try using a scroll view or an active animation in a lazy cell or remove/readd it, it won‘t keep the active state.

@chriseidhof @state @ObservedObject What do you mean I shouldn‘t? Not every object should be observable and represent some kind of state. This totally the case at the `App` level, or would you want to create fileprivate singletons instead?

@DevAndArtist_ @state @ObservedObject yes, it's all possible but you shouldn't do it!

Here's a first draft of a decision tree for how to define your SwiftUI properties...

@chriseidhof @state @ObservedObject State’s wrappedValue is still mutable and the PW will re-create your object as it wasn‘t designed to be lazy like StateObject. Instead use StateObject and let the object have `let objectWillChange = Empty<Never, Never>(…: false)` to indicate that it won‘t send any signals.

This is a simplification, there are many exceptions: for example, you could use a regular property or even @State for objects (instead of @ObservedObject) but then you won't be notified of changes.

@chriseidhof @jckarter Small nitpick: the `view` part can be generalized because we now have `App`, `Scene` and what not in WidgetKit.

@SwiftUILab Nothings seems to have changed there. I‘ll send you a gist with my workaround if you want to look at it (possibly for you next article, unless you‘re already done with it 😅).

@DevAndArtist_ Yes, gestures were a little messy last year. I haven't look at them this year yet. 😬

Time for a new two-part article. This time we are diving into matchedGeometryEffect. It may look innocent at first, but combine it with custom transitions and animatable modifiers... et voilà! Hero Animations! #SwiftUI #iOSDev swiftui-lab.com/matchedgeometr…

@SwiftUILab I mean, I build a workaround using pure SwiftUI, but there is a small bug which requires the `isTracking` state. However gestures are a nightmare in SeiftUI. The order of gestures, their combinations, etc. all things matter and produce other results.

@SwiftUILab Here is also a possible challenge for your article, which I couldn’t crack: There seems to be no way to create/observe states like `isTracking` and/or `isDecelerating` for the scroll view. I really need to build a custom picker that always centers, but I can’t. 😭

@SwiftUILab LazyHStack is interesting but it‘s type shadowing and clarly should be an anti-pattern. I‘d rather give it a different name or a small prefix.

Hi, here’s a new post about how to handle backward compatibility in SwiftUI to avoid plaguing your code with “available” checks. We’ll also explore how to combine the new App protocol and the old UIApplicationMain in the same app. swiftui-lab.com/backward-compa… #iOSDev #SwiftUI

@TizianoCoroneo @natpanferova @valv0 @ViewBuilder Here: twitter.com/jckarter/statu…

@DevAndArtist_ @natpanferova @valv0 @ViewBuilder I didn’t know this either! Do you have a link to learn more please? 🙏

Spotted in #WWDC20 Fruta app that we can add @ViewBuilder to body in #SwiftUI to be able to conditionally return different views. I was using Group for it before. Adding @ViewBuilder also works in Xcode 11 for iOS 13 😯

@natpanferova @TizianoCoroneo @valv0 @ViewBuilder Also note that you already used ViewBuilder through Group, as it‘s applied as the function builder attribute in its init‘s closure. 👍

@DevAndArtist_ @TizianoCoroneo @valv0 @ViewBuilder Will use `ViewBuilder` for this purpose now, thank you!