PERFECT ! :)<div><br></div><div><br><br><div class="gmail_quote">On Thu, Mar 14, 2013 at 2:48 PM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">thanks for the feedback!<div><br></div><div>answers inline</div><div><br><div><div class="im">
<div>On Mar 14, 2013, at 1:58 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div>A few comments</div><div><br></div><div>1) Change the mkdir/value to<div>
<div>mkdir -p ~/Library/Developer/Xcode/Templates/Application/Project\ Templates/</div></div></div></blockquote></div>ok</div><div><div class="im"><br><blockquote type="cite"><div><div><div><br></div><div>
2) Not sure, but IMO the gray info on cocoapods can be easily missed. I know that AFNetworking uses that approach... but I prefer making this a bit more explicit.</div><div>Especially with our JBoss background, we may target a different set of developers</div>
</div></div></blockquote><div><br></div></div><div>I put and "important notice" header and updated the doc with why "pod install" is required and link to cocoapods web site</div><div class="im"><blockquote type="cite">
<div><div>
<div><br></div><div>3) What about adding this as the first line of the PODFILE ?</div><div><span style="line-height:16px;color:rgb(51,51,51);font-size:12px;white-space:pre-wrap;font-family:Consolas,'Liberation Mono',Courier,monospace;margin:0px;border:0px;padding:0px">xcodeproj</span><span style="line-height:16px;color:rgb(51,51,51);font-size:12px;white-space:pre-wrap;font-family:Consolas,'Liberation Mono',Courier,monospace"> </span><span style="line-height:16px;color:rgb(221,17,68);font-size:12px;white-space:pre-wrap;font-family:Consolas,'Liberation Mono',Courier,monospace;margin:0px;border:0px;padding:0px">'XXXX.xcodeproj'</span></div>
<div>(where the XXXXXX is hte name of the chosen app name)</div></div></div></blockquote><div><br></div></div>ok</div><div><div class="im"><br><blockquote type="cite"><div><div><div><br></div><div>4) instead of "5.0" (double quotes), I'd prefer single quotes: '5.0' (the CocoaPod doc uses that format as well)</div>
<div><a href="https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/CocoaPods.xctemplate/TemplateInfo.plist#L15" target="_blank">https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/CocoaPods.xctemplate/TemplateInfo.plist#L15</a></div>
</div></div></blockquote><div><br></div></div>ok<div class="im"><br><blockquote type="cite"><div><div>
<div><br></div><div>5) Should this be ".gitignore" (the . is missing??)??</div><div><a href="https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/gitignore" target="_blank">https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/gitignore</a></div>
</div></div></blockquote><div><br></div></div>done on purpose so that the filename is visible when browsing. During the generation process it is converted to .gitignore on the user's project directory.</div><div><div class="im">
<br><blockquote type="cite"><div><div>
<div><br><div><div>6) use Xcode - not xCode, noXCode :)</div><div>one example:</div><div><a href="https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/ViewController.h#L3" target="_blank">https://github.com/cvasilak/aerogear-ios-xcode-template/blob/master/AeroGear/Application.xctemplate/ViewController.h#L3</a></div>
</div></div></div></div></blockquote><div><br></div></div>ok :)</div><div><br></div><div>Thanks!</div><div><br></div><div>-</div><div>Christos</div><div><div class="h5"><div><br></div><div><blockquote type="cite"><div><div>
<div><div>
<div><br></div><div><br></div><div>Cheers!</div><div><br></div><div>Great works!!!</div><div><br><div class="gmail_quote">On Thu, Mar 14, 2013 at 12:14 PM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi,</div><div><br></div><div>the Xcode template is ready[1], I would appreciate if someone else gives it a try too and let me know if there are any issues.</div>
<div>If not we can go ahead and merge in our organisation repo</div><div><br></div><div>Thanks!</div><div>Christos</div><div><br></div><div>[1] <a href="https://github.com/cvasilak/aerogear-ios-xcode-template" target="_blank">https://github.com/cvasilak/aerogear-ios-xcode-template</a></div>
<div><div><div><br></div><div><div>On Mar 13, 2013, at 10:16 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite">yup, I know... But I was curious if we want to encourage folks to use a more liberal license :)<div>
<br></div><div>In any case, we should at least add some header, like "generated by the JBoss AeroGear team/plugin" etc...<br>
<div><br><div class="gmail_quote">On Wed, Mar 13, 2013 at 9:08 AM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>Hi,</div><div><br></div><div>from what I have seen (e.g. in AFNetworking case) the generated source code doesn't contain any license header so I guess it's left for the user to decide afterwards. I can easily go ahead and add it if we choose so though.</div>
<div><div><br></div><div><br></div><div><div>On Mar 12, 2013, at 11:47 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite">
+1 the application is easy and simple - exactly what we want.<div><br></div><div>Question: Do we want to use our Apache licensed template ? <br><br><div class="gmail_quote">On Tue, Mar 12, 2013 at 2:28 PM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I've created an quick-start example here[1] that will be used as an Xcode template [2] (think of it as maven archetype for iOS) for our users to easily get started with the framework. Prior to create the config required to produce the template, I would like to have your opinion on what else should be included in the base demo.<br>
<br>
Currently it connects to our TODO demo, retrieves the tasks and updates a table view component. I think it serves as a good basis for users to extend.<br>
<br>
Wdyt?<br>
<br>
Thanks<br>
Christos<br>
<br>
<br>
[1] <a href="https://github.com/cvasilak/AeroGearPrototype" target="_blank">https://github.com/cvasilak/AeroGearPrototype</a><br>
[2] <a href="http://tinyurl.com/bvhusuk" target="_blank">http://tinyurl.com/bvhusuk</a><br>
<br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote>
</div><br></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote>
</div><br></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></div></div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote>
</div><br></div></div></div></div><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>