Hei
Now I must interfear with this discussion.
When I decided to use Qt, one reason was to avoid
huge amount of #ifdefs and move to just one
codebase. With Qt this about 95 to 98% true, that
is good. Porting Order from easiest to most
difficult is in my opinion Win32, mac. linux,
wince, winppc (6.5 most difficult) , maemo, symbian touch and symbian navpad.
With mobility/Location I tried to use it on
Symbian and Maemo platforms. Unfortunately had to
use native api's. So I ended up with situation
there I have five location / nmea components for
mac, Win32, Wince/ppt, symbian and maemo.
actually maemo and symbian have double, qt
location abandoned. The mobility apis had minor
faults an minor errors here and there. Another
thing is that NMEA-standard is huge having
support for all kind of instruments, so all data
that is coming is from almost same source. You do
not have to make different apis for eg compass,
gps, echo, AIS, wind etc. Once You have proper
NMEA-parser, you can read almost any device.
When starting to do programs with location
everything seems so easy, in real life things are
more complex, actually very complex.
I have also something to say about samples. They
mostly demostrate jus one object. You enter to
difficulties when combining those examples into
larger unity. When You have deeper hierachies in
application You are many times jumping into big trouble.
Br
Hannu
At 18:39 3.10.2010, Till Harbaum / Lists wrote:
Hi Alex,
thanks for your reply.
Am Sonntag 03 Oktober 2010 schrieb [email protected]:
> You need a custom QGeoPositionInfoSource.
Since your source seems to be an NMEA source
you might want to give QNmeaPositionInfoSource a try.
I am afraid i don't get the concept behind this.
If there's one thing i expected qtmobility to do
then it's to abstract the hardware layer.
Also there's QNmeaPositionInfoSource, but e.g.
no QNmeaSatelliteInfoSource which obviously
seems to be what the satellitedialog depends upon.
The "right" way to use an nmea gps is really to
hard code nmea support into the app and to write
your own QNmeaSatelliteInfoSource? This would
result in a bunch of #ifdefs when using GPS on
desktop linux vs. meego/maemo and is exactly
what i'd like to avoid. If you e.g. look at the
sourcecode of maep/gpxview etc then you'll find
exactly this #ifdef'd GPS location switching
which i hoped would be gone with qtmobility.
Also the maps seem to face the same issue. There
are two map demos/examples, one being
openstreetmap based and one being nokia maps
based. It seems the osm example is handling osm
completely in the application and not by
qtmobility. Does this make sense? What's the
point having a powerful framework when it's up
to the application to do the most complex parts
itself? Will this change? My expectations were
that the map widget reports to the application
what map source plagins it has and then uses one
of these. What's the point of moving low level
map stuff out of the framework into the application?
Till
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
Hannu Säles Oy
Ruomelantie 12 C, FI-02210 Espoo, Finland
http://www.hannusales.fi
tel: +358-400-725374
_______________________________________________
Qt-mobility-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-mobility-feedback
