Andrew Turner wrote: >> My design: >> - backend is extremely simple as it has no UI >> - It reads civic location data from gconf, uses a geocoding >> backend to get lat/lon >> - civic location data in gconf can be updated by anyone. In maemo I've >> included that in my statusbar applet. >> - civic location data in gconf has a "valid-until" timestamp with it > > Sounds nice. Agreed that a GUI shouldn't be necessary and using gconf > means any application can write it. I can imagine the calendar writing > it out during the day (and it also has my valid-until).
There are some interesting options here (I had a similar idea), but also some problems if writing the data is as free-form as it is in my design: what happens when there are two applications that would like to update the information... The calendar data-source is tempting, but maybe it should be a backend itself? > Valid-until should probably be optional So a location should be valid forever when "valid-until" is unset? > So there is the manual position backend, that just reads position. And > then a separate app (a front-end) is the dialog you wrote? Exactly. And any app could be a front-end but IMO the gconf entries should only be changed as a result of user interaction: this is the Manual backend after all... > In the US we'll also need State - for example "Springfield, US" has > some 34 possibilities. Sure, I'm still figuring out how to allow the needed detail and keep the number of UI elements down... -jussi
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GeoClue mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/geoclue
