- Using a RR QT player object plus the Enhanced RR QT external for accessing the QT content; when JavaScript calls were still allowed from within QT content, could they be made in this QT player object scenario ? If yes, what are the plans to overcome those newly introduced QT player restrictions (no Flash content, no JavaScript calls) ?
- Embed a QT movie within a web page and consume it using the revBrowser plugin; does this RR solution offer any (security) advantages over web page embedded (QT) player content browsed via the contemporary standard browsers ?
It is my intention to serve AxelEdge-generated 3D content to the (RR) community; and I thought using the first path (RR QT player object + Enhanced RR QT external) could offer (security) benefits over using the second path (web page embedding + RR revBrowser plugin). BUT: Now that the QT player does NOT support JavaScript calls any longer, I have to reconsider this strategy.
I have come to the conclusion that I would have to use the following:
- Native Axel player movie embedded within a web page (the Axel player can still make calls to JavaScript)
- Consume that web page using the RR revBrowser plugin
The question is if such a solution will be accepted by the RR community:
- Will they install the IE Axel player plugin for example ? The installation is a seamless procedure ...

- Are possible calls to JavaScript from the web page embedded Axel player object more secure when consumed by the revBrowser plugin compared to consumption by regular browsers (see above) ?
I would be pleased to hear about the RR way to go with regard to QT and Axel 3D content - or QT, Flash and 3D content in general, for that matter.