dragCrossMove: v3 markers don't float with cross when dragged?

[Falstaff]

As described in the v2 API reference for the GMarkerOptions
dragCrossMove property: "When dragging markers normally, the marker
floats up and away from the cursor. Setting this value to true keeps
the marker underneath the cursor, and moves the cross downwards
instead."

Not only is this property missing in v3 MarkerOptions, but markers no
longer float with a cross when dragged. The Google Maps webpage still
shows this behavior. How is it done? (Or is the webpage using v2??)

[Pil]

maps.google.com still uses v2, actually 264c.
Seems as if the incompleteness of v3 wouldn't suit their needs.

There is no such thing like dragCrossMove or similar in v3.

[Rossko]

> Not only is this property missing in v3 MarkerOptions, but markers no
> longer float with a cross when dragged.

So the option to suppress that behaviour isn't needed? v3 deliberately
dumps many of the frills of v2 to make it leaner.

> The Google Maps webpage still
> shows this behavior. How is it done? (Or is the webpage using v2?

v2 ; inspect the source of maps.google.com

[Pil]

On Aug 11, 1:17 pm, Rossko <ros...@culzean.clara.co.uk> wrote:

> v3 deliberately
> dumps many of the frills of v2 to make it leaner.

Yes, thats necessary because even with many many lesser features v3 is
much more sluggish to handle than v2 - especially on older machines.

In about a year or so when a few additional features will be
implemented the users will generally need the newest and fastest
machines available on the market - if they want to use the v3 maps
API.

[Federico Ulfo]

I hear that v3 is made lighter and faster than v2, it doesn't make sense to me to make a new version slower!
Do you have any link of the difference and the improvement between v2 and v3?

2010/8/11 Pil <wol...@gmail.com>

--
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-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Pil]

Try this simple page where you can use v2 and v3 side by side.
Try not use the newest machine and drag both maps with the mouse

http://www.wolfpil.de/v2-v3-sidebyside.html

Although the v3 map loads a bit faster it's pretty sluggish to drag
compared to v2.260.

I've tested the load speed of v2.140 (that unfortunately has been
switched off) with v3.1.6 and 2.140 loaded faster - although it has
had many more features than v3.

If Google tells you that there has been a general performance boost
from v2 to v3 it's a mere fairy tail, nothing more than PR.

Of course there has been some performace boosts, maybe for kml layers
and for Webkit browsers on newer machines. But the general assertion
that there has been a performance boost is not fair and is contrary to
the facts.

On Aug 11, 3:05 pm, Federico Ulfo <rainelemen...@gmail.com> wrote:
> I hear that v3 is made lighter and faster than v2, it doesn't make sense to
> me to make a new version slower!
> Do you have any link of the difference and the improvement between v2 and
> v3?
>

> 2010/8/11 Pil <wolf...@gmail.com>

>
>
>
>
>
>
>
>
>
> > On Aug 11, 1:17 pm, Rossko <ros...@culzean.clara.co.uk> wrote:
>
> > >  v3 deliberately
> > > dumps many of the frills of v2 to make it leaner.
>
> > Yes, thats necessary because even with many many lesser features v3 is
> > much more sluggish to handle than v2 - especially on older machines.
>
> > In about a year or so when a few additional features will be
> > implemented the users will generally need the newest and fastest
> > machines available on the market - if they want to use the v3 maps
> > API.
>
> > --
> > 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-map...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > google-maps-js-a...@googlegroups.com<google-maps-js-api-v3%2Bunsu...@googlegroups.com>
> > .

[Nianwei Liu]

This may not be the best thread to debate v2 vs v3, but I think it's
time to have that discussion. Maybe Pil can start a feature request to
"undepreciate" v2, or even further, request release of v2 to have it
community maintained if Google does not want to dedicate staff to
support it. Closure library is released so coding style and dependency
should not be an issue.

I have some similar observations like Pil has. On older machines, v2
does perform much better in many cases, for example, if an info window
is opened at the edge then the map pan to fit in the info window, v3
is much slower in the animation. There are also many small subtle
issues that were not considered in v3 implementation.

maps.google.com's mobile edition is still on v2, and it runs just fine
on my android phone. I do not have solid number for load speed. I know
main.js in v3 is smaller than v2, but that's because many code was
broken into more modules, and that's a disadvantage in some scenarios.