<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 11, 2014 at 11:20 PM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Guys,<br>
<br>
Last Tuesday during our (favourite) iOS meeting [1] [2] we talked about modularization. We agreed with Android team modularization is scheduled for 2.0.<br>
<br>
For iOS we have several actions:<br>
<br>
1. rename existing repos (too bad we don’t follow well Android convention)<br>
• aerogear-ios-crypto<br>
• aerogear-ios-push (thanks passos for the suggestion)<br>
• aerogear-ios-otp<br>
• aerogear-ios-xcode-template<br>
• aerogear-ios-cookbook<br>
<br>
Since we’re talking about renaming, what about dropping “arerogear” for the repo name? </blockquote><div><br></div><div>+1 makes sense</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
all those repos belong to aerogear organization anyway. Maybe removing the aerogear part will stress more the small libraries aspect. Maybe sth we already discussed but can’t remember/find it. wdyt?<br>
<br>
2. Pipe and Store deprecated. All aerogear-ios we’ll stick to 1.7 version and will be marked deprecated.<br>
But …. don’t be scared new modules will replace them:<br>
<br>
• aerogear-ios-http : Lightweight lib around NSURLSession to ease HTTP calls with pluggable request and response Serializers. Very very Draft version [3] with some cookbook recipe [4]. With this module we will work directly with NSURLSession (iOS foundation networking) instead of using AFNetworking. Sure Andrea will like it: no dependency :)<br>
• aerogear-ios-oauth2 : dependent on aerogear-ios-http, bring all the good stuff like AccountManager, OAuth2 extensible adapters, fluid http post/get ...<br>
• aerogear-ios-storage usage of incrementalStorage to plug into Core Data<br></blockquote><div><br></div><div><br></div><div>+1 all of that sounds awesome!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Those modules will be written in Swift code. We’ll test them both in iOS7 and iOS8.<br></blockquote><div><br></div><div>+1 on Swift!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3. Cookbook recipes rpo<br>
• tag our repo 1.7: we didn’t have a tag strategy for cookbook demos but with the move from 1.X to 2.) I think we should<br>
* Swift demo naming convention add “-swift” for Swift version like we did [5]. We should also append “-objc” to other recipes to be consistent.<br></blockquote><div><br></div><div>yeah</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
4. Differentiate Swift vs Objective-C libs<br>
How to differenctiate Swift code. Specially for aerogear-ios-push which will be declined in 2 versions? One suggestion from Matthias was to have 2 separate branches.<br>
master -> objc-c<br>
until iOS8 is released and stable.<br>
I’m +1 with that idea.<br></blockquote><div><br></div><div>yeah, let's have ObjC on master now;</div><div>The master can, later this year, contain the Swift lib, and we move ObjC to be deprecated as soon as we do have iOS8 (~September)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Let me know if you have suggestions/objections. When we reach an agreement, I’ll create associated JIRA.<br>
<br>
++<br>
Corinne<br>
<br>
[1] <a href="http://oksoclap.com/p/aerogear_ios_meeting_01072014" target="_blank">http://oksoclap.com/p/aerogear_ios_meeting_01072014</a><br>
[2] <a href="http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-07-08-11.42.txt" target="_blank">http://transcripts.jboss.org/meeting/irc.freenode.org/aerogear/2014/aerogear.2014-07-08-11.42.txt</a><br>
[3] <a href="https://github.com/corinnekrych/aerogear-ios-http" target="_blank">https://github.com/corinnekrych/aerogear-ios-http</a><br>
[4] <a href="https://github.com/corinnekrych/Weather" target="_blank">https://github.com/corinnekrych/Weather</a><br>
[5] <a href="https://github.com/aerogear/aerogear-push-helloworld/tree/master/ios-swift" target="_blank">https://github.com/aerogear/aerogear-push-helloworld/tree/master/ios-swift</a><br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>