[Development] Qt5 missing features

[BogDan]

Hello,

 First and foremost congrats for Qt5 alpha release, it is great to see Qt
moving forward.
Back in December I tried to merge current android port but I quickly gave up
because Qt 5 didn't seem to be too stable and it didn't had all the features
I was looking for[1], these days I briefly check Qt5 source code and most of
the features are in place except a just few which are not there, IMHO these 
features are very important and they will make the difference between a good
port and a great port. I'll highlight the most important two of them:

 - platform menu APIs. Current APIs are not enough for Android platform (same
 for Mac OSX?), I need a way to *manage* from platform plagin the menubar and
the context menus, meaning that Qt must show/hide the menu(bar) using the
platform plugin. There where two proposals [2], [3] which, at first sight,
seems to be what I'm looking for, but they have been abandoned for months, 
is there any reason why not pushing them forward ?

 - platform theme APIs, current APIs are good but not enough, BTW 
"KeyboardSchemes" enum doesn't seems to used and IMHO doesn't contain very
cross platform values :). For several months I struggle to create a style 
plugin for Android, I manage to create the support for a few classic widgets
and I found that the work I did can not be used also for QML ones. I believe
it is a huge waste of time to do the same job twice in two different ways. 
IMHO both QML and classic widgets should use a single theme manager to draw
the widgets, of course every single platform should be able to create its own
implementation. Android has a pretty good theme manager implementation, which
is flexible enough and lets the user to overwrite almost all theme attributes,
I really love to see something BETTER in Qt !

IMHO these features are too important to miss the opportunity to include them
in Qt5.0.
Kindly please consider to include these features in final Qt5.0, I don't know
if it will be a second chance to include them without any compromise, without
not worry about API/ABI compatibility.

Thank you !

Kind regards,
BogDan.

[1] http://lists.qt-project.org/pipermail/development/2011-December/001028.html
[2] http://codereview.qt-project.org/#change,11954
[3] http://codereview.qt-project.org/#change,17906