Instead of a .sdef file (or older formats) made in advance and stored in an app’s bundle, I wonder if the script dictionary can be set soon after the app opens? I seen related API, with a note that the scripting file reader ultimately calls that API. I grok about 90% of that API, but I’m not sure it’s possible.

One of the features of Big Sur and ARM-based Macs is that they can run iOS and iPadOS apps. The iOS app format is used for iPhones and iPods Touch. This format is reused for iPadOS apps. But isn't the format used, for the third time, for tvOS apps? I've read descriptions of iPhone/iPad/AppleTV triple-platform apps. So, can AS-Macs run tvOS-only apps too? If not, why? Wouldn't they be easier, since they're designed with taking a non-direct-touchscreen in mind?

In the original SwiftUI, you still used NSWindow and friends, so the older techniques would work. But with SwiftUI 2 taking over all of the command reception and handling, where is printing supposed to be recognized (and the PDF or whatever gets sent back)?

As seen in the WWDC 2020 videos, the ways Scene instances can be initialized are constrained by what is present in the App instance's definition. Is there a way for a scene to produce another, where the first scene can use the initialization arguments to control how much it shares or doesn't share with the new scene?

Just been watching some WWDC 2020 videos again, specifically "App essentials in SwiftUI". I wondered about the two different scene types shown. Most of the time was WindowGroup, but the end mentioned DocumentGroup. The DocumentGroup scene type allows instances to have separate root objects. But the examples of WindowGroup used a shared root, even though each scene kept independent values of where they were in the interface. Is there a way for a Scene type to be configured to allow independent roots? Can that be added if not? (Like DocumentGroup, a scene type allowing independent roots would need a separate View type to represent the "open-file dialog" equivalent to choose a root.) This is a rewording of a previous post - https://developer.apple.com/forums/thread/655037. I've also added an official feedback for this: FB8307528.

(Note: If it makes a difference, I'm a Mac developer.) In Swift UI 1, you create your application View instances by piecing together various Apple-supplied views. If they weren't sufficient, you could create new primitives with a hosting controller supporting a UIView/NSView setup. Is there a similar method for making new custom primitive Scene instances? What I read about the Apple-supplied ones so far don't cover: Making a mode-less dialog panel, which will have at most one instance. (If you activate the command for the panel when an instance already exists, the current instance is brought to the foreground, instead of making a second instance.) Making a setup similar to the Document system, but the source data are URL/URI/URNs instead of FileWrappers (i.e. the each pseudo-document is an internet download). A web browser would work like this. The ability of a window being made from a command off another window, and you want at least one of the two windows to keep a (weak) reference token to the other. Can this capability be added before the Fall releases if it isn't there already?

I want a modeless dialogue panel in Mac OS that has at most one instance on screen at a time. I can figure how to do it with AppKit and/or Swift UI 1. But can the new WindowGroup stuff have its count of active windows limited to one? Alternatively, can we mix in windows made the traditional way along with a Swift UI 2 App/Scene set up?

I still have Xcode 11.0 on my alternate hard drive (SSD) with a Catalina beta installed. I tried installing 11.5, but the Mac App Store refused to do it. I found the general developer downloads site, and grabbed it from there. But the app icon has a white barred-circle around it and won't run. I think I have the latest beta on the hard drive ("10.15 Beta (19A582a)"). I'm also going to try Xcode 12.0 beta 2.

I found the SASL libraries poking around with "ls." Is there a wrapper library in Apple's frameworks for it? At the Documentation site, I did see a "GSS" framework; does that do all the parts of SASL?

Normally, you just declare properties in your `NSObject`-derived class as `@objc` and `dynamic`, and Swift automatically makes those properties KVC- and KVO-compliant. But that can't be done all the time. The class's "public properties" may be forwarding to some hidden object, and/or you may want to throw NSError upon a validation failure. (Swift will/did-set accessors cannot error out; you can only `fatalError` if the value is wrong). There are KVC and KVO Guides, that for a given key name we can use methods with special names to get/set/validate keyed values. Those guides are in Objective-C; I'm wondering what the equivalent method name patterns are for Swift.(I want to dabble making a Mac app, planning to use KVC/O to connect the model to any actions affecting it. This means I need to way to transmit errors from trying to submit out-of-range values.)