> Useful for Mac users who need to access Windows network shares.
Looks great.
Related story. In late 2010 a client asked me to write effectively the same thing for him as a Mac app, using that one protocol I can't remember the name of, but which had promise and never quite caught on. All I can remember about it is that I implemented JavaScript's `for await (...)` in 2010-era Objective-C, and I felt like a genius because I had never even heard of such a concept before, and came up with it on my own just to solve a problem in that project. That function worked amazingly and only took like 100 loc or something. I wonder if he still has that source code around somewhere.
SwiftUI uses a different event handling model than AppKit's responder chain. This NSViewRepresentable approach is afaik the recommended way to access AppKit's event handling capabilities from SwiftUI.
5 comments
[ 2.6 ms ] story [ 18.6 ms ] threadLooks great.
Related story. In late 2010 a client asked me to write effectively the same thing for him as a Mac app, using that one protocol I can't remember the name of, but which had promise and never quite caught on. All I can remember about it is that I implemented JavaScript's `for await (...)` in 2010-era Objective-C, and I felt like a genius because I had never even heard of such a concept before, and came up with it on my own just to solve a problem in that project. That function worked amazingly and only took like 100 loc or something. I wonder if he still has that source code around somewhere.
> struct FocusableTextField: NSViewRepresentable {
Did things change? We used to use "responder chains" to do this. In fact that concept was created to avoid having to subclass for keyboard shortcuts.
https://developer.apple.com/documentation/swiftui/nsviewrepr...
For windows users you can install a little script as a URL handler for smb addresses to go the other way.