<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 11, 2013 at 10:37 AM, 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">Even better if we eventually push the AG Cookbook to App Store.<br></blockquote><div><br></div><div>Not sure - we had that discussion before. Apple is very clear that they don't like demos in the App-Store; we better not bug them :-)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
On Oct 11, 2013, at 10:35 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
<br>
> I haven't though of a cookbook app. Interesting concept.<br>
> We could implement it later glueing together the recipes.<br>
> +1<br>
><br>
> To start with, I'd like to have a list of recipes bundled together in a commom cookbook repo and as you suggested the main readme section willbe the table of content and link to different sub-folder readme or for otp/push other repos.<br>
><br>
> ++<br>
> Corinne<br>
><br>
> On Oct 11, 2013, at 10:25 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:<br>
><br>
>><br>
>><br>
>><br>
>> On Fri, Oct 11, 2013 at 10:07 AM, Christos Vasilakis <<a href="mailto:cvasilak@gmail.com">cvasilak@gmail.com</a>> wrote:<br>
>><br>
>> On Oct 11, 2013, at 10:37 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
>><br>
>>> Hello All,<br>
>>><br>
>>> Agree for the file upload, having a mechanism to check the size and reject it if too big seems good idea<br>
>>>> [1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-cookbook-component-td3553.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-cookbook-component-td3553.html</a><br>
>>><br>
>>> I guess all should be gather in our new max-rs nased backend repo.<br>
>>> <a href="https://github.com/aerogear/aerogear-controller-demo" target="_blank">https://github.com/aerogear/aerogear-controller-demo</a><br>
>><br>
>> +1<br>
>><br>
>>><br>
>>> For the iOS cookbook, I'd like to have a root directory splited in different HowTo… sub-directories. Ideally ,I'd like each HowTo section to have it's own readme file with details explanation so that you can read the cookbook and have all information gather in one place. However, the centent of those read me files will be very close to <a href="http://aerogear.org" target="_blank">aerogear.org</a> [1]. Any suggestion to stick to DRY principle?<br>
>><br>
>> personally I would prefer when downloading the demo to be self-contained. Logical Structure can be provided by the IDE (e.g. folder) and/or by the naming of the different ViewControllers (PipelineViewController, SQliteViewController etc). For the README I guess on the demo's project README.md we can point to the ios-cookbook demo with all the details.<br>
>><br>
>><br>
>> you prefer single, isolated demos - at least one folder: one case, right ? and on the "home screen" of the cookbook app, perhaps a bunch of 'links' (e.g. "OTP demo", "Auth Demo",……), right ?<br>
>><br>
>> I'd like that too<br>
>><br>
>><br>
>><br>
>>><br>
>>> Most of the recipes could be wrtitten using storyboard approach [2] because it's much less code, therefore it helps focus on the main tutorial code. Interesting also to see that in iOS7, when creating your project with XCode5 template storyboard is no more an option by default behaviour. wdyt?<br>
>><br>
>> +1<br>
>><br>
>> Thanks,<br>
>> Christos<br>
>><br>
>><br>
>>><br>
>>> ++<br>
>>> Corinne<br>
>>><br>
>>> [1] <a href="http://aerogear.org/docs/guides/iOSCookbook/" target="_blank">http://aerogear.org/docs/guides/iOSCookbook/</a><br>
>>> [2] <a href="https://github.com/corinnekrych/aerogear-ios-cookbook" target="_blank">https://github.com/corinnekrych/aerogear-ios-cookbook</a><br>
>>><br>
>>> On Sep 19, 2013, at 1:29 PM, Daniel Passos <<a href="mailto:daniel@passos.me">daniel@passos.me</a>> wrote:<br>
>>><br>
>>>> Hey Corinne,<br>
>>>><br>
>>>> +∞ to cookbook<br>
>>>> +9001 to create server<br>
>>>><br>
>>>> We already discussed it here and several times at meetings[1]. This is on our roadmap. Summers started to develop POC[2], but stopped. Our idea was to use vert.x and make one "module" per feature isolated to use in cookbook and integration tests.<br>
>>>><br>
>>>> [1] <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-cookbook-component-td3553.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-cookbook-component-td3553.html</a><br>
>>>> [2] <a href="https://github.com/secondsun/aerogear-integration-tests-server" target="_blank">https://github.com/secondsun/aerogear-integration-tests-server</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Thu, Sep 19, 2013 at 4:42 AM, Corinne Krych <<a href="mailto:corinnekrych@gmail.com">corinnekrych@gmail.com</a>> wrote:<br>
>>>> Hello Guys<br>
>>>><br>
>>>> I like very Android Cookbook repo and I like to start the same idea for iOS. Putting together receipes in one common repo with different exemples sorted by folder. Adaopting the naming convention "HowTo…." for the file name that will match the documentation "How to … " is a good ay to easily find the information you need.<br>
>>>><br>
>>>> Talking about it on IRC we had a question though: how do we handle when in the exemple you need a server side code.<br>
>>>><br>
>>>> Would you deploy it on cloud server and available for client apps. Like in <a href="https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org/jboss/aerogear/cookbook/pipeline/HowToUsePipeWithPagination.java#L58" target="_blank">https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org/jboss/aerogear/cookbook/pipeline/HowToUsePipeWithPagination.java#L58</a><br>
>>>><br>
>>>> Or would you package the server side exemple in the cookbook repo?<br>
>>>> I rather put servide side in cookbook as we could also to demo this part too.<br>
>>>><br>
>>>> We have this need for example with the multipar file upload example:<br>
>>>> <a href="https://github.com/cvasilak/MultiPartDemo" target="_blank">https://github.com/cvasilak/MultiPartDemo</a><br>
>>>> <a href="https://github.com/cvasilak/MultiPartIOSDemo" target="_blank">https://github.com/cvasilak/MultiPartIOSDemo</a><br>
>>>><br>
>>>> ++<br>
>>>> Corinne<br>
>>>><br>
>>>><br>
>>>><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>
>>>><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>
>>><br>
>>><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>
>><br>
>><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>
>><br>
>><br>
>><br>
>> --<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><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>
><br>
<br>
<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></div></div></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>