<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 09.09.2010, at 02:57, John M McIntosh wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div>The fastest way is to go from Quicktime to Open/GL viewport overlaying the squeak window. But then you loose any ability for squeak to alter the bits since it never sees them. </div></div></div></div></blockquote><br></div><div>The best way would be to give the bits to Squeak only if it asks for them. The UI could then enable fast overlay rendering while the video is unobscured, and switch to slow bitblt rendering when needed. It might be tricky to make the transition be seamless, but it is the only way to have our cake and eat it too.</div><div><br></div><div>Well, unless we switch to a layered rendering model where the VM does the compositing. Now that would be neat :) Though we'd still need access to the composited frame buffer for things like color picking and Etoys color tests. </div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Lucida Grande; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><div style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; ">- Bert -</span></div><br class="Apple-interchange-newline"></span>
</div>
<br></body></html>