---- Reported by vinodpatel2006 2008-06-25 21:47:30 ----
This is not the issue but i am requesting an enhancement in the JOGL API.
The problem is that JOGL does not able to render on the browser window. I must
have to use applet to render the 3D objects. But what if i have to render on the
browser window. Rendering on the browser window means i have to use browser
window as the drawable. That is possible using the C++, i can make browser
window as drawable and send all rendering things on that. I can provide the
examples also that this is possible in C++.
I think that if that would be possible in the JOGL then it may be a great
feature and changes the impression of the JOGL.
I am waiting for you decision......
Thanks and Regards
--- Bug imported by email@example.com 2010-03-24 07:51 EDT ---
This bug was previously known as _bug_ 358 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=358
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, firstname.lastname@example.org.
Previous assignee was aaronanderson.
As discussed with Rami and others before,
this might be a big one.
Seamless integration with the windows(*1) of the browser
would need a high grade of interoperability ..
Two solutions I could think of for now:
1) Transparent overlay without decorations
Such a new window could be attached to it's browsers parents
with the right offset.
What would not work properly here is if the target layer
should be invisible.
2) [Offscreen] render into target framebuffer of [sub] window
Assuming all DIV layers are rendered offscreen,
composited by the browser. In case the AWT Applet's browser window
is such an offscreen window, we query this property and follow suite.
More to come ..
*1) browser windows: all windows representing a renderable component,
ie DIV layers - which are somehow stacked and composited by the browser.
translucency support is handled w/ bug #517
*** This bug has been marked as a duplicate of bug 517 ***