89
edits
NPAPI:Pepper: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 13: | Line 13: | ||
A somewhat related issue is how to extend NPAPI to provide platform independent access to new hardware or software features such as webcams, microphones, etc. While certainly important, this is deferred to future discussions. | A somewhat related issue is how to extend NPAPI to provide platform independent access to new hardware or software features such as webcams, microphones, etc. While certainly important, this is deferred to future discussions. | ||
=== Requesting the "Pepper" Platform === | |||
A plugin may call NPN_GetValue() with the following NPNVariable to query the browser whether it supports the Pepper platform: | |||
<pre> | |||
/* TRUE if the browser supports the Pepper platform */ | |||
NPNVsupportsPepperBool = xxxx | |||
</pre> | |||
Once the plugin finds a supported drawing model, it calls NPN_SetValue() to tell the browser which drawing model it will use. We're using the NPNVariable used for Mac drawing model for this: | |||
<pre> | |||
NPNVpluginUsePepperPlatform = xxxx /* TRUE if we should use the Pepper platform */ | |||
</pre> | |||
== Out of process plugins == | == Out of process plugins == | ||
| Line 58: | Line 73: | ||
This proposal is clearer at this moment regarding 2D graphics. We expect we may need to pass some state (2d vs. 3d, hardware vs. raster, etc.) in through other calls and/or with some extensions to the data structures we propose below. | This proposal is clearer at this moment regarding 2D graphics. We expect we may need to pass some state (2d vs. 3d, hardware vs. raster, etc.) in through other calls and/or with some extensions to the data structures we propose below. | ||
=== An Example === | === An Example === | ||
| Line 183: | Line 175: | ||
Plugins should receive all their events from NPP_HandleEvent. We believe that standardizing the event types and payloads based on, for example, DOM events, would be sufficient to provide browser and OS independent events. If not, the goal can be accomplished by possibly extending the set of event types or data on the event structures to convey more information. | Plugins should receive all their events from NPP_HandleEvent. We believe that standardizing the event types and payloads based on, for example, DOM events, would be sufficient to provide browser and OS independent events. If not, the goal can be accomplished by possibly extending the set of event types or data on the event structures to convey more information. | ||
== Plugin Registration == | == Plugin Registration == | ||