From: <ma...@co...> - 2005-06-09 20:56:36
|
Mike, You're right - that is an advantage of the render-to-app-window feature. I think in general, if my changes get back into the tree, we'd just have to make sure users understand the tradeoffs between one way and the other. > It's still very useful for tiled display work however... Probably the #1 use for Chromium right now... right? Anyway, thanks for your input! What would be a good name for an ENV variable to toggle "my" new feature. Jon Quoting mho...@gr...: > I think you might be misunderstanding the purpose of render-to-app-window. > What you have built is effectively a "T" SPU. Allowing the window to be > drawn by the original app as well as feed the Chromium SPUs. > render-to-app-window as currently written means that after the stream has > gone through transformations, the render spu will use the original app > window to render to instead of putting up it's own window. For example, > you might use Chromium to change the colors of vertices in the > application, and instead of rendering to a separate window, you want to > replace the original app's rendering. > > What you have made has actually been requested by many in the past. The > main issue with your approach is that it will show the app rendering prior > to stream tranformations. It's still very useful for tiled display work > however... > > -Mike > |