OK, testing report...

1°) Portability

The good news is that GRead definitely still runs on Diablo, even though there are now two incompatible Qt APIs instead of one, and thus two files that need tweaking :

- of course the two InputMethodHint calls on LineEdits are still there, in Ui_settings

- the older Qt on Diablo doesn't know about QPropertyAnimation either, so in src/views/basic/__init__.py I had to comment out everything related to "self.banner_animation" in several places (thanks, PyGtkEditor ! :-).

After that the app runs just fine, with only a cryptic warning at startup about a conflict between QGtkStyle and the GTK_Qt engine...


2°) Usability

Everything works, but there are a few issues due to the differences between Diablo and Fremantle UIs :

- as I already mentioned last time, the default font is tiny ! The new font size setting in GRead applies only to the item view, which is fine in Maemo5, but in Diablo it should apply everywhere (feeds/posts/settings/banners) because everything is so small to be hardly legible. Either that, or bind the zoom keys (F7/F8) to font size...

- unlike in Maemo5, Diablo "fullscreen" really means "full screen", so displaying the feed name (or anything else) in the windows caption is useless in that mode. Here it would come in handy to have the feed name with the title in the banner.

- as per the previous report, menus are still not translated to Diablo "system" menus, but something has changed for the better in this version : menu entries appear in a horizontal row at the bottom of the screen, like a toolbar with text buttons. Actually this works quite well, even the "furtive arrows" appear there in item view mode :-)

- the settings appear as a regular, scrolling frame, but without an 'OK' button, which may be confusing for those not used to Fremantle... you need to take it on faith that "escape" will save your settings :-)
Interestingly, the "help" dialog does have an OK button...

So, it is still true that very, very little is missing to make a usable GRead for Maemo4: probably remove the banner animation from 'basic', and create a thin 'maemo4' view that takes care of the font size issue and F7/F8 keys. the rest is not so important.