On Jun 22, 2010, at 4:36 PM, Bill Appleton wrote: > all that stuff in the docs you mention is about interacting with the browser > > now the browser is a whole separate application, its talking to the > WebKitPluginHost through ports > > so thats what they are talking about -- if you want a popup menu on the > browser screen you have to call their API > > but invoking an open file dialog from a plugin should be fine, its all a > separate window ,separate process etc. > > this is much more solid than the carbon/quickdraw/x manager stuff we used to > use
The section of the Apple docs that I linked to was specifically talking about out-of-process plug-ins on Mac OS X 10.6 64-bit. http://developer.apple.com/mac/library/documentation/InternetWeb/Conceptual/WebKit_PluginProgTopic/Tasks/NetscapePlugins.html#//apple_ref/doc/uid/30001250-DontLinkElementID_1 You get a separate process for your plug-in, but there is no guarantee that that process will have a full Cocoa environment running. You are recommended to use only plug-in APIs as much as possible, and not to spawn new windows. Charles_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
