On Oct 11, 2013, at 10:37 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
Hello All,
Agree for the file upload, having a mechanism to check the size and reject it if too big
seems good idea
> [1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-...
I guess all should be gather in our new max-rs nased backend repo.
https://github.com/aerogear/aerogear-controller-demo
+1
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
aerogear.org [1]. Any suggestion to stick to DRY principle?
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.
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?
+1
Thanks,
Christos
++
Corinne
[1]
http://aerogear.org/docs/guides/iOSCookbook/
[2]
https://github.com/corinnekrych/aerogear-ios-cookbook
On Sep 19, 2013, at 1:29 PM, Daniel Passos <daniel(a)passos.me> wrote:
> Hey Corinne,
>
> +∞ to cookbook
> +9001 to create server
>
> 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.
>
> [1]
http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Android-multipart-...
> [2]
https://github.com/secondsun/aerogear-integration-tests-server
>
>
>
> On Thu, Sep 19, 2013 at 4:42 AM, Corinne Krych <corinnekrych(a)gmail.com> wrote:
> Hello Guys
>
> 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.
>
> Talking about it on IRC we had a question though: how do we handle when in the
exemple you need a server side code.
>
> Would you deploy it on cloud server and available for client apps. Like in
https://github.com/aerogear/aerogear-android-cookbook/blob/master/src/org...
>
> Or would you package the server side exemple in the cookbook repo?
> I rather put servide side in cookbook as we could also to demo this part too.
>
> We have this need for example with the multipar file upload example:
>
https://github.com/cvasilak/MultiPartDemo
>
https://github.com/cvasilak/MultiPartIOSDemo
>
> ++
> Corinne
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev