NPAPI:DrawImage: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
= Problem Summary =
= Status =


It is very painful to render plugin content to non-X surfaces on Linux using X11. (For Mozilla if MOZ_X11 is defined then HandleEvent is operating with XEvent's).
Under consideration.
When browser renders its content into a memory buffer or to some other surface (Qt::RasterPaintEngine/cairo-image-surface which are not very friendly to X), then we are forced to do data moving X-client-X...


= Proposal =
= Contributors =


I propose an NPAPI DrawImage event type which would allow a plugin to render directly into an image memory buffer, without involving X-Surface.
* Last modified: April 27, 2010
* Authors: Oleg Romashin (Nokia), Josh Aas (Mozilla)
* Contributors:
 
= Overview =
 
This drawing model allows plugins to draw into a buffer.
 
= Event Model Requirements =
 
This drawing model is currently compatible with the following event models:
 
* [[NPAPI:ExtendedXEventModel|Extended X Event Model]]
 
While this is currently only compatible with the extended X event model, this could change. This drawing model was designed to work on any platform.
 
= NPDrawingModelX =
 
As this will be the first alternative to the default X drawing model, we'll designate the original model:
 
* NPDrawingModelX (NPDrawingModel = 4)
* NPNVsupportsXDrawingBool (NPNVariable = 2004)
 
= NPDrawingModelDrawImage =
 
For documentation on negotiating drawing models, see [[NPAPI:Models]]. The drawing model variables for draw image events are:
 
* NPDrawingModelDrawImage (NPDrawingModel = 5)
* NPNVsupportsDrawImageBool (NPNVariable = 3005)
 
= Event Structure =


= Drawing Image Event =
= Drawing Image Event =
Confirmed users, Bureaucrats and Sysops emeriti
1,680

edits

Navigation menu