On Mon, Aug 16, 2010 at 2:18 PM, [email protected] <[email protected]> wrote: > On Aug 15, 5:33 pm, Ben Appleton <[email protected]> wrote: >> Hi Larry, >> >> On Mon, Aug 16, 2010 at 2:58 AM, [email protected] >> <[email protected]> wrote: >> > On Aug 15, 6:38 am, Hrvoje <[email protected]> wrote: >> >> Mike Willims has an implementation of an area calculation in his v2 >> >> epoly extension (but it doesn't fully account for the spherical >> >> earth). >> >> >> -- Larry >> >> >> I doesn`t care about spherical earth beacuse i need that tool for >> >> measuring roof surface, in other words, small part of earth. >> >> >> what is your suggestion, V2 or V3 or not important? >> >> > That determination you will have to make yourself. >> > Is it a production site? The version control on v3 leaves something to >> > be desired, and v3 doesn't "officially support" IE6. >> >> Can you elaborate on "The version control on v3 leaves something to be >> desired" - what more do you desire? > > In v2 there is the concept of stable, release and development > versions. Any released version can be referenced. > > In v3 the only choices are the equivalent of the "stable" release. > Most people are forced to use the equivalent of the "development" > version (.x) which was never suitable for production sites. Things > tend to break unexpectedly in the development version.
How are you forced to use the development version? >> The versioning system is documented >> here:http://code.google.com/apis/maps/documentation/javascript/basics.html.... >> If the docs or release process are unclear we'd like to improve that. > > I think it is clear. I just don't think the current process is > acceptable for production sites. What is the "official" > recommendation for production sites? Use v3.0? If you're a production site and risk-averse: Use the frozen version (currently v3.0). This ensures that the API JS will not change under your site. Test your site against the release version (currently v3.1). Report regressions with respect to the frozen version and we'll attempt to fix them. This will become the next frozen version. If you're a production site but need more recent features and fixes, use the release version (currently v3.1). We only patch bugs in this version, so it should be reasonably stable. If you want to try out the latest features and fixes, enjoy living on the edge, or want to be involved in the direction of the API, test the latest version (currently v3.2). > -- Larry > >> >> Thanks! >> Ben >> >> > Also, the tools for measuring area of polygons in v2 are available, in >> > v3, they don't seem to be. >> >> > -- Larry >> >> >> Thanks. >> >> > -- >> > 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 >> > athttp://groups.google.com/group/google-maps-js-api-v3?hl=en. > > -- > 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. > > -- 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.
