Re: [aerogear-dev] my AeroGear notes

Hi, Thanks for the replies. Some responses are inline. --- Yavuz Selim Yilmaz SUNY at Buffalo Computer Science and Engineering PhD Candidate On Jun 5, 2013, at 2:28 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: I started using AeroGear with the knowledge of there exist an open source library which makes mobile to REST API communication easier. But once I saw the AeroGear controller while reading through aerogear.org, I thought mobile libraries communicate with REST APIs through this controller on the server side (as the controller is there and is not a client library, i thought like this. it's maybe my misunderstanding though). And I found no explanation on my iOS API trial path which states the opposite (i.e. I don't need AeroGear controller, or better to say the library directly communicates with REST API). Once I get to know more and more about AeroGear, then it becomes clear (like checking more docs, playing with the example apps etc.). But if I choose to try quickly and pick a mobile lib, then it's harder to figure the things out. Here is my example: aerogear-android-todo app (versionCode=1) does not compile on my eclipse (it does if I compile on terminal). I think if and when the libs used in the example apps changed (i saw recent updates or bug reports), it sometimes (as in my case) causes problems. (probably my problem is related to a recent update on m2eclipse or android-sdk-deployer or something else, as the project shows error on pom.xml file. or maybe, even if I followed the links you provided to install those, I could not do it correctly - but on the contrary, it works well if I create a maven android project on eclipse and then add AeroGear dependency to pom.xml and use the AeroGear in my project). This would be an awesome solution I believe. As I started with a client library (while just knowing that there is an AeroGear controller), I was confused about server side. If that client lib's guide was talking a little bit about the server side, I think I could've got it quickly. I think my confusion was about client side libs (about what should be the server side specs). So your previous suggestion (libs guides state about backend side) would work awesome (and for the controller guide, as I am not familiar to Java backend (not as much as I do to iOS and Android), maybe it was hard specifically for me, so leaving that part). Good news. :) I integrated maven to eclipse and now using it. But my point is coming into scene considering this flow: - I started to develop for Android, so followed the documentation/guidelines that Google provides. Google recommends (and follows on the guidelines) using Eclipse and provides ADT plugin which takes care of the compilation. So, going through that docs, one does not need maven at all. So, I was expecting to have an option for AeroGear, which will work with my setup (i.e. Eclipse + ADT). But AeroGear requires me to use maven. I think this goes to the same explanation with the previous one. As I was not using maven for developing Android apps, it was not as quick as iOS. (not because of documentation, but because it was requiring me to use new tools) Yes, the kitchensink app.