From: Schuyler, D. <Dav...@di...> - 2002-02-28 01:40:53
|
Hi, Yeah, Greg Humphreys mentioned some similar ideas outside of the list. I don't think I'm the one to write a tee spu, and I don't think it will do what I'm looking for. I'm looking to have a couple of local windows (rendering scenes 'a' and 'b', for example) and have a half dozen chromium render servers (rendering scenes 'c', 'd', 'e', 'f', 'g', and 'h'). In this setup, none of the scenes would be the same data (well the world might be the same, but all the camera/viewports would be different). -----Original Message----- From: Sean Ahern [mailto:sea...@ll...] Sent: Wednesday, February 27, 2002 5:22 PM To: chr...@li... Subject: Re: [Chromium-dev] Native and Chromium Brian Paul wrote: > "Schuyler, Dave" wrote: > > Every now and then I come across code in chromium that talks about > > rendering to a native window or a chromium window. Does anyone have an > > example of rendering to a local/native window and a chromium window > > from within the same app (at the same time)? > > None of the Chromium demos do that. One thing that I'd like to see someday along these lines is the following: I want to put together a "tee" SPU, hooked up to a render SPU and a tilesort SPU, all three within a client node. The tilesorter would distribute primitives on the network like normal. tilesort -/\/- network / App - tee \ render The render SPU would be told to use the application's window for rendering, rather than creating its own. All OpenGL submitted by the client would then appear both in its normal window and also wherever the tilesorter was configured to go. This is theoretically possible, though I've heard some stumbling blocks discussed here. I seem to recall someone mentioning that having the renderspu display to a window that's not its own has problems under Windows. I don't know that there aren't symbol lookup issues with a tee spu. While I'm dreaming... the holy grail would be to have the render SPU accept imagery from something else, probably out of band. This would allow scalable remote rendering and compositing, with the final image displayed back into the app without the user even having to know that Chromium's doing the acceleration. A few of us have talked about this before, and have identified that there are a number of roadblocks. But it's a nice dream for now! -Sean __ sea...@ll... God bless America. And shed His Grace on thee. _______________________________________________ Chromium-dev mailing list Chr...@li... https://lists.sourceforge.net/lists/listinfo/chromium-dev |