Hello Swift lovers,
We’ve already talked about iOS7 support for our Swift libs in this thread [0] but I’d like
to start from fresh with a different approach.
I’ve recently revisit the subject with some experiments and I ended up writing a blog
post: How well does Swift play with iOS7? [1]
where I take 2 examples: aerogear-ios-push and aerogear-ios-http with their demo apps:
HelloWorld [2] and ChuckNorrisJokes [3] all written in Swift and run them in iOS7
device/simulator.
This is just an experiment, but moving forward I’ve created a JIRA epic [4] to support
iOS7 for our aerogear-ios Swift libraries. In the long run, we will have only one branch
to maintain: master.
All the libs should be tested with iOS7 and iOS8 examples. Some libs can stay in
Objective-C (until we feel the need of moving them to Swift) like aerogear-ios-otp for
example.
A corraleted JIRA epic [5] is to test all aerogear-ios libs written in Objective-C with
iOS8 and Swift. We might have issues around common crypto usage in Swift [6].
I’d like to adress those 2 epics for iOS 2.4 release and deprecate the 1.6.X branch
maintenance.
wdyt?
++
Corinne
[0]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Swift-to-Objective...
[1]
http://corinnekrych.blogspot.org/2015/04/how-well-does-swift-plays-on-ios...
[2]
https://github.com/corinnekrych/unified-push-helloworld/tree/ios7.experim...
[3]
https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/ios7.support...
[4] TODO when jira is up
[5] TODO when jira is up
[6]
http://stackoverflow.com/questions/25248598/importing-commoncrypto-in-a-s...