Roger Lee rijieli

What’s the first class way to use PhotoKit to reimplement a high performance photo grid? We’ve been using a LazyVGrid and the photos caching manager, but are never able to hit the holy trinity (60hz, efficient memory footprint, minimal flashes of placeholder/empty cells)

A few things. It sounds like you're using the PHCachingImageManager already, which is definitely recommended.

One kind of specific note there—you want to use that to get media content delivered before you need to display it. So, for example, let's say you're showing a large grid of photos. You can be prefetching before and after, in expectation that the user's going to scroll. Or, if you're in a one-up situation, prefetching left and right so that you know the user is likely going to swipe, and you can quickly deliver those images to the screen and cache them.

Another thing you should really make sure you're doing is specifying the size you need for the grid size. For example, if your app supports showing a smaller grid

(Summary generated by ChatGPT based on the automatic transcription. Transcript is attached to this Gist)

Q: What's the best approach to updating my app's UI for the new design?

A:

I think the best approach is to start from either the top down or the bottom up---however you perceive the hierarchy of your application. Focus on the big structural parts, since they tend to be most affected by the design and are often reflected in your code structure. Start there, then focus on the smaller elements.

Follow-up (Mohammed):

(Summary generated by ChatGPT based on the automatic transcription. Transcript is attached to this Gist)

Panelists:

Host: Shashank
Panelists: Michael, Erik, Richard, Ronan

Reliable mouseEnter/Exit for SwiftUI

On Mac, SwiftUI's .onHover closure is not always called on mouse exit, particularly with high cursor velocity. A grid of targets or with finer target shapes will often have multiple targets falsely active after the mouse has moved on.

It is easy to run back to AppKit's safety. Below is a SwiftUI-like modifier for reliable mouse-tracking. You can easily adapt it for other mouse tracking needs.

import SwiftUI

	//
	// IntelligenceUIPlatterView.swift
	//
	// Created by Stephan Casas on 2/13/25.
	//

	import SwiftUI
	import AppKit
	import Combine

	@available(iOS 15.0, *)
	public struct RichTextEditor : SwiftUICore.View {
	public init(text: SwiftUICore.Binding<Foundation.AttributedString>)
	@_Concurrency.MainActor @preconcurrency public var body: some SwiftUICore.View {
	get
	}
	@available(iOS 15.0, *)
	public typealias Body = @_opaqueReturnTypeOf("$s7SwiftUI14RichTextEditorV4bodyQrvp", 0) __
	}
	@available(*, unavailable)

	//
	// HelloAnimation.swift
	// OpenvisionOS
	//
	// Created by Amos Gyamfi on 17.2.2024.
	//

	import SwiftUI

	struct HelloAnimation: View {


	# source http://blog.jaredsinclair.com/post/97193356620/the-best-of-all-possible-xcode-automated-build
	#
	# Set the build number to the current git commit count.
	# If we're using the Dev scheme, then we'll suffix the build
	# number with the current branch name, to make collisions
	# far less likely across feature branches.
	# Based on: http://w3facility.info/question/how-do-i-force-xcode-to-rebuild-the-info-plist-file-in-my-project-every-time-i-build-the-project/
	#
	git=`sh /etc/profile; which git`