| The Following User Says Thank You to Nathan For This Useful Post: | ||
|
|
2009-10-16
, 18:31
|
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#12
|
I hoped that the new qt would have Maemo buttons, menu's etc. The current pull down menu is on the left of the screen and looks exactly the same as under x86 Linux.
| The Following User Says Thank You to allnameswereout For This Useful Post: | ||
|
|
2009-10-16
, 18:36
|
|
|
Posts: 475 |
Thanked: 771 times |
Joined on Dec 2007
@ Hamilton, Ontario, Canada
|
#13
|
| The Following 5 Users Say Thank You to fiferboy For This Useful Post: | ||
|
|
2009-10-17
, 20:16
|
|
Posts: 287 |
Thanked: 165 times |
Joined on Oct 2009
@ The Netherlands
|
#14
|
Out of curiosity are you the maintainer for the Diablo/Fremantle ports or did someone else do the Keepassx for Diablo. (I love Keepass)
You're not being efficient here. If Qt 4.6 changelog mentions things like 'Maemo buttons, menu's etc' then new Qt will provide this. If it does not mention, then it won't provide this.
[snip]
Does keepassx know its running Maemo? If it doesn't know, and Qt isn't compiled to know its running Maemo, it should look like Linux/x86-32. Qt supports various styles (?), such as Win32, MacOSX, ... but on Linux/ARM there are multiple.
[snip]
If there are specific Maemo features you probably see them in some test/example applications. No need for running keepassx.
Your screenshot shows a GTK application. You need to compile Qt 4.6 in SDK, and compile keepassx against that Qt version. As I said, you probably need to tell Qt to enable Maemo support (might be called different). You can compile for x86-32 in SDK, no need for ARM(EL) yet, thats for when you gonna roll out and test on real hardware.
The qt-maemo project on gitorious contains the best set of libraries I have used so far, and hopefully in the next few days they will be even better. The community port is going to be updated in the coming weeks (in the device repositories) and should give you the hildon look-and-feel you are expecting.
As far as I know, a simple re-compile against the correct libraries should bring the majority of the features for hildon (finger sized widgets, kinetic scrolling, etc). Finding the right set of libraries to provide that seems to be the sticking point right now, but hopefully it will be clearer in the immediate future.
Community port git repository: http://gitorious.org/+qt-maemo-developers/qt/qt-maemo
|
|
2009-10-17
, 20:45
|
|
|
Posts: 2,121 |
Thanked: 1,540 times |
Joined on Mar 2008
@ Oxford, UK
|
#15
|
|
|
2009-10-17
, 20:47
|
|
|
Posts: 3,397 |
Thanked: 1,212 times |
Joined on Jul 2008
@ Netherlands
|
#16
|
doesn't make the application unusable though.
|
|
2009-10-19
, 10:28
|
|
|
Posts: 3,105 |
Thanked: 11,088 times |
Joined on Jul 2007
@ Mountain View (CA, USA)
|
#17
|
This is caused by having an incompatible Qt installed on the system. The
"checkWindowRole" is a function added by a KDE patch, which most distributions
ship.
Just set LD_LIBRARY_PATH to where Qt is being compiled and where it is getting
installed to. This should fix the issue, by forcing the correct library
loading.
Also note that the standard build doesn't have this problem -- we supply the
equivalent -rpath-link option to the linker, so that it can find the right
libraries. Unfortunately, the Scratchbox buildchain messes that option up (it
doesn't behave like a native linker *nor* a cross-linker, but something in-
between).
This is technically a toolchain problem, not a Qt problem.
How to Provide Feedback
All feedback from the Qt user community is highly valued, and extensive testing of Qt on Maemo is encouraged. To collect this feedback, we have set up a special mailing list. The address of the mailing list is:
* qt-maemo-feedback@trolltech.com
Please join the mailing list to provide technology feedback, bug reports, suggestions or comments by sending a mail with the subject set as "subscribe" to:
* qt-maemo-feedback-request@trolltech.com
![]() |
| Tags |
| development, qt 4.6 |
| Thread Tools | |
|
Out of curiosity are you the maintainer for the Diablo/Fremantle ports or did someone else do the Keepassx for Diablo. (I love Keepass)
Nathan.