(No comment was entered for this change.)

Please consider loading just enough to function on a particular browser.  An iPhone
user does not require VML support.

Your "mld" service is under appreciated.  It works well with light weight portable
devices without JavaScript vector graphics capabilities.  It produces cacheable
polys.  The polys do not have to be rebuilt from scratch by every user during every
session.

I like polyline & polygon..
hope I can using polyline & polygon in API V3..

In addition to loading just the components (VML / SVG / CANVAS / SERVER) required for
the active browser, the "clickable" option ought to be loaded on demand.  V2 GPolys
are really slow & bloated.  V3 ought to remain "light weight".  It is unclear whether
the "fromEncoded" option is worth the extra overhead.

The ability to specify Mercator projection pixel coordinates (along with a zoom
level) is a fast alternative to Lat/Lon coordinates.  It eliminates a lot of
conversion overhead.

While API v3 has some nifty features, I'm not sure how "light weight" it could remain
if GPoly functions are added.  I've found that the only reason my 524kb xml file of
lat/lon points used to create polygons of buildings, parking lots, walkways, etc...
fails to load properly on the iPhone is because of v2's js memory footprint (which is
supposedly going to be fixed in the next update of the iPhone's software).  The funny
thing is that my Palm Pre renders the map perfectly and rather quickly.

If I understand the "v3" right, it means that this version is not just a mobile
branch of the maps api v2. It's the next version, which will replace v2 earlier or
later. So I expect, that all(!) features of the v2 version will be in the final
release of v3. This includes polylines, polygons, draggable points, support for
streetview, Google Earth and all the other great stuff of v2.
If this is not the intention of v3, the new API should be renamed to Mobile Maps Api
or Maps Light API or whatever!

Sascha 

And btw this means, that there should be here just one big issue for all of the
missing v2 features. 

Sascha

@sascha or v3 could be the new stripped version with the ability to load gmap plugins
for other functionality like polylines or streetview. just my thought google!

I'm also waiting for Polylines.  Are there any hacks or workarounds until the feature
is added?

Some workarounds are discussed in this thread:

http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/7eb629ba9da78d9e/

+1 for polylines... not able to convert to v3 unless this is supported.

I would really like polylines and polygons too.  And I would really like a way to
have a circle overlay too, centered at a given coordinate with a given radius in km
or miles or some other real-world measure.

Polylines are very essential part. Hope it will be added to v3, if v3 is going to be
the Future version.

An interim solution does exist.  Some examples:

Simple
    14,000 vertices
    www.polyarc.us/polycluster/alaska.html
    41,000 vertices
    www.polyarc.us/polycluster/absurd.html

Advanced
    20,000 vertices (static load)
    www.polyarc.us/polycluster/canada.html
    110,000 vertices (dynamic load)
    www.polyarc.us/polycluster

Firefox, Opera, Safari, Chrome & iPhone are supported.  Unfortunately, IE does not
support CANVAS.

Thanks for posting the interim solution; however, I don't believe MSIE supports CANVAS. :(  I'm definitely looking 
forward to native polyline functionality in v3. :-(   

++*;

Yeah its not a solution until IE can do it unfortunately

You are right.  I have a kludge using Google's "mld" server but it is illegal.  I am
looking for a VML wizard to help me port it.  VML is broken on my machine.

We have just posted a roadmap that confirms support for this functionality is
upcoming, please read through it:
http://groups.google.com/group/google-maps-js-api-v3/web/v3-roadmap---september-2009

Excellent news.  Thanks Pamela!

thanks Pamela. These new features in roadmap are very important!

i think that the feature it is included now ... right? :)

Thanks for this:
https://code.google.com/intl/it/apis/maps/documentation/v3/overlays.html#Polylines
I think that there is a bug in documentation (maybe the syntax is correct but in this
way, at the moment, it doesn't work):
  var flightPath = new google.maps.Polyline(flightPlanCoordinates, {
    strokeColor: "#FF0000",
    strokeOpacity: 1.0,
    strokeWeight: 2
  });

Must be:

    var flightPath = new google.maps.Polyline({
      path: flightPlanCoordinates,
      strokeColor: "#FF0000",
      strokeOpacity: 1.0,
      strokeWeight: 2
    });


For Pamela: we can open an issue for bugs found in these new features? 

Thanks, we'll fix the snippet. Check the linked example for now, it's correct.
It's fine to start opening issues related to them now.

And yes, for those of you watching this issue's comments, polys are in the latest 
release, and you can read more about them in the documentation and reference. We will 
publish the changelog within the next day, and a blog post soon after that.

One more code snippet to update on the same page: 
https://code.google.com/intl/it/apis/maps/documentation/v3/overlays.html#Polylines

In the polylines section, the code still has the bug.  Thanks to Roberto for the fix 
and Pamela for the documentation updates.