For option 2...
...you could consider using Swift Package Manager, to make a number of separate self-contained modules.
Each App would be it's own Xcode project, and could include whichever Swift Packages it requires.
Of course, you could use a single Swift Package, for all the shared code.
But I would lean towards using a number of packages, each with a clearly-defined purpose.
I find the modular approach cleaner, and easier to maintain.
If you click the blue "Share this Post" icon (at the far right, below the post)...
...you can get the url
e.g. for your initial post here:
https://developer.apple.com/forums/thread/702354
And this reply is:
https://developer.apple.com/forums/thread/702354?answerId=707411022#707411022
Unfortunately, I don't seem to be able to "Copy" the link...
...I have to send it somewhere else (e.g. a new email), then grab it from there.
(to view: UIView,
..."to" is used when calling the func
"view" is used inside the func
(view: UIView,
"view" is used both when calling the func, and inside the func
So it is a stylistic thing... it may be preferable to think of anchoring "to" something.
But inside a func body, "to" is pretty meaningless, so we replace it with "view".
You could consider "Unlisted app distribution".
Release your apps that aren’t suited for public distribution as unlisted on the App Store, discoverable only with a direct link.
See https://developer.apple.com/support/unlisted-app-distribution/
You could try restoring the M1 MBP from the second Mac...
Connect the two Macs using USB-C
Run Apple Configurator 2 on the second Mac
Put the M1 MBP into "DFU" mode
Then you can attempt a "Revive", or a "Restore" from Apple Configurator 2
More information here:
"Revive or restore a Mac with Apple silicon using Apple Configurator 2"
https://support.apple.com/en-gb/guide/apple-configurator-2/apdd5f3c75ad/mac
Agree 100%
Particular annoyances, which spoil the forum:
First-time posters who clearly ask a non-developer question
One-time posters, who don't acknowledge answers, and never post again
Obvious spam messages (which include phone numbers in the question)
Perhaps it is too easy to sign up!
And certainly not clear enough that this is (intended to be) a Developer Forum.
How hard would it be to use a Catalina driver for an audio interface to create a driver for Monterey or Big Sur?
I would say it would either be extremely hard, or impossible.
For option 2...
...you could consider using Swift Package Manager, to make a number of separate self-contained modules.
Each App would be it's own Xcode project, and could include whichever Swift Packages it requires.
Of course, you could use a single Swift Package, for all the shared code.
But I would lean towards using a number of packages, each with a clearly-defined purpose.
I find the modular approach cleaner, and easier to maintain.
If you click the blue "Share this Post" icon (at the far right, below the post)...
...you can get the url
e.g. for your initial post here:
https://developer.apple.com/forums/thread/702354
And this reply is:
https://developer.apple.com/forums/thread/702354?answerId=707411022#707411022
Unfortunately, I don't seem to be able to "Copy" the link...
...I have to send it somewhere else (e.g. a new email), then grab it from there.
(to view: UIView,
..."to" is used when calling the func
"view" is used inside the func
(view: UIView,
"view" is used both when calling the func, and inside the func
So it is a stylistic thing... it may be preferable to think of anchoring "to" something.
But inside a func body, "to" is pretty meaningless, so we replace it with "view".
You could consider "Unlisted app distribution".
Release your apps that aren’t suited for public distribution as unlisted on the App Store, discoverable only with a direct link.
See https://developer.apple.com/support/unlisted-app-distribution/
You could try restoring the M1 MBP from the second Mac...
Connect the two Macs using USB-C
Run Apple Configurator 2 on the second Mac
Put the M1 MBP into "DFU" mode
Then you can attempt a "Revive", or a "Restore" from Apple Configurator 2
More information here:
"Revive or restore a Mac with Apple silicon using Apple Configurator 2"
https://support.apple.com/en-gb/guide/apple-configurator-2/apdd5f3c75ad/mac
Agree 100%
Particular annoyances, which spoil the forum:
First-time posters who clearly ask a non-developer question
One-time posters, who don't acknowledge answers, and never post again
Obvious spam messages (which include phone numbers in the question)
Perhaps it is too easy to sign up!
And certainly not clear enough that this is (intended to be) a Developer Forum.
How hard would it be to use a Catalina driver for an audio interface to create a driver for Monterey or Big Sur?
I would say it would either be extremely hard, or impossible.