On Thu, Oct 16, 2008 at 3:20 PM, Marshall Greenblatt <[EMAIL PROTECTED]> wrote: > I'm exploring the best way to embed a plug-in within the browser control > where the plug-in is part of the container application instead of being > loaded from a separate DLL. As a simple usage case, consider an application > where the user interface is hosted within an embedded browser window, and > the application-specific functionality is rendered using a plug-in within > that browser window. > > I see two possible approaches for supporting this capability: > > A) Write a custom WebPluginDelegate implementation and return an instance > from WebViewDelegate::CreatePluginDelegate(). > B) Add support for embedded plug-ins to the existing NPAPI framework. > > My personal preference is B, as we could then make use of the plug-in > management capabilities already provided by the NPAPI framework.
Hi Marshall, Can you go into some more specifics about the advantages of (b) over (a), as you see them? At least at first glance, this seems like exactly the sort of thing that the WebPluginDelegate would be great for. --Amanda --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
