Hi there, Using QGraphicsWebView is fine and you can always make a QML class out of it, if needed.
I do not know what kind of animations you refer to, CSS3? Are you using accelerated compositing? For effective scrolling/panning you will need to use the tiling feature and the resizesToContents feature. With that you should see improved panning performance, but it might require a bit more work... look at the QtTestBrowser in WebKit... you will find it in the Tools subdirectory. It is a good source of ideas on how to make this work. In order to get a real non-blocking experience you will need to run webkit in another thread or process. This in non-trivial and part of our WebKit2 strategy. This meaning that our current WebKit1 port is mostly feature complete and most mobile related performance work will probably to into our WebKit2 port. If you are interested in what this means you can have a look at my FOSDEM presentation (there are videos somewhere as well) http://www.slideshare.net/kchristi/qt-webkit-going-mobile-7016102 If you are a brave soul, you might even be able to find out webkit2 port on gitorious :-) but you probably want to hold off a bit on using that. Cheers Kenneth On Tue, Apr 12, 2011 at 10:21 PM, Roland Labrecque <[email protected]> wrote: > > I'm trying to clarify some assumptions about the roadmap Qt WebKit moving > forward. Any help would be appreciated. > > We are working on a complex web application for a handheld device(s) which > needs to support orientation changes and we are currently seeing > responsiveness issues when animating/scrolling. > > Current Implementation: > qt-webkit-2.1 > QGraphicsWebView (to support orientation changes). > Custom Pan Gesture (not using QtGesture framework though a similar > approach). > > > So the questions I'm trying to answer > 11vcccccgcgcgcgcgfcgvtfvcccccgtfc2vvvvvvvvvvvvvvvvvvvvvvvcr444455555555sssssSSSSEeaa44dde4dd4ddsw33232eeeeeeeeeeeeeeeeeeeeee4are > for rendering/amimation performance: > > Which version of the technology should perform the best QWebView, > QGraphicsWebView, and QML WebView? > > Now? > 6 Months? > 12 Months? > > So related to this is where is the priority for development? > Will qt-webkit-2.2 impact this? > Will the QML Scene Graph be used to to drastically improve things for QML > WebView (but not for QGraphicWebView and QWebView)? > > > Roland > > > > > > _______________________________________________ > 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
