On Thu, Mar 5, 2009 at 8:59 PM, eager_learner <[email protected]>wrote:
> > Hello Plugin Gurus > > The following link is very well written and I hope it still holds good > > http://sites.google.com/a/chromium.org/dev/developers/design-documents/plugin-architecture > > I have some followup questions on plugin development (internal) > > 1. Based on the plugin architecture design document, can you point me > to an existing plugin (flash, shockwave, activeX) code file names? The > source Navigator project that I have created does not show any > inheritance of WebPplugin I think there's some confusion between the internal Chrome classes used to implement multi-process plugins, and the NPAPI APIs that are exposed by any plugin (external or internal). > > > 2. Again the debugging process seems a little difficult if new > processes are spawned (one for the browser, one for the renderer and > one for the plugin). How can we attach Visual Studio to the plugin? Start chrome with --renderer-startup-dialog and/or --plugin-startup-dialog to have a message box load on process startup, then you can attach VS. > > > 3. Do plugin writers need to know anything about the class > PluginInstance? It seems to create the WebPlugin or atleast gets > passed it and has a reference to it. No it's internal to the plugin implementation. > > > Simply put, what needs to be done by plugin developers to develop an > internal plugin? Have a look at plugin_list.cc, specifically the constructor which adds default_plugin. The main thing to look at is how it maps the three NPAPI methods (NP_GetEntryPoints/NP_Initialize/NP_Shutdown) to functions that are linked in the same binary. > Does the NPAPI need to know about the PluginInstance? No > > > Perhaps there is a clearer document that explains this. > > Thanks > Vijay > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
