To understand a bit more how Qt WRT works I started playing with example widgets. Nothing fancy: just some plain simple stuff.
A framework that I find great is "jQTouch":http://www.jqtouch.com/: it's just plain cool. So I decided to take one of their examples (the "clock") and pack it into a .wgt, to see how Qt WRT behaves.
Functionality wise, I think all went smooth. But rendering wise, I think it highlights some of the problems of Qt WRT and how the WebView rendering is setup.
!http://img842.imageshack.us/img842/9905/iphonerendering.png(iPhone rendering of jQTouch Clock example)!
!http://img207.imageshack.us/img207/1488/qtwrtrendering.png(The same example, packed in a .wgt, and running in Qt WRT)!
As you can surely see, there are at least 2 problems in the rendering:
- Coloring: The gradient doesn't show up smoothly. I guess it's a matter of how many color the Scratchbox + Xephyr thing puts on the screen.
- Rotating element: The clock uses 3 images representing the "legs of the clock", and rotates them using WebKit rotations. You can see the low quality of the Qt WRT rendering of the rotated image
Any comment from the Nokia guys? I'm sure you know about this, but just in case I'm reporting you. I must occupy somehow my time while "you write the doc":http://developer.qt.nokia.com/forums/viewthread/301/#1516 ;)
I'd like to point out that the WebKit animation/transformation that jQTouch builds on the top of WebKit goodness seems to work. Not smoothly, but work. And that's a great sign.