No You sound correct in both respects. An insulating (HW ABST) is needed! Sounds like fun wish I could do it.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kevron Rees Sent: Wednesday, August 18, 2010 4:36 PM To: [email protected] Subject: [MeeGo-dev] getting gps position in meego (with gypsy) I'm trying to understand how gps position retrieval is going to work in meego. My questions are specifically related to gypsy and it's usage within meego. I may be wrong, but I see a couple issues with using gypsy currently: 1. gypsy seems to require that "some application" initiates a connection with a device via the dbus (or library wrapper) interface. This means that the application (and this applies to a qt-mobility location backend that uses gypsy) has to know about the hardware that it's running on. I feel like an application or qt-mobility should be abstracted away from being required to know about the details of the hardware. Getting the gps position should be as simple as an api call. A solution that comes to mind would be to enable gypsy to read some sort of config file when it starts. This config file would be device specific and would allow gypsy to work without requiring an app to do extra setup. 2. org.freedesktop.Gypsy.Server has no way to notify location aware apps if a connection has been created. To get around this, a location aware app would have to poll dbus introspection for a "client" node. This is less than optimal. The simple solution in this case would be to have Gypsy.Server expose a "ClientCreated" signal and possibly a "ClientRemoved". I wanted to shoot out these observations with the assumption that I'm wrong and I just don't know about "the right way to do it". If anyone can help me better understand, I'd appreciate it. -Kevron _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
