PunchScrollView hosted on github is a ScrollView framework for iOS (iPhone, iPad and iPod Touch) which works like the Apple UITableView framework
Easy and fast implementation, almost like the UITableViewUse the benefits of the NSIndexPath like you might know it from the UITableViewEasy setup in combination with Core DataHelpful methods, i.e. jump or scroll to a desired pageAvoid boilerplate codeSave lots of memory with the use of dequeuingPunchScrollView GitHub
RestKit is an Objective-C framework for iOS that aims to make interacting with RESTful web services simple, fast and fun. It combines a clean, simple HTTP request/response API with a powerful object mapping system that reduces the amount of code you need to write to get stuff done.
What about the AFCache API? Why do I would use it?
The AFCache API has some convenience methods that care about receiving data, parsing headers, storing data, error handling, etc. See CacheableItemDemoController.m for basic usage.
I guess I'm confused as to what AFCache actually does.
Basically it stores NSURLResponses on disk and serves them from there on subsequent requests. AFCache checks for freshness of the file. If the cached file on disk is outdated, AFCache transparently updates it and gives you the new version. I wrote AFCache because on iPhone, NSURLCache doesn't write to disk. In the last months AFCache has evolved to something like a cache package management tool. You may package a bunch of files on the server (via the afcpkg commandline tool), request this package from your client and prefill the cache instead of doing many requests for small files. One uses case would be a digital magazine issue downloaded into the cache (e.g. for offline reading).
You can do it now, starting with XCode 4.2 for iOS5 beta 4
From command line, you can run instruments pointing to the automation template and specify as environment variables the test script you want to execute and destination path for results:
// jump to the app store to manage your renewable products NSURL *url = [NSURL URLWithString:@"itmss://buy.itunes.apple.com/WebObjects/MZFinance.woa/wa/manageSubscriptions"];
[[UIApplication sharedApplication] openURL:url];
Die Zukunft der Unterhaltungselektronik ist mobil. Samsung etwa macht immer weniger Gewinn mit PCs und erzielt dafür traumhafte Umsätze mit Smartphones. Tablets haben sich zumindest für Apple zu einem Verkaufserfolg entwickelt. Den Markt für mobile Betriebssysteme führen derzeit Android und iOS an – wenn man Nokias sterbendes System Symbian außen vor lässt. Dahinter klafft mittlerweile ein Loch, und viel Ernüchterung hat sich breit gemacht. HP hat es noch nicht geschafft, mit seinem von Palm übernommenen Betriebssystem WebOS einen signifikanten Marktanteil zu erobern, bei Blackberry-Hersteller RIM herrscht nach der jüngsten Ergebnisprognose Rätselraten und Microsoft übt sich in Selbstkritik.
We now had to implement some CRON jobs which runs every day: every day
we make a list of passes which are supposed to expire, and we ask
Apple if the original receipt is still valid: the magic thing is that
in their answer, there is a field latest-receipt which embeds the
latest receipt. If it is not the same as the one we have, we
understand that the subscription has been renewed automatically, we
store the latest receipt for the next cron check, and we update the
user account to extend the expiration date.
The olloclip(TM) is a quick-connect lens solution for the iPhone 4 that includes a fisheye, wide-angle and macro lens in one small, convenient package that easily fits in your pocket. Nestled in the palm of your hand, the olloclip connects to the iPhone within 2 seconds so you’ll be sure to capture the image you want…if you don’t see the picture you’re looking for just flip it over and switch the lens.
Computing cryptographic hashes of files on iOS and Mac OS X using the CommonCrypto APIs is fairly easy, but doing it in a way that minimizes memory consumption even with large files can be a little more difficult… The other day, I was reading what some people were saying about this on a forum about iPhone development, and they thought they found the trick, but they still had a growing memory footprint with large files because they forgot something fundamental about memory management in Cocoa.
Even though they had a solution to read bytes from the file progressively instead of reading everything at once, it did not improve the memory consumption of their program when computing hashes of large files. The mistake they made is that the bytes read in the while loop were in an autoreleased instance of NSData. So, unless they create a local autorelease pool within the while loop, the memory will just accumulate, until the next autorelease pool is drained. But I think it would be very ineffic…
Simply put, appFigures is a reporting platform for iPhone developers that automatically downloads and visualizes iTunes Connect sales data with App Store reviews and ranks for all of their apps. Detailed ReportsConquer your data with reports that simply make sense.Daily Email ReportsYour reports come directly into your inbox - every day.Hourly RanksSee how your app is doing in App Stores around the globe.Translated ReviewsReviews from all App Stores in the language of your choice.appFigures