Zip. WebSocket. Index | NodObjC v0.0.11. NodObjC is the bridge between NodeJS and the Objective-C runtime and frameworks, making it possible to write native Cocoa applications (both GUI and command-line) using 100% NodeJS. Applications are written entirely in JavaScript and interpreted at runtime. Getting Started Every NodObjC application begins with requiring the NodObjC module.
You can name the returned module variable anything you want, but the "canonical" name for it is $. This is mostly because you're going to be using the variable all over the place, and probably want to keep it short. var $ = require('NodObjC') The next step is to import() a desired "Framework" that is installed on the system. . $.import('Foundation') import() doesn't return anything, however it will throw an Error if anything goes wrong. A lot of core classes expect an NSAutoreleasePool instance on the stack, so the first Objective-C object instance you create is usually one of those. var pool = $.NSAutoreleasePool('alloc')('init') Pretty simple! More Docs. AFNetworking. Restkit. ASIHTTPRequest. ASIHTTPRequest is an easy to use wrapper around the CFNetwork API that makes some of the more tedious aspects of communicating with web servers easier. It is written in Objective-C and works in both Mac OS X and iPhone applications.
It is suitable performing basic HTTP requests and interacting with REST-based services (GET / POST / PUT / DELETE). The included ASIFormDataRequest subclass makes it easy to submit POST data and files using multipart/form-data. Features ASIHTTPRequest comes with a example applications for Mac and iPhone that demonstrate some of the features.
ASIHTTPRequest is partly based on code from Apple’s ImageClient code samples, so if it doesn’t meet your needs, take a look at their CFNetwork examples for more. ASIHTTPRequest is compatible with Mac OS 10.5 or later, and iOS 3.0 or later. NSURLCache Class Reference. Overview The NSURLCache class implements the caching of responses to URL load requests by mapping NSURLRequest objects to NSCachedURLResponse objects. It provides a composite in-memory and on-disk cache, and lets you manipulate the sizes of both the in-memory and on-disk portions. You can also control the path where cache data is stored persistently. Class Methods setSharedURLCache: Sets the shared NSURLCache instance to a specified cache object. + (void)setSharedURLCache:(NSURLCache *)cache Parameters cache The cache object to use as the shared cache object.
Discussion An application that has special caching requirements or constraints should use this method to specify an NSURLCache instance with customized cache settings. Availability Available in OS X v10.2 with Safari 1.0 installed.Available in OS X v10.2.7 and later. Declared In sharedURLCache Returns the shared NSURLCache instance. + (NSURLCache *)sharedURLCache Return Value The shared NSURLCache instance. Instance Methods cachedResponseForRequest: PSURLCache/PSURLCache.m at master · ptshih/PSURLCache. Rs/SDURLCache. Oauth. JSON. XMPP Framework. MailCore. Remail-iphone. ReMail downloads all your email to your iPhone and searches it instantly. reMail was acquired by Google in February of 2010, and we've decided open source the product: Read the reMail open source announcement for details Here's a a list of products based on reMail open souce code. You will need a Mac to do this. Install the following: Clone the repository: $ hg clone Note: do this in a path that has no spaces.
Open a terminal, cd into the source directory. . $ sh pull_dependencies.sh This can take up to an hour. Open ReMailIPhone.xcodeproject Click "Build and Debug" You should consider following the author, @gabor for occasional reMail updates. If you want to release your own, rebranded version of reMail in the App Store, read RebrandingRemail. These are inspired by the top recent feature requests.
See ProjectIdeaDetails for more. No. Here's a rough overview of the data flow in reMail: There is a central contacts db which is used to autocomplete names.