On Sep 15, 8:23 pm, Esa <[email protected]> wrote:
> @bradliff You are in a good position to suggest the best syntax for
> v3. Would it be a fragile series of comma separated numbers like
> areamap in html. Would it be a series of two-member arrays? You name
> it. I agree that a series of LatLng objects is wasting. They carry
> even some functions on their backbag.
Each "new GLatLng" has to be executed. Each "{x:,y:}" can be
interpreted directly by JavaScript.
I guess I would like to see a flexible parser able to digest whatever
the user throws at it.
For humans,
poly=
[
{x:,x0,y:y0},
{x:,x1,y:y1},
{x:,x2,y:y2},
{x:,x3,y:y3},
. . .
]
works well.
For machines,
poly=
{
x:[x0,x1,x2,x3, . . .]
,
y:[y0,y1,y2,y3, . . .]
}
works well.
I convert from the "human" form to the "machine" form internally.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Maps API" 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-api?hl=en
-~----------~----~----~----~------~----~------~--~---
