On Mar 14, 7:28 pm, Esa <esa.ilm...@gmail.com> wrote: > We can see that the latest libraries (geometry, adsense, panoramio ) > were introduced as 'manually addable' libraries. > > Do you think it is good or bad? > > What I think is bad, is that I have to make the decision before I can > see the client performance. That makes difficult the roadmap called > 'progressive enhancement'. I am measuring certain parameters of the > client before deciding if I load certain scripts. With 'adsense' or > 'panoramio' I cannot make the decision after I loaded the map script. > Or can I?
I believe the API ought to decide what to load to give Google the flexibility to make changes. I believe cacheability ought to be favored over latency for first time users of any mapping application. I believe users of different mapping applications from different sources ought to expect to be able to share cached files. I believe "odd-ball" features like SVG & VML controls ought to be segregated in there own JS files. -- 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 google-maps-js-api-v3@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
