On Fri, Jun 11, 2010 at 11:03 AM, Alexander Shabanov <[email protected]>wrote:
> I'm not sure whether it solves your problem or not - but you can use Qt. > > It is shipped with QtWebKit module that provides fully functional > browser components, e.g. renderer, and bundled js engine. > > Native code-to-js bindings in Qt is really simple and straightforward > (in fact there is no need to write glue code, MOC introduces some sort > of "reflection" capabilities to Qt classes what makes them usable from > scripts without writing even a line of binding code). > That is generically true, but last i checked (Qt 4.4, i think) QtWebKit does NOT provide a way for clients to bind to the JS code running in the browser. i was at Qt Dev Days 2 summers ago, where it was explained that the JS engine used in the WebKit code was NOT the same as QtScript, and there was no way for clients to hook into it. Maybe that's been resolved since then. > I heard that Nokia planned to replace their js engine with v8 but I'm > not sure whether it is at least prototyped. > At Qt DevDays i explicitly asked the Qt developers if my QtScript-based code was in any danger of being obsoleted by Qt dropping their QtScript engine in favour of the one in WebKit. i was told "no", and that my QtScript-based code was future-proof. It now seems that they hadn't foreseen the rise of v8. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
