Summary: | Rendering on the browser.... | ||
---|---|---|---|
Product: | [JogAmp] Jogl | Reporter: | Sven Gothel <sgothel> |
Component: | applet | Assignee: | Sven Gothel <sgothel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 1 | ||
Hardware: | All | ||
OS: | all | ||
Type: | FEATURE | SCM Refs: | |
Workaround: | --- |
Description
Sven Gothel
2010-03-24 07:51:30 CET
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. |