Qt WebKit

The approach I'm now working on is using process spawning to avoid this problem. Basically, I construct a separate process which creates a shared memory segment (QSharedMemory), and writes output to stdout. The shared memory segment is a data channel (containing the RGBA buffer for a QPainter), and stdout is the command channel (e.g. pick up freshly rendered content on this qrect). The main process connects to this shared memory segment using QSharedMemory, and instantiates the process with QProcess. Because I need Win32 compatibility, I need to suck the big one and create a new process every time a web page is spun-up - using a new QProcess instance. On unix, however, I believe that one could create one main process and call fork() every time a new web view is required. This would allow the parent process to do much of the setup work prior to forking, thus an efficiency gain. If you are on unix you may be able to use this approach. Unfortunately, I can't see how Javascript can be viewed as a serious language - and I can't understand why this language is being chosen for the basis of QML. I only see a lot of pain for developers trying to get their systems reliable with that approach. Alternatively, they'll be back to forking processes for reliability and threading - back to early 1990's :) -bms

thanks a lot . you are right

I stumbled on to http://developer.qt.nokia.com/wiki/Using_QtWebKit_and_QML_with_PySide But is there a method to skip python and use c++ or qml to access the javascript context in qtwebview? Can someone give me a hint? Thanks

Q_INVOKABLE seems to not work. But the Q_PROPERTY sample is ok for me too: @QVariant BusinessProxy::lineUp() { qDebug() << this->objectName() << ": lineUp called"; QVariant var(QMetaType::QObjectStar); var.setValue((QObject*)m_lineUp); return var; }@ with into the constructor: @m_lineUp = new DBusLineUp("com.orange.device.BusinessLayerService", "/LineUp", connection, this); m_lineUp->setObjectName("lineUp");@ And into the header: @ Q_OBJECT Q_PROPERTY(QVariant lineUp READ lineUp) public: QVariant lineUp(); private: DBusLineUp *m_lineUp;@ But I didn't put any 'qRegisterMetaType': I used the 'addToJavaScriptWindowObject' way

I also just found "this blog post":http://qtwebkit.blogspot.com/2010/10/texture-mapper-accelerated-compositing.html explaining some of the plans for how future versions of QtWebKit will do hardware acceleration. Apparently they are moving to a TextureMapper based approach rather than QGraphicsView. I hope this helps and isn't too much technical detail for what you wanted.

or is there any ways I can get webkit2 into qt myself?

I think it is related with HTML5 local storage (http://diveintohtml5.org/storage.html) support ... Anyone could provide any tip about how to activate it in QML? In PySide it would be something like this: @mSettings = mWebView.settings() mSettings.setAttribute(QWebSettings.LocalStorageEnabled, True) mSettings.setAttribute(QWebSettings.OfflineStorageDatabaseEnabled, True) mSettings.setAttribute(QWebSettings.OfflineWebApplicationCacheEnabled, True) mSettings.enablePersistentStorage(path=sys.path[0])@

help needed ..