site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com That's my understanding, having never written a Firefix plugin... -- Terry On Jan 3, 2008, at 5:15 PM, John Zorko <jmzorko@mac.com> wrote: Terry, Regards, John, who has to figure out how to do it for Windows next *sigh* Falling You - exploring the beauty of voice and sound http://www.fallingyou.com _______________________________________________ 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... Depending on how integrated you want it to look (e.g. If it opens another application, not very; if it takes over a region of the Safari display, then it's going to look like part of Safari), it could end up being a small stub to launch your app, or your app could be a complete plugin. By going the webkit route, though, that should buy you working with anything that uses webkit, without additional effort. Either way, you should try to partition the code, so you can share as much code as possible between everything, IMO. I am always a fan of less work. 8-). Wow, this helps quite a lot -- many thanks! Since this is WebKit, i'm assuming it's Safari-specific i.e. i'll have to do it a different way for Firefox (XPCOM, here I come)? Go to developer.apple.com and search for WevKitPluginStarter. It has an example of how you support a new MIME type using a plugin. This email sent to site_archiver@lists.apple.com