ModRana postpones screen blanking every 60 seconds, so that the screen stays on when you are using it. Looks like the Qt API for this (QScreenSaver I think ?) not only does this, but also unlocks the screen.

A check if the screen is locked will probably need to be added to the code.

There were some issues with segfaults caused by both GTK & GObject stuff and Qt stuff being loaded by modRana, but I think I have already fixed that one.

So this might be unrelated and quite possibly the cause can be somewhere inside Qt or PySide - BTW, someone got an idea how to debug a library that makes a Python application using it segfault ?

OK, noted.

Yeah, it shouldn't be that difficult.

At least short term, I plan to concentrate at the QML GUI to get it to feature parity with the GTK one. As I'll be also improving the general modRana data models while doing this, the GTK GUI should also benefit from this quite a bit.

BTW, at a glance, some + and - for the GTK and QML GUI:

GTK
+ has the most features
+ works even without CSSU
+ works on desktop (but is not very desktop like )
+ has the most features at the moment

- quite tedious to add new features due to lowlevel implementation
(The GTK GUI is written in Cairo, so for everynew layour or special button you
have to actually tell Cairo which lines, glyphcs and rectangles to draw and on which coordinates. You have a full control over the graphics, but it is really quite tedious. )
- no hardware acceleration, everything runs on CPU
-> the whole screen is redrawn every time (due to using Cairo for everything)
-> no kinetic scrolling
(well, there is this, integrating it with the fullscreen-Cairo-widget might be an issue)
- very old GTK version (not that big of a problem actually)
-> how long will be GTK 2 supported on desktop ?
- bad support for more recent mobile operating systems
-> basically no support for anything non-X
-> this rules out Android, BB10, etc.


QML
+ very fast and easy for UI development
-> mainly due to the build in elements and property bindings
(bindings save a HUGE amount of code)
+ fast, even on the N900
-> even the built-in Javascript interpreter is surprisingly fast
+ kinetic scrolling and animations are not a problem
+ good multi platform support
-> Harmattan, Android, BB10, etc.
(BTW, I have basically all I need to start making modRana packages for Android and later BB10 (BB10 has Python 3.2, which complicates things a bit))

- stability issues on the N900
-> also requires CSSU for proper functionality (PR 1.3 Qt is too outdated)
-> and that issue with loading two GUI libs to RAM
- Qt Components are usually unavailable on desktop
-> makes running the QML GUI on desktop problematic
- no Python bindings that support new Qt5 features
-> there seems to be some progress from both PyQt and PySide, but not timetable just yet
- QML/QtQuick lacks some important features and sometimes feels a little unpolished
-> no programmable imports (which is problematic if you want to support multiple component sets)
-> no really asynchronous image loading interface (the current implementation triggered by setting the async flag for Image is severally lacking)
-> no control over the image cache, no explicit cached image reloading
-> issues with nested data models
-> the PySide bindings sometimes have issue, for example with nested data models or automatic QObject wrapping