James Dempsey

Investigate Xcode 14 multiplatform projects to see if updates are necessary

Xcode 14 introduces a new project version. Add support for it.

Consider adding automatic version updates via Sparkle 2

1

Sparkle 2 can be used with sandboxed apps. It seems just about ready to be released. Consider adding automatic updates and figure out if that can be done with a...

Consider choosing which instance of Xcode in file system to use for setting info

8

Currently the version of Xcode at /Applications/Xcode is searched for build setting info strings. Consider allowing the user to choose another version of Xcode instead, or possibly looking at multiple...

Consider supporting a platform/sdk-level set of xcconfig files for cross-platform projects

4

At the moment BSE performs all of its consolidation on the same 'level'. Common settings across multiple build settings at the project or target level are consolidated into a shared...

Consider processing Markdown links in build setting info descriptions

1

A number of build setting descriptions now contain Markdown links: `You can find more information at [our online reference](https://developer.apple.com/etc/etc) ` It would make for a cleaner info comment to strip...

Currently, the user is asked for a destination and only after choosing, do we alert the user the Xcode project version is not valid. Would be better to alert the...

Currently it looks like we write the destination folder and *then* figure out the project file is of an unsupported version. Would be better to either not write it in...

Consider some way of handling build setting changes over time (extracting modern settings from older project)

1

This issue is related to issue #33, where a setting is now obsolete and is now represented by two settings. The old setting is still allowed by Xcode to be...

In Xcode 11, the two Info.plist entries that change with each release are now automatically switched to two build settings. Since those two settings change with each release, it may...