AcknowList 3.2.0

• Add visionOS support

AcknowList 3.1.0

• Add GitHubAPI to get licenses from GitHub API
• Update AcknowListViewController and AcknowListSwiftUIView to get missing licenses from GitHub API, with new canFetchLicenseFromGitHub property to disable this behavior
• Add URL extension with openWithDefaultBrowser() function to fix opening URLs on macOS with SwiftUI

3.0.1

• Update AcknowListSwiftUIView to fix navigation to repository URL
• Add AcknowListRowSwiftUIView

3.0.0

• Add AcknowList struct to represent list model
• Add AcknowPackageDecoder to parse “Package.resolved” files (Swift Package Manager)
• Refactor plist file parser into AcknowPodDecoder
• Refactor AcknowParser to manage parsing different file types
• Refactor file paths parameters (String) into file URLs (URL) instead
• Update AcknowListViewController to load acknowledgements from “Package.resolved” by default

AcknowList 2.1.1

• Follow readable content guides
• Fix Swift Package Manager warning (exlude DocC folder)

AcknowList 2.1.0

• Add SwiftUI interface (supports iOS/tvOS/watchOS/macOS) (#83)
• Add DocC resources (#86)
• Fix Xcode 13 support (#85), by Thomas Mellenthin (@melle) and Francesc Bruguera (@ifrins)
• Update CocoaPods and Swift Package Manager support to require iOS 13/tvOS 13, necessary to support SwiftUI

AcknowList 2.0.3

• Update AcknowListViewController default initializer implementatoin to fix Xcode 13 support (#89, #91)

AcknowList 2.0.2

• Update AcknowListViewController to remove Objective-C compatibility, fixing Xcode 13 support (#89, #91)

AcknowList 2.0.1

• Update AcknowListViewController to make initializers available with Objective-C (#81)
• Fix header/footer layout when resizing AcknowListViewController (#82)

AcknowList 2.0.0

I’m very happy to finally release the AcknowList “2.0” update.

This project started in 2013, and, on the surface, it hasn’t changed much. It’s still parsing the same data, presenting it with the same interface. And I believe it’s still as useful today as ever, to help us promote all the amazing libraries that power our mobile applications.

Under the hood, there have been a lot of improvements. Labels are localized with more than 10 languages, licenses are nicely formatted, views support all the accessibility features, Dynamic Type, Dark Mode, Safe Area, and so on.

This “2.0” update introduces automatic link detection in headers and footers (thanks to NSDataDetector) and customizable table view style. It’s also the right time to break backward-compatibility. We get rid of superfluous methods and rename some parameters. The goal is to make this library easy-to-use, customisable, and future-proof.

So what happens next?

I currently still maintain Swift and Objective-C versions of this library. They both have their merits, but I think we’re past the point of diminishing returns. It will soon be time to deprecate the Objective-C project, to focus on just one version.

I never got around to offer an AppKit implementation... but the most obvious path forward is SwiftUI. Would that be a different library, or just a new option? Does the model need to change too, and offer a Combine API? I’ve created a GitHub issue, so feel free to join the discussion.

---

• Update AcknowListViewController to detect URLs in header and footer
• Update AcknowListViewController to make acknowledgements property non-optional
• Update AcknowListViewController initializers
  • Add optional table view style parameter (#69), by Matt Croxson (@Lumus)
  • Add initializer with array of Acknow (#75)
  • Rename plist path parameter (#75)
  • Remove initializer with multiple plist paths (#75)
• Improve Swift Package Manager support
  • Support SPM localized resources (#72), by Patrick (@iDevelopper)
  • Add SPM test target (#73)
  • Add SPM example project
  • Move sources, tests, and resources to follow SPM guidelines (#74)
• Add CocoaPods example project
• Update supported platforms to iOS 9 and more recent

---