Bot releases are hidden (Show)
GitHubAPI
to get licenses from GitHub APIAcknowListViewController
and AcknowListSwiftUIView
to get missing licenses from GitHub API, with new canFetchLicenseFromGitHub
property to disable this behaviorURL
extension with openWithDefaultBrowser()
function to fix opening URLs on macOS with SwiftUIPublished by vtourraine over 1 year ago
AcknowListSwiftUIView
to fix navigation to repository URLAcknowListRowSwiftUIView
AcknowList
struct to represent list modelAcknowPackageDecoder
to parse “Package.resolved” files (Swift Package Manager)AcknowPodDecoder
AcknowParser
to manage parsing different file typesString
) into file URLs (URL
) insteadAcknowListViewController
to load acknowledgements from “Package.resolved” by defaultPublished by vtourraine over 2 years ago
Published by vtourraine almost 3 years ago
Published by vtourraine about 3 years ago
AcknowListViewController
default initializer implementatoin to fix Xcode 13 support (#89, #91)Published by vtourraine about 3 years ago
AcknowListViewController
to remove Objective-C compatibility, fixing Xcode 13 support (#89, #91)Published by vtourraine over 3 years ago
AcknowListViewController
to make initializers available with Objective-C (#81)AcknowListViewController
(#82)Published by vtourraine over 3 years ago
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.
AcknowListViewController
to detect URLs in header and footerAcknowListViewController
to make acknowledgements
property non-optionalAcknowListViewController
initializers
Acknow
(#75)Published by vtourraine over 3 years ago
Published by vtourraine about 4 years ago
Published by vtourraine over 4 years ago
Published by vtourraine over 4 years ago
Published by vtourraine over 4 years ago
Published by vtourraine over 4 years ago
Published by vtourraine over 4 years ago
AcknowListViewController
initializers access level (#66), by Kevin Mitchell Jr (@klmitchell2)Published by vtourraine almost 6 years ago
AcknowListViewController
initializer for multiple plist paths (#47), by Kieran Harper (@KieranHarper)Published by vtourraine about 6 years ago
Published by vtourraine over 6 years ago
AcknowViewController
(support layout margins, safe area insets)AcknowViewController
Published by vtourraine over 6 years ago