Active Topics
-
Porting apps to Leste (49)
to Maemo 7 / Leste by teroyk - 1 day, 2 hrs ago -
Maemo repository (39)
to Community by teroyk - 1 day, 3 hrs ago -
Help needed to recover from botched user config preventing boot (8)
to MeeGo / Harmattan by nphuracm - 2 days, 9 hrs ago - more...
| The Following User Says Thank You to rlinfati For This Useful Post: | ||
|
2010-01-12
, 16:15
|
|
Posts: 5 |
Thanked: 0 times |
Joined on Dec 2009
|
#12
|
Originally Posted by rlinfati
Ahhhhhhh.
the glib object loop is "autostarted" via Qt...
i not seed any new mail
The problem fixed when I changed:
Code:
QCoreApplication app(argc, argv);
Code:
QApplication app(argc, argv);
And the solution was so easy.
Thanks a lot for the reply.
Yet it would be nice if it would be possible to use QCoreApplication and start glib event loop manually for those who write cli applications.
 |
|
2010-02-16
, 13:30
|
|
Posts: 71 |
Thanked: 47 times |
Joined on Dec 2009
|
#13
|
Originally Posted by yerga
Check the PDF in this page: http://wiki.forum.nokia.com/index.ph...velopers_Guide
Chapter 5.1: Using Maemo APIs in Qt applications - Liblocation
The example that comes there is with Gtk though (weird thing being Qt documentation).
Is there a newer version of that pdf or a better Qt developer guide? I went through chapters 1 and 2, and for some reason created deb doesn't have a binary inside. While reading the guide I noticed some inconsistencies.
Maybe it's because of newer SDK, but the content of generated rules file is very different and APPNAME variable not used in it.
Then this uuencode tool...works weird. With the following command:
uuencode -m icon-26x26.png > icon-26x26.base64
it just gets stuck, waiting for input? who knows. Had to do it like this:
uuencode -m icon-26x26.png foo > icon-26x26.base64
I copy-pasted the content into control file, and received a complaint later:
dpkg-genchanges: warning: unknown information field `Xb-Maemo-Icon-26' in input data in package's section of control info file
Huh?
Next, nothing said about iconxpm icon26 icon40 icon64 icons creation, for the author it seemed to be too obvious to talk about.
And finally, after dpkg-buildpackage I've got a deb package of 3kb size. What's inside:
./usr
./usr/share
./usr/share/doc
./usr/share/doc/qscroll-test
./usr/share/doc/qscroll-test/copyright
./usr/share/doc/qscroll-test/changelog.Debian.gz
./usr/share/doc/qscroll-test/README.Debian
./usr/bin
./usr/sbin
Even no .desktop file there. From the build logs everything looks ok, except Xb-Maemo-Icon-26 complaint. I have never done deb packaging before, so I'm quite lost
|
|
2010-02-16
, 14:12
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#14
|
Originally Posted by sph
Find a good packaging guide for Qt in the wiki.
Is there a newer version of that pdf or a better Qt developer guide? I went through chapters 1 and 2, and for some reason created deb doesn't have a binary inside.
Originally Posted by sph
The right command is:
Then this uuencode tool...works weird. With the following command:
uuencode -m icon-26x26.png > icon-26x26.base64
it just gets stuck, waiting for input? who knows. Had to do it like this:
uuencode -m icon-26x26.png foo > icon-26x26.base64
Code:
uuencode -m <name of 48x48 image> <name of 48x48 image> > <name of 48x48 image>.base64
Originally Posted by sph
The field is called 'XB-Maemo-Icon-26'.
I copy-pasted the content into control file, and received a complaint later:
dpkg-genchanges: warning: unknown information field `Xb-Maemo-Icon-26' in input data in package's section of control info file
Huh?
Originally Posted by sph
Do you have the sources somewhere? The easiest thing is to do that with the help of the project file and Qt itself. Please consider therefore the packaging guide I mentioned above. Without knowing how your rules & project file look like, is it hard to figure out what is going wrong here.
Next, nothing said about iconxpm icon26 icon40 icon64 icons creation, for the author it seemed to be too obvious to talk about.
And finally, after dpkg-buildpackage I've got a deb package of 3kb size. What's inside:
./usr
./usr/share
./usr/share/doc
./usr/share/doc/qscroll-test
./usr/share/doc/qscroll-test/copyright
./usr/share/doc/qscroll-test/changelog.Debian.gz
./usr/share/doc/qscroll-test/README.Debian
./usr/bin
./usr/sbin
Even no .desktop file there. From the build logs everything looks ok, except Xb-Maemo-Icon-26 complaint. I have never done deb packaging before, so I'm quite lost
Daniel
| The Following User Says Thank You to danielwilms For This Useful Post: | ||
|
|
2010-02-16
, 14:34
|
|
Posts: 71 |
Thanked: 47 times |
Joined on Dec 2009
|
#15
|
Originally Posted by danielwilms
Thanks, I will read it.
Find a good packaging guide for Qt in the wiki.
The right command is:
Code:uuencode -m <name of 48x48 image> <name of 48x48 image> > <name of 48x48 image>.base64
The field is called 'XB-Maemo-Icon-26'.
Do you have the sources somewhere? The easiest thing is to do that with the help of the project file and Qt itself. Please consider therefore the packaging guide I mentioned above. Without knowing how your rules & project file look like, is it hard to figure out what is going wrong here.
I will read the packaging guide you gave and then if still have problems I will share the sources. I was going to do so after I finish with packaging. That's a scroll performance test, something that bothers me from the beginning. Every scroll area in maemo is slow as hell when scrolling. I did a simple app with a single qt scroll area which is blazingly so much faster. I wish I knew how to get a FPS counter to make a comparison.
|
|
2010-02-16
, 14:54
|
|
Posts: 432 |
Thanked: 645 times |
Joined on Mar 2009
|
#16
|
Originally Posted by sph
Have a look here
Makes no sense.
Originally Posted by sph
It is an extension field, according to the debian policy. Might be that a warning is thrown, because it is a non-standard field.
I didn't misspell XB with Xb, but it may look so from the warning. I don't know why.
Originally Posted by sph
Ok, that sounds good. Let us know if you need more infos.
Nowhere yet
Daniel
|
|
2010-02-16
, 15:30
|
|
Posts: 17 |
Thanked: 42 times |
Joined on Feb 2010
|
#17
|
Maybe also look at http://qtmapper.garage.maemo.org/. I've not looked at it much, it seems to be getting the GPS data from a serial port somehow (how does the gtk version talked about in this thread work at the low level?). From what I can see, you can include the stuff from QtMapper, and you can then just create a QObject, and get GPS details with its accessor methods.
Edit: It strikes me that there should really be some sort of provision in Qt for things like camera, GPS, etc, especially with Qt becoming the default UI Maemo/Meego. Having to access GPS by serial port is fine if it works, but it's not something that lends itself to cross-platform/device situations: that's the kind of thing that should be handled by the Qt API, providing a nice interface to the underlying device-dependent stuff.
Edit 2: D'oh, I fail so bad: QtMobility
Last edited by StewartHolmes; 2010-02-16 at 16:05.
Edit: It strikes me that there should really be some sort of provision in Qt for things like camera, GPS, etc, especially with Qt becoming the default UI Maemo/Meego. Having to access GPS by serial port is fine if it works, but it's not something that lends itself to cross-platform/device situations: that's the kind of thing that should be handled by the Qt API, providing a nice interface to the underlying device-dependent stuff.
Edit 2: D'oh, I fail so bad: QtMobility
Last edited by StewartHolmes; 2010-02-16 at 16:05.
i not seed any new mail
User:rlinfati