Projects tagged ‘cocoa’ and ‘iphone’

Here is a simple class that allows you to transfer files via WebDAV. Inside it uses: CFNetwork for HTTP/HTTPS connections. Streams for reading and writing files. NSXMLParser for parsing WebDAV ... [More] responses. Known Issues and Future plans: At the moment it doesn't provide anything unrelated to file transferring. It doesn't support resuming upload/download and timeout handling yet, but I'm working on this. No documentation yet, and not many comments in the code. However, there is a simple example for the iPhone platform. [Less]

CocoaAsyncSocket supports TCP and UDP. The AsyncSocket class is for TCP, and the AsyncUdpSocket class is for UDP. Each class is described below. AsyncSocket is a TCP/IP socket networking library ... [More] that wraps CFSocket and CFStream. It offers asynchronous operation, and a native cocoa class complete with delegate support. Here are the key features: Queued non-blocking reads and writes, with optional timeouts. You tell it what to read or write, and it will call you when it's done. Automatic socket acceptance. If you tell it to accept connections, it will call you with new instances of itself for each connection. You can, of course, disconnect them immediately. Delegate support. Errors, connections, accepts, read completions, write completions, progress, and disconnections all result in a call to your delegate method. Run-loop based, not thread based. Although you can use it on main or worker threads, you don't have to. It calls the delegate methods asynchronously using NSRunLoop. The delegate methods include a socket parameter, allowing you to distinguish between many instances. Self-contained in one class. You don't need to muck around with streams or sockets. The class handles all of that. Support for TCP streams over IPv4 and IPv6. The library is public domain, originally written by Dustin Voss. Now available in a public setting to allow and encourage its continued support. AsyncUdpSocket is a UDP/IP socket networking library that wraps CFSocket. It works almost exactly like the TCP version, but is designed specifically for UDP. This includes queued non-blocking send/receive operations, full delegate support, run-loop based, self-contained class, and support for IPv4 and IPv6. [Less]

The goal is to create an NSXML style API that can used in environments without NSXML (e.g. iPhone). KissXML was inspired by the TouchXML project, but was created to add full support for generating XML as well as supporting the entire NSXML API.

Google Toolbox for MacA collection of source from different Google projects that may be of use to developers working other Mac projects. Also includes the Google Developer Spotlight Importers. To ... [More] browse the Google Toolbox for Mac source code, visit the Source tab. Library changes are documented in the release notes. If you find a problem/bug or want a new feature to be included in the Google Toolbox for Mac, please join the discussion group or submit an issue. Google Toolbox for Mac follows the Google Objective-C Style Guide. [Less]

This is a class browser for the Objective-C runtime on Mac OS X. It gives you full access to all classes loaded in the runtime; allows you to dynamically load new modules and their classes; shows ... [More] every method implemented on each class; and displays information in a header (.h) file format. We have found this to be a useful development tool. Please note, however, that each user is responsible for their own usage. The original version was released in April 2002 by Ezra Epstein. Nicolas Seriot upgraded the code to support Mac OS X 10.5, Objective-C 2.0 and syntax colorization. An iPhone version is also available. [Less]

This sample iPhone application demonstrates how to use the GData API Objective-C library to log in, upload, download and rename files in Google Docs, including support for documents inside multiple ... [More] levels of folders. There are two ways to use the code. First, the GoogleDocs.m/.h can be used as-is and plugged into an iPhone app. It should also work in a Mac OS X Cocoa app with little or no changes needed. Second, GoogleDocs.m/.h shows an example of how to use various aspects of the GData Objective-C API. By seeing how this code works, a developer can learn the underlying API to create their own interface. Additionally, the code demonstrates a method for packing up binary/non-user editable data files and uploading them as HTML files, then downloading and decoding the original content. The sample application fully exercises the included interface in an app that will run on an iPhone, iPod Touch and the iPhone Simulator. [Less]

A few things you may be able to use. Enjoy!

OverviewWhenever iTunes syncs with an iPhone, it creates a backup of the files on the device. This backup is stored in: ~/Library/Application Support/MobileSync/Backup It can be interesting to ... [More] look at these backups, but a bit of work is necessary to get access to them. I've whipped up a quick and dirty application to display the most common cases, iPhone Backup Slurper. mdbackup FilesThe files themselves are named with what appears to be a hex representation of a UUID with the extension "mdbackup". One of these files corresponds to a single filesytem entry on the iPhone. The file is just a standard plist, with binary encoding. You can convert this to a text file using plutil -convert -o The plist contains the following keys: Domain: The scope of the file. Options are "HomeDomain", "LibraryDomain", or a specific application bundleID. Path: The path within the domain where the file is stored on the iPhone. Data: The contents of the file. I assume that this is data-fork only, if the iPhone supports multiple forks. The file can be any arbitrary kind of file, but in practice, there are only a few different types of files that developers seem to actually be saving in the filesystem. The app reads in the plist, displays the metadata keys described above, and does some heuristics on the data to try to guess how to display it. The most common cases I found by browsing my own backup directory were: text file plist saved as a string file binary plist image zip file sqlite 3 database completion dictionary iPhone Backup Slurper will print any of these out to a descriptive file when it encounters them. If the backup contains an image, it will display the image. For a zip file, it will display the filenames embedded in the zip. It will dump the contents of an SQLite database. There are two pathological cases I found while playing with this that I couldn't figure out how to handle. First, there are some files that appear to be SQLite 3 databases – the file begins with the string "SQLite format 3". But the version of SQLite 3 included with Leopard 10.5.5 gawks when trying to read them. Second are the audio files bundled with Tap Tap Revolution. The Quicktime APIs don't recognize them as valid m4a files. Maybe they're actually something different. Manifest FilesThe backup directory also contains a plist named "Manifest.plist". This is a manifest of all of the mdbackup files in the same directory. iPhone Backup Slurper can also display the contents of this file by choosing Open Manifest from the File menu. The manifest contains the following key/value pairs: AuthVersion: The current version of this file. AuthData: The string "Forty Two" encoded as hex without a null terminator. AuthSignature: The SHA1 signature of the "Data" key. Data: The actual manifest stored as a binary plist. The manifest itself is just a listing of all of the applications on the phone, with the files for each, and a separate listing of each file's attributes. Specifically, these are the keys: Applications: A list of each application, keyed by the applications' bundle identifiers. DeviceId: The device that this manifest is intended to be used with. Files: A list of each of the files in the backup directory, keyed by the file's UUID. Each entry contains filesystem attributes for the file and a DataHash to ensure data integrity. I don't know the hash algorithm used by the data hash, but I suspect it's something tricky that uses the "Forty Two" value mentioned above as a hash seed. ConclusionI hope iPhone Backup Slurper is useful to people or just fun for exploration! If nothing else, it's a good example of using a bunch of different APIs to parse different filetypes. Finally, I'm indebted to OmniGroup for their useful OSLDatabaseController sqlite wrapper class. [Less]

FSKit is a Cocoa framework to help Mac OS X applications access the FamilySearch.org public web service APIs. NEW FSKit now works on the iPhone iPhone search screenshot demo movie FSKit is still ... [More] in early development, and needs feedback and help with development. Please look at the initial code and sample app and provide feedback as to architecture, structure, usefulness, etc. and we would gratefully appreciate your code contributions as well. Lets make FSKit a great API for the next generation of Macintosh and iPhone genealogy applications! Introduction Roadmap NEW The slides from the 2009 FamilySearch Developers Conference on March 11, 2009 are now available. [Less]

This tictactoe game is based off of the original "itictactoe" a few modifications and a bunch of comments have made it for the .30 toolchain and great as a beginner app along with the HelloWorld App. 10-1-07 Started