I added support for Google Gears at the Geolocation API. The previous 'support' was broken, now I added proper support and it works (tested on Mac Safari 4).
There is a small downside: The Geolocation module defines an extra GWT property ('use.gears.geolocation', values true/false) which effectively doubles the amount of GWT compiler permutations. The Gears Geolocation API is *only* selected when the browser has no native Geolocation API support (e.g. Opera, Desktop Safari, IE but not FF3.5+).
I intent to apply the same Gears strategy to the Database API: Add GWT property 'use.gears.database', which is only 'true' when Gears is installed AND the browser has no native Web Database API (and again doubling the amount of GWT compiler permutations :-))
An alternative approach would be to add a general 'gears.installed' property, and when 'true', just use the Gears API's regardless of native browser API's. This is easier for the GWT compiler (less properties -> less permutations) but might result in lower Geolocation precision.
What do you guys think?
Bart Guijt
E: bgu...@gmail.com
T: +31 6 30408987