[maemo-developers] Qt Mobility 1.1 for Fremantle

[From: Attila Csipa]

On Wednesday 29 December 2010 17:04:21 you wrote:
> Will a similar effort be done for N8x0 folks? Is there any technical
> reason why Diablo should be locked in to qt 4.5.x instead of 4.7.1?

Well, yes and no. You can certainly compile it (in fact at one point I 
compiled 4.7.0 for Diablo myself, but for some reason it was fairly sluggish), 
but there are things that need to be worked on before it makes sense to 
release it onto unsuspecting N8x0 users

1. inputmethod stuff - this is very custom work on 4.5, so those patches need 
to be transplanted carefully

2. the maemo5 module will not be available - IIUC it requires/wraps some 
hildon functionality which is not available on Diablo

3. It's big. I guess most people who had interest in Qt cloned their roots 
already, but it takes up significantly more space than 4.5

4. look into what's causing the performance regression

Otherwise, if I look at it from the QtQuick angle, it's actually fairly OK 
(one of the QtQuick promise is actually observable here - a QML/components 
based application most of the time far easier to port to Diablo with 4.7 than 
a QWidget based  application from Fremantle, performance notwithstanding).

Best regards,
Attila Csipa