Re: New iOS SDK

Hi , Sorry about late response Ive been over seas , I just got back, For details on the server side that would depend on wether a push or pull model was used for getting data to sync with local DB or CoreData on the mobile device , Ive been looking at the work on usergrid 2.0 and as Ive said

Re: New iOS SDK

Jason, This sounds pretty awesome.  Can you be more specific about the changes required to the server-side code?  Rod --  Rod Simpson On June 15, 2015 at 12:30:27 AM, jas...@apps4u.com.au (jas...@apps4u.com.au) wrote: HI Rob and to All, I posted a while back about a new iOS sdks that Ive

Re: New iOS SDK

HI Rob and to All, I posted a while back about a new iOS sdks that Ive created and was going to release in February. Now I never meet that deadline as we (my team) wanted to add some features. For example we added in a file based cache that cached REST api request in a json format using a file

Re: New iOS SDK

Jason,  thanks for the update and no need to be hard on yourself. We sincerely appreciate all of your hard work!!   Rod Simpson On Wed, Jan 14, 2015 at 3:20 AM, Jason Kristian wrote: > HI TO ALL, > Im sorry Ive been late with the New iOS SDK I did say Id have it done by new > year, I’m sorry

Re: New iOS SDK

HI TO ALL, Im sorry Ive been late with the New iOS SDK I did say Id have it done by new year, I’m sorry Ive had a project that run over and Ive been flat out and not had time , Im just sending this to let every know Its nearly done and I’ll have out out by end of this month the latest , I just d

Re: New iOS SDK

Just convenance It could be one repo with the main SDK and a UI Helpers . IT can all be put in to one that fine as just because the UI Helpers classes are there dose not mean people have to use them .. And after thinking about it , its probably better to have one as most people will use the tab

Re: New iOS SDK

Jason, Separating the SDKs out from the main repo is something we have talked about for a while.  Since you are contributing a new SDK, we could start with yours.   The only concern I have is that we will end up with a lot of repos.  Is having 3 repos for this SDK mandatory?  Or is it just a co

Re: new iOS SDK

Just to let every one know I’m starting the new iOS SDK on Monday the repo is private at the moment once Ive had a day or two to get some code in there I’ll make it public. Also Ive had some reply which I’m grateful for . I’ll might need some directions once I get going , once Ive got the networ

Re: new iOS SDK

Diagram of network layer its not the class map but just a flow diagram of how I propose the network layer works November 19 2014 4:38 PM, "Jason Kristian" wrote: > Base Class. eg: Usergrid > One main Base Class that will be responsible for > Org and App name init. > Login > Oauth 2 (get token s

Re: new iOS SDK

Base Class. eg: Usergrid One main Base Class that will be responsible for Org and App name init. Login Oauth 2 (get token stash it and use in http header). Push Messaging registration One Main HTTP Client that is based on NSURLSession so it can have many requests in flight as once . Block based a

Re: new iOS SDK

HI Ive added this to the Google Doc on the iOS SDK proposal . This is just the start so I’ll create a class diagram using mind maps but I think I’ve covered the most important bits let me know if I’ve missed anything please. As they say two heads are better then one. Base Class. eg: Usergrid

Re: new iOS SDK

Good stuff!  Sounds like you have a good handle on the use-cases that are specific to iOS.  I have only built one app with iOS so can’t give as much input on that platform specifically.  I am really looking forward to what you come up with! Rod   --  Rod Simpson @rockerston rodsimpson.com O

Re: new iOS SDK

Thanks for feed back Jason Kristian | Director | Apps 4 U Pty Ltd. ph: +61 075699 8109 mob: +61 0411 389 392 e: Jason Kristian > On 18 Nov 2014, at 2:43 pm, Jason Kristian wrote: > > I agree with what you say, I’ve had a chance to deal with this in the PHP SDK >

Re: new iOS SDK

I agree with what you say, I’ve had a chance to deal with this in the PHP SDK which is why I wanted to tackle this SDK after I’d did the PHP version , To take paging as one example I would give users both options where there is a easy Iterator type method that can say page in lots of 20 for a U

Re: new iOS SDK

Other members have also built SDKs, like Scott Ganyo(Ruby) and Anuradha (Perl).  Jason, I know you have already been through this with PHP, but since you are spurring this really awesome discussion, I thought I would throw in some thoughts.  I added this copy to the doc, but pasting it here for

Re: new iOS SDK

HI to all Ive now made sure that the Google doc has got read / write access when opening with that link . It would be good if any one had input to speak up now as this will be a better SDK when all the Usergrid comunity has input so every idea and most users needs can be catered for. I was ho

Re: new iOS SDK

this link has edit permission https://docs.google.com/document/d/1Fd6zGpNEUh8KwrcIjK3W4aZ8gHlKax79qZFmc6F-kIA/edit?usp=sharing Jason Kristian | Director | Apps 4 U Pty Ltd. ph: +61 075699 8109 m

Re: new iOS SDK

Sorry Ill look it the doc it should be editable . and Yes I didn’t write unit Test It will contain UnitTest I unitTest all my code ad as its a requirement for Usergrid contribution. Jason Kristian | Director | Apps 4 U Pty Ltd. ph: +61 075699 8109 mob: +61 0411 389 392 e: Jason Kristian

Re: new iOS SDK

Jason, it looks like I can’t edit or comment on that doc.  One thing I don’t see mentioned is Unit / e2e tests.  It would be great if we were designing those from the start.  Also, samples.  It would be awesome if we had some samples - especially for the get-up-and-going things. Thanks! --  R

Re: new iOS SDK

Jason, Nice way to start this out! https://docs.google.com/document/d/1Fd6zGpNEUh8KwrcIjK3W4aZ8gHlKax79qZFmc6F-kIA/edit?usp=sharing I am reviewing now. --  Rod Simpson @rockerston rodsimpson.com On November 12, 2014 at 11:15:18 PM, Jason Kristian (jas...@apps4u.com.au) wrote: This is a link

Re: new iOS SDK

It is awesome to see all this discussion!  When the existing iOS SDK was made (3 yrs ago), we didn’t know exactly what people would want to use it for / how.  Very cool to be getting input on this! --  Rod Simpson @rockerston rodsimpson.com On November 13, 2014 at 11:46:58 AM, J (n75...@gmail.

Re: new iOS SDK

Hello, I like the idea of a new iOS SDK. Actually, I considered starting to work on something similar. Some comments, as reply to different mails and the google doc. > AFNetworking or RESTKit My intuition would be to use pure AFNetworking - last time I had a look at RESTKit it felt bloated. I

Re: new iOS SDK

This is a link to the new iOS SDK proposal as it would help if any one with ideas or suggestions gave the input as the more input we have the better the end result. https://docs.google.com/document/d/1Fd6zGpNEUh8KwrcIjK3W4aZ8gHlKax79qZFmc6F-kIA/edit?usp=sharing Jason Kristian | Director | Apps

Re: new iOS SDK

Cool , The libraries I would select will have to meet a few guideline that we (the Usergrid community) can se. Like for example license , stable is it going to be around , etc. Yes I would like to have JSON handling done right this is why I thought that the idea that the SDK be open to us

Re: new iOS SDK

Jason, It is awesome to see your enthusiasm.  My personal preference would be that we don’t work from the Apigee SDK.  That codebase is quite old and is definitely not the way we would architect it from scratch today. Your idea of using RESTKit or AFNetworking is great.  As you select libraries