On Oct 11, 2013, at 10:07 AM, Christos Vasilakis <cvasilak(a)gmail.com> wrote:
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
> I guess all should be gather in our new max-rs nased backend repo.
> 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
. 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
What do you mean by demo? In the cookbook I like to see a list of recipes which are I
guess close to what you call demo.
See an example here:
HowToUseSQLiteStorage is a Xcode project by itself. It is indeed self contained. This
recipe doesn't need a backend.
Although the recipe is an app by itself I try to keep the UI code minimal.
The samples could be fun too. It could be displaying makup on a map instead of the
traditional TableView. J
It is true that we have separate aerogear-push-ios-deno and aerogear-otp-ios-demo
For those we could add a recipe that ill point to the github repo.
The key feature of a cookbook is to contain a fair number of recipes.
> Most of the recipes could be wrtitten using storyboard approach  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?
>  http://aerogear.org/docs/guides/iOSCookbook/
>  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. This is on our
roadmap. Summers started to develop POC, but stopped. Our idea was to use vert.x and
make one "module" per feature isolated to use in cookbook and integration
>>  https://github.com/secondsun/aerogear-integration-tests-server
>> On Thu, Sep 19, 2013 at 4:42 AM, Corinne Krych <corinnekrych(a)gmail.com>
>> 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
>> 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:
>> aerogear-dev mailing list
>> aerogear-dev mailing list
> aerogear-dev mailing list
aerogear-dev mailing list