JWAnimatedImage 0.2.1

You want to add pod 'JWAnimatedImage', '~> 0.2' similar to the following to your Podfile:

target 'MyApp' do
  pod 'JWAnimatedImage', '~> 0.2'
end

Then run a pod install inside your terminal, or from CocoaPods.app.

Alternatively to give it a test run, run the command:

pod try JWAnimatedImage

JWAnimatedImage 0.2.1

By
Jiawei Wang

An animated GIF engine for iOS in Swift with low memory & cpu usage.

Features

[x] Using asynchronous image decoding to reduce the main thread CPU usage.[NEW]
[x] Optimized for Multi-Image case.
[x] As UIImage and UIImageView extension,easy to use.
[x] Have a great performance on memory usage by using producer/consumer pattern.
[x] Have a great performance on CPU usage by using asynchronous loading.
[x] Allow to control display quality by using factor 'level of Integrity'
[x] Allow to control memory usage by using factor 'memoryLimit'

Installation

How to Use

let url = NSBundle.mainBundle().URLForResource(“imagename”, withExtension: "gif")!
let imageData = NSData(contentsOfURL:url)
let image = UIImage()
image.AddGifFromData(imageData!)
let gifmanager = JWAnimationManager(memoryLimit:20)
let imageview = UIImageView()
imageview.AddGifImage(image,manager:gifmanager)
imageview.frame = CGRect(x: 0.0, y: 5.0, width: 400.0, height: 200.0)
view.addSubview(imageview)

Architecture

UIImageView State:

JWAnimationManager:

Inital class 'JWAnimationManager' with memory limit. JWAnimationManager will manage all the GIF image views in it.

CheckForCache:

When adding a new GIF image view to 'JWAnimationManager',it estimate memory usage of new GIF,and add to 'totalGifSize' as a new valuation.When new valuation is greater than memory limit, JWAnimationManager changes all GIF image views to no-cache mode.

ImageView's life cycle:

ImageView will be suspended if function 'isDisplayedInScreen' returns false. ImageView will be deleted from 'JWAnimationManager' if function 'isDiscarded' returns false.

Benchmark:Compared with FLAnimatedImage

1.Display 1 Image

	CPU Usage[average]	Memory Usage[average]/MB
JWAnimatedImage	6% ~ 14% [8%]	7.5 ~ 8.4 [8.2]
FLAnimatedImage	8% ~ 24% [11%]	7.3 ~ ??? [???]

2.Display 3 Images

	CPU Usage[average]	Memory Usage[average]/MB
JWAnimatedImage	31% ~ 44% [38%]	12.4 ~ 13.4 [12.9]
FLAnimatedImage	36% ~ 62% [54%]	11.0 ~ 12.4 [11.3]

3.Display 30 Images

	CPU Usage[average]	Memory Usage[average]/MB
JWAnimatedImage	38% ~ 81% [53%]	59.3 ~ 82.4 [63.3]
FLAnimatedImage	126% ~ 185% [143%]	58.4 ~ 98.9 [74.2]

NOTE:

1.Measurement Factors:

Last updated: March 26, 2016
Measurement device: iPhone6 with iOS 9.3
Measurement tool: Profile in Xcode 7.3
Measurement image: See it in repository, all the parameters are default.
Raw data are here.

2.I've discussed the high memory usage of FLAnimatedImage with @mitchellporter and confirmed this problem does exist，as described here.

Licence

JWAnimatedImage is released under the MIT license. See LICENSE for details.