Re:IOS Boilerplate: A base template for iOS apps
by Zev on Wednesday September 14, 2011 @06:27PM
(#2998103)
I typically use PullToRefresh from https://github.com/leah/PullToRefresh instead of EGOTableViewPullRefresh. It positions itself as a superclass that handles all of the logic, rather than an external object that handles the delegate methods (as EGO does).
Re:IOS Boilerplate: A base template for iOS apps
by lukeredpath on Wednesday September 14, 2011 @06:46PM
(#2998162)
Obligatory plug for Resty:
https://github.com/lukeredpath/LRResty ;)
Re:IOS Boilerplate: A base template for iOS apps
by Greenisus on Wednesday September 14, 2011 @01:59PM
(#2997225)
How is AFNetworking easier than ASIHTTPRequest?
Re:IOS Boilerplate: A base template for iOS apps
by matttthompson on Wednesday September 14, 2011 @02:17PM
(#2997295)
Simple block-based API, significantly less lines of code to accomplish the same tasks, and smaller, more understandable codebase that uses Foundation classes (e.g. NSURLRequest, NSURLResponse, etc.), rather than re-inventing the wheel
And though I don't have the exact numbers, AFNetworking is really fast, maybe 2-3x over ASI in average cases, from my experience and what other users report.
Take a look at the examples in the README and compare that to how you'd do the same in ASI.
Re:IOS Boilerplate: A base template for iOS apps
by hamedh on Wednesday September 14, 2011 @09:20PM
(#2998520)
doesn't ASI also use blocks? its syntax is very similar. but i didn't know about that it's much faster than ASI, thanks for that
The rest of this I could really take or leave. Really wish there was something better than EGOPullToRefresh in wide use...