1# WatchPosition. However I've heard some people complaining that watchposition doesn't work as well on Android and that getPosition works better.
2# Performance wise it's always better to use any API directly rather than a plugin. If you are using jquery.ui.map (http://code.google.com/p/jquery-ui- map/) the overhead would be 4KB. A simple test adding 10000 markers with Google maps API and jquery-ui-map differs in 0-50 ms. 4KB in relation to jQuery ~31KB, jQM ~22KB, jQM CSS ~7KB, PhoneGap ~130KB (not minified), Google Maps ~85KB + atleast ~80KB images is pretty small. But if you are trying to optimize, you should start with removing any plugins (unless your coding would add more size than the plugin would), then removing jQM CSS not used and jQM code (I think they have split up the files so you just can load what you need). Performance wise it would be best to remove jQuery, jQM, any jQuery plugins and use Google static maps API. But I dont think that would work with what you are trying to accomplish. /Johan -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
