site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Sep 23, 2008, at 2:49 PM, David M. Cotter wrote: here you go: http://www.martinkahr.com/2007/07/26/remote-control-wrapper-20/index.html just food for thought, Jaime Magiera Sensory Research http://www.sensoryresearch.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... Yeah, I've seen this and also done some reverse engineering myself. However, it's not the same thing as having a true public API. With a public API things are standardized and somewhat frozen. Playing with unsupported/non-public API is playing with fire if you want your app to be solid in the commercial market. If Apple decides to change something, you could be left without recourse. I speak from experience. For a while I was working for a company whom used unsupported ways of inserting applescript dictionaries into applications. Things changed between Tiger and Leopard, and that functionality is now hosed. Avoiding such situations is probably a sound business and technical decision. This email sent to site_archiver@lists.apple.com