Hi all,
I'm on a team writing a windowless npapi (browser) plug-in. Such plug-
ins don't let you have a window to draw into, just an offscreen pixbuf
that the browser blits to the main browser window.
We also need to use Clutter as an underlying technology, but we can't
offer an on-screen window for Clutter to use for a stage.
I gather the ClutterOffscreen container proposed for Bug 1573 requires
an on-screen stage window - if so, it won't work for us.
So I'm thinking of writing a ClutterOffscreenStage. This would
subclass ClutterStage, accept normal ClutterActors as children, but
render to an offscreen pixbuffer (which can be platform-specific).
Oh, and whatever I do needs to work on GLX and EGLX in the next two
weeks. :-) Fortunately, I have full time to work on that, and lots of
good coffee available.
So I'd be very grateful for advice, reality-checks, comments,
alternatives, suggestions, etc. Anybody who helps will get a hearty
handshake and a free beer, whiskey, coffee, tea, soft drink, or other
beverage of their choice at the next FOSS conference we're both at.
Thanks,
Bob
P.S. Here are some things I'm thinking about this so far, and would
appreciate corrections and advice from people who know more than I do:
It seems to me that an offscreen stage is necessary to build a
completely offscreen scene graph, without any on-screen window, and
render it into an offscreen pixbuf. Is this correct? Or is there
another, simpler way to accomplish those goals?
I'd like to do this without doing any backend-specific code. But it
doesn't look like that's feasible. Is that right?
Many ClutterStage implementation details are done in the back-ends. So
ClutterOffscreenStage would need to do the same thing. Is that right?
Do any of the ClutterActors make assumptions, like about being on-
screen, that would cause problems if they were embedded in a
ClutterOffscreenStage?
--
To unsubscribe send a mail to [email protected]
