Quote Originally Posted by anda_skoa View Post
Hmm, so the difference is that, behavior wise, the web engine bridge did pre-load the equivalent of qwebchannel.js?

I am not really into the web technologies, but can't you do the same by loading an "environment page" using setHtml() which then loads the actual content?

Cheers,
_
In theory, provided we didn't clobber anything and the index.html file didn't get horribly complex. The bridge approach was cleaner. Only two teams had to be coordinated for an injection approach. The C++ developers and the Javascript developers. Adding a file requires coordinating 4-5 teams because now source control, build, deployment, and static html groups all have to be involved. At any rate, late last night they opted to go with the webchannel route because the cheat of using the title and clipboard was going to be limiting potential enhancements down the road.

Let the slow journey begin.