On Wed, Oct 12, 2011 at 12:32 AM, Loïc Yhuel <[email protected]> wrote: > How would you wrap a QObject* (so it's signals could be invoked, properties > accessed) ? > Dynamically constructing wrapper functions, and sending them as JSON would > be complex, and probably slow.
For those use-cases, we will probably need web process plugins, and communicate with it via messages. WebKit2 already supports that on mac via InjectionBundles API. > Le mercredi 12 octobre 2011 00:08:20, [email protected] a écrit : >> >> I was thinking that you can stringify/parse JSON on either side. Those >> convenience converters are nice sugar, but can be done without. >> ________________________________________ >> From: ext Loïc Yhuel [[email protected]] >> Sent: Tuesday, October 11, 2011 3:05 PM >> To: Rosenthal Noam (Nokia-CTO-Qt/SiliconValley) >> Cc: [email protected]; [email protected] >> Subject: Re: [webkit-qt] API proposal for handling (some) hybrid use cases >> >> I see your examples and prototype code are always using a string as >> message argument. >> Is it possible to use a QVariant like with the QtWebKit bridge ? >> >> If I understand correctly, it won't be possible to implement synchronous >> JS -> C++ calls like Q_INVOKABLE methods. > > > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt > -- Kenneth Rohde Christiansen Senior Engineer Application and Service Frameworks, Nokia Danmark A/S Phone +45 4093 0598 / E-mail kenneth.christiansen at gmail.com http://codeposts.blogspot.com ﹆﹆﹆ _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
