parent
087eac626e
commit
6fcaa47f45
20
CHANGELOG.md
20
CHANGELOG.md
|
@ -6,6 +6,26 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [2.0.0] - 2021-02-23
|
||||
### Added
|
||||
- Update with the playbackMode support for `WebImage` and `AnimatedImage` #168
|
||||
- Update watchOS demo to watchOS 7, remove the custom indicator sample and use `ProgressView` instead #166
|
||||
- Update the WebImage to defaults animatable #165
|
||||
- Update the Example to make WebImage animatable by default #160
|
||||
|
||||
### Fixed
|
||||
- Fix the issue sometime the `WebImage` appear/disappear logic wrong. Using UIKit/AppKit to detect the visibility #164
|
||||
- Fix the leak of WebImage with animation and NavigationLink. #163
|
||||
- Try to fix the recursive updateView when using AnimatedImage inside `ScrollView/LazyVStack`. Which cause App freeze #162
|
||||
- Remove the fix for EXIF image in WebImage, which is fixed by Apple in iOS 14 #159
|
||||
|
||||
### Changed
|
||||
- Bump the limit to Xcode 12, because we need new iOS 14+ APIs check #167
|
||||
- Update the WebImage to defaults animatable #165
|
||||
|
||||
### Removed
|
||||
- Remove the wrong design onSuccess API. Using the full params one instead #169
|
||||
|
||||
## [1.5.0] - 2020-06-01
|
||||
### Added
|
||||
- Add the convenient API support to use SwiftUI transition with ease-in-out duration #116
|
||||
|
|
|
@ -54,8 +54,10 @@
|
|||
debugDocumentVersioning = "YES"
|
||||
debugServiceExtension = "internal"
|
||||
allowLocationSimulation = "YES">
|
||||
<BuildableProductRunnable
|
||||
runnableDebuggingMode = "0">
|
||||
<RemoteRunnable
|
||||
runnableDebuggingMode = "2"
|
||||
BundleIdentifier = "com.apple.Carousel"
|
||||
RemotePath = "/SDWebImageSwiftUIDemo-watchOS WatchKit App">
|
||||
<BuildableReference
|
||||
BuildableIdentifier = "primary"
|
||||
BlueprintIdentifier = "32E529362348A0DD00EA46FF"
|
||||
|
@ -63,7 +65,7 @@
|
|||
BlueprintName = "SDWebImageSwiftUIDemo-watchOS WatchKit App"
|
||||
ReferencedContainer = "container:SDWebImageSwiftUI.xcodeproj">
|
||||
</BuildableReference>
|
||||
</BuildableProductRunnable>
|
||||
</RemoteRunnable>
|
||||
</LaunchAction>
|
||||
<ProfileAction
|
||||
buildConfiguration = "Release"
|
||||
|
@ -71,8 +73,10 @@
|
|||
savedToolIdentifier = ""
|
||||
useCustomWorkingDirectory = "NO"
|
||||
debugDocumentVersioning = "YES">
|
||||
<BuildableProductRunnable
|
||||
runnableDebuggingMode = "0">
|
||||
<RemoteRunnable
|
||||
runnableDebuggingMode = "2"
|
||||
BundleIdentifier = "com.apple.Carousel"
|
||||
RemotePath = "/SDWebImageSwiftUIDemo-watchOS WatchKit App">
|
||||
<BuildableReference
|
||||
BuildableIdentifier = "primary"
|
||||
BlueprintIdentifier = "32E529362348A0DD00EA46FF"
|
||||
|
@ -80,7 +84,16 @@
|
|||
BlueprintName = "SDWebImageSwiftUIDemo-watchOS WatchKit App"
|
||||
ReferencedContainer = "container:SDWebImageSwiftUI.xcodeproj">
|
||||
</BuildableReference>
|
||||
</BuildableProductRunnable>
|
||||
</RemoteRunnable>
|
||||
<MacroExpansion>
|
||||
<BuildableReference
|
||||
BuildableIdentifier = "primary"
|
||||
BlueprintIdentifier = "32E529362348A0DD00EA46FF"
|
||||
BuildableName = "SDWebImageSwiftUIDemo-watchOS WatchKit App.app"
|
||||
BlueprintName = "SDWebImageSwiftUIDemo-watchOS WatchKit App"
|
||||
ReferencedContainer = "container:SDWebImageSwiftUI.xcodeproj">
|
||||
</BuildableReference>
|
||||
</MacroExpansion>
|
||||
</ProfileAction>
|
||||
<AnalyzeAction
|
||||
buildConfiguration = "Debug">
|
||||
|
|
12
README.md
12
README.md
|
@ -36,8 +36,6 @@ Besides all these features, we do optimization for SwiftUI, like Binding, View M
|
|||
|
||||
This framework is under heavily development, it's recommended to use [the latest release](https://github.com/SDWebImage/SDWebImageSwiftUI/releases) as much as possible (including SDWebImage dependency).
|
||||
|
||||
The v1.0.0 version is now **released**, which provide all the function above, with the stable API, fully documentation and unit test.
|
||||
|
||||
This framework follows [Semantic Versioning](https://semver.org/). Each source-break API changes will bump to a major version.
|
||||
|
||||
## Changelog
|
||||
|
@ -61,7 +59,7 @@ All issue reports, feature requests, contributions, and GitHub stars are welcome
|
|||
|
||||
iOS 14(macOS 11) introduce the SwiftUI 2.0, which keep the most API compatible, but changes many internal behaviors, which breaks the SDWebImageSwiftUI's function.
|
||||
|
||||
From v1.6.0, we adopt SwiftUI 2.0 and iOS 14(macOS 11)'s behavior.You can use `WebImage` and `AnimatedImage` inside the new `LazyVStack`.
|
||||
From v2.0.0, we adopt SwiftUI 2.0 and iOS 14(macOS 11)'s behavior.You can use `WebImage` and `AnimatedImage` inside the new `LazyVStack`.
|
||||
|
||||
```swift
|
||||
var body: some View {
|
||||
|
@ -75,7 +73,7 @@ var body: some View {
|
|||
}
|
||||
```
|
||||
|
||||
Note: However, many differences behavior between iOS 13/14's is hard to fixup. Due to maintain issue, in the future v2.0.0, we will drop the iOS 13 supports and always match SwiftUI 2.0's behavior.
|
||||
Note: However, many differences behavior between iOS 13/14's is hard to fixup. Due to maintain issue, in the future release, we will drop the iOS 13 supports and always match SwiftUI 2.0's behavior.
|
||||
|
||||
|
||||
## Installation
|
||||
|
@ -86,7 +84,7 @@ SDWebImageSwiftUI is available through [Swift Package Manager](https://swift.org
|
|||
|
||||
+ For App integration
|
||||
|
||||
For App integration, you should using Xcode 11 or higher, to add this package to your App target. To do this, check [Adding Package Dependencies to Your App](https://developer.apple.com/documentation/xcode/adding_package_dependencies_to_your_app?language=objc) about the step by step tutorial using Xcode.
|
||||
For App integration, you should using Xcode 12 or higher, to add this package to your App target. To do this, check [Adding Package Dependencies to Your App](https://developer.apple.com/documentation/xcode/adding_package_dependencies_to_your_app?language=objc) about the step by step tutorial using Xcode.
|
||||
|
||||
+ For downstream framework
|
||||
|
||||
|
@ -95,7 +93,7 @@ For downstream framework author, you should create a `Package.swift` file into y
|
|||
```swift
|
||||
let package = Package(
|
||||
dependencies: [
|
||||
.package(url: "https://github.com/SDWebImage/SDWebImageSwiftUI.git", from: "1.0")
|
||||
.package(url: "https://github.com/SDWebImage/SDWebImageSwiftUI.git", from: "2.0.0")
|
||||
],
|
||||
)
|
||||
```
|
||||
|
@ -149,7 +147,7 @@ var body: some View {
|
|||
}
|
||||
```
|
||||
|
||||
Note: This `WebImage` using `Image` for internal implementation, which is the best compatible for SwiftUI layout and animation system. But unlike SwiftUI's `Image` which does not support animated image or vector image, `WebImage` supports animated image as well (by defaults from v1.6.0).
|
||||
Note: This `WebImage` using `Image` for internal implementation, which is the best compatible for SwiftUI layout and animation system. But unlike SwiftUI's `Image` which does not support animated image or vector image, `WebImage` supports animated image as well (by defaults from v2.0.0).
|
||||
|
||||
However, The `WebImage` animation provide simple common use case, so it's still recommend to use `AnimatedImage` for advanced controls like progressive animation rendering, or vector image rendering.
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
|
||||
Pod::Spec.new do |s|
|
||||
s.name = 'SDWebImageSwiftUI'
|
||||
s.version = '1.5.0'
|
||||
s.version = '2.0.0'
|
||||
s.summary = 'SwiftUI Image loading and Animation framework powered by SDWebImage'
|
||||
|
||||
s.description = <<-DESC
|
||||
|
|
|
@ -15,7 +15,7 @@
|
|||
<key>CFBundlePackageType</key>
|
||||
<string>$(PRODUCT_BUNDLE_PACKAGE_TYPE)</string>
|
||||
<key>CFBundleShortVersionString</key>
|
||||
<string>1.6.0</string>
|
||||
<string>2.0.0</string>
|
||||
<key>CFBundleVersion</key>
|
||||
<string>$(CURRENT_PROJECT_VERSION)</string>
|
||||
</dict>
|
||||
|
|
Loading…
Reference in New Issue