Skip to content
This repository has been archived by the owner on Apr 24, 2021. It is now read-only.

Upgrade to Maps v3 #381

Open
GoogleCodeExporter opened this issue Sep 10, 2015 · 84 comments
Open

Upgrade to Maps v3 #381

GoogleCodeExporter opened this issue Sep 10, 2015 · 84 comments

Comments

@GoogleCodeExporter
Copy link

I would like to see support for Maps v3.

Original issue reported on code.google.com by dusan.ma...@gmail.com on 4 Jun 2010 at 12:23

@GoogleCodeExporter
Copy link
Author

In the mean time, see:

http://code.google.com/p/gwt-google-
apis/wiki/MapsFAQ#How_can_I_use_GWT_with_Maps_API_3.0?

Original comment by zundel@google.com on 4 Jun 2010 at 1:03

  • Changed state: Accepted
  • Added labels: API-Maps

@GoogleCodeExporter
Copy link
Author

I'm fully aware of that page, but we use quite a large set of API features. Is 
there any schedule/roadmap, or some 
rough approximation on when it will be available? Is there anybody working on 
it?

Original comment by dusan.ma...@gmail.com on 4 Jun 2010 at 1:13

@GoogleCodeExporter
Copy link
Author

There is another open source project out there that has support for a good 
number of features you can use:

http://code.google.com/p/gwt-google-maps-v3/

Original comment by zundel@google.com on 19 Jun 2010 at 3:14

@GoogleCodeExporter
Copy link
Author

Now that v2 has been deprecated, I would have thought this would be raised to 
'high' priority? 

It looks here like we are being encouraged to use a third party api over the 
official one.

Would love to get a date on the official api release.


Original comment by tculs...@gmail.com on 25 Aug 2010 at 11:04

@GoogleCodeExporter
Copy link
Author

gwt-google-maps-v3 has also been deprecated. This is the message on the project 
page.
"This project will soon be merged into gwt-google-apis and hence is 
depricated".  It would be interesting to get the timeframe.

Original comment by brendanp...@gmail.com on 26 Aug 2010 at 5:49

@GoogleCodeExporter
Copy link
Author

[deleted comment]

2 similar comments
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Is there any way to track the v3 integration advancement ? 

Since the process for v3 integration is quite long, i would like to be able to 
see at least the shape of the api, i like to work on my code base with future 
migration to v3 in sight, to at least avoid introducing too much compatibility 
problems. 

I'm already pretty worried about the v2->v3 migration, and i am not comfortable 
at all with the silence on this issue.

Original comment by nicolas....@gmail.com on 6 Jan 2011 at 11:11

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

There is no change in status since the FAQ entry (mentioned above as the second 
post in this issue) and several posts on the gwt-google-apis forum.  We are 
updating gwt-google-maps-v3 in a change branch while leaving the 
gwt-google-maps-v3 project stable.

Original comment by zundel@google.com on 6 Jan 2011 at 3:00

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I really need this!

Thanks,
Brandon Donnelson
http://gwt-examples.googlecode.com

Original comment by branflak...@gmail.com on 6 Feb 2011 at 4:07

@GoogleCodeExporter
Copy link
Author

Yes. Uncertainty is a poison pill for developers. Please keep us up to date on 
the path for the version 3.

Original comment by terry.je...@gmail.com on 24 Feb 2011 at 3:59

@GoogleCodeExporter
Copy link
Author

I second that, in fact the lack of upgrades here (for me) starts to beg the 
question, if integration is such a big deal, why should developers be 
(considering) using GWT at all. Don't get me wrong, I'm a big GWT fan, BUT if 
we start having issues even with Google (!!) APIs, I think we have a problem. 

Original comment by tculs...@gmail.com on 24 Feb 2011 at 4:43

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I will comment again on this thread and say that there is no timeline for 
incorporating the Maps v3 bindings into gwt-google-apis.  You can use other 
third party maps v3 bindings or write your own bindings using GWT's built in 
JavaScriptObject and JSNI support.  You are welcome and encouraged to star this 
issue to vote your support.  I maintain the library and I know it is a popular 
request, but adding more comments on the same line obscures my previous updates 
to the status of the problem.

Original comment by zundel@google.com on 24 Feb 2011 at 2:07

@GoogleCodeExporter
Copy link
Author

Ok, but you, as a maintainer, are obliged to let your users know what's the 
status. If you say there's no timeline, you should give a reason why there 
isn't one, and when it will be. If there is no interest in this project any 
more from maintainers' side, please let us know, so that we can drop our 
dependencies on gwt-google-apis, or even GWT. That would be a fair behavior, I 
don't see you doing that, all you say is "go honk yourself" (that's what you 
call "use other third party maps v3 bindings or write your own bindings using 
GWT".

Original comment by dusan.ma...@gmail.com on 24 Feb 2011 at 2:17

@GoogleCodeExporter
Copy link
Author

shame on google ..., but there is 3rd party implementation that works pretty 
fine for me. Check it out. http://code.google.com/p/gwt-maps3/

Original comment by fili...@gmail.com on 24 Feb 2011 at 2:30

@GoogleCodeExporter
Copy link
Author

I do not intend to condone honking yourself or others.

Let me try to clarify and summarize from conversations in the group:  This 
issue, number 381 is a request for a new feature as far as the gwt-google-apis 
library is concerned.  Yes, it is something we'd like to add, but there is no 
one working this new feature.  Please do not make future plans expecting it to 
arrive at a certain time because there is no timeline for fixing it or the 
other outstanding new feature requests.

We had a change branch going for a while (see the SVN repository under 
changes/vinays), but now no one is available to work on it.  That change branch 
relies on the JSIO library which is much less efficient than using 
JavaScriptObject overlays.  We were trying to get rid of JSIO and tease out 
other inefficiencies.   There have been some ideas tossed around for 
automatically generating an API from the documentation, but I've only done a 
proof of concept - there are complexities in mapping class hierarchies and 
parameters that are closures in JS to Java constructs.  Its pretty simple to 
look at the design and do it by hand, but difficult to write an automatic rule 
for.  And even if all that were done, to be an official library, we'd need unit 
tests, documentation, examples...

We are maintaining existing features of the API.  It is an open source project 
and if someone wants to make a contribution, let's talk about it on the 
gwt-google-apis group.  

There is more than one third party wrapper checked in to Google Code.  If you 
would like some help wrapping any JavaScript API there are many examples you 
can look to on Google Code and a vibrant GWT community.

Original comment by zundel@google.com on 24 Feb 2011 at 2:50

@GoogleCodeExporter
Copy link
Author

Let me add one more comment.  Some developers might be waiting for a 
gwt-google-apis official set of bindings because they hope to be able to 
upgrade to v3 without changing the API.

The Maps v3 API is incompatible with the Maps v2 API and any attempt to make 
new GWT bindings will likely break source and binary compatibility as well.  
The v3 API was carefully crafted to be lightweight enough for use on mobile 
devices, and I'd like to see any official GWT bindings remain true to that 
design goal. 

Original comment by zundel@google.com on 24 Feb 2011 at 3:01

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I can't speak for others, but the reason I'm looking forward to an upgrade is:

* Maps v2 is deprecated.
* Maps v3 does not require API keys.

I'm perfectly fine with the newer API breaking backwards compatibility.

Original comment by cowwoc...@gmail.com on 24 Feb 2011 at 3:04

@GoogleCodeExporter
Copy link
Author

I removed a few comments requesting a release date for this feature (there is 
none) to cut down on the clutter in this issue.  

If you would like to participate in the discussion about contributing to the v3 
bindings that are in changes/vinays, see the groups discussion below.

https://groups.google.com/forum/#!topic/gwt-google-apis/4e9GU638KCc

Original comment by zundel@google.com on 24 Feb 2011 at 3:32

@GoogleCodeExporter
Copy link
Author

My organization has made a few web applications
with GWT and the official Maps V2 library.
We also have made mobile/HTML5 apps with GWT,
but not yet with Maps.

I just went to a Google Earth Outreach program where the
presenters emphasized that the Maps V2 API was deprecated,
and that we all (developers in the audience) should switch
to Maps v3. After hearing that, I am hesitant to put much more effort
into GWT + Maps V2, much as I like it.

Over the past two days I have tried using this:
  http://code.google.com/p/gwt-google-maps-v3/
in a new application. I did get it to work, but had
to stop when I came up against the lack of support for
(what were called in V2) TileOverlays. Our map
applications rely on a custom tile layer which appears 
on top of the Google Map Type

Here is a concrete question: I am wondering if it
is worthwhile to keep going with
  http://code.google.com/p/gwt-google-maps-v3/
and try to add the needed tile overlays with
JNDI and ImageMapType. Either that or,
again with JNDI, try to add a V3 KMLLayer
that duplicates the effect of the custom tile layer.
Other than that, at the moment I do not see a
migration path from Maps V2 to Maps V3
for our GWT applications.

Any advice appreciated.
(Another thing they said at the Google Outreach program
was this: use Google Groups to say what features
you want.)

Original comment by jhmalp...@gmail.com on 27 Feb 2011 at 8:26

@GoogleCodeExporter
Copy link
Author

What is the status of this issue? 

Original comment by racam...@gmail.com on 23 Sep 2011 at 7:26

@GoogleCodeExporter
Copy link
Author

Why on earth is Google not actively developing this? Their flagship API still 
isn't supported by their flagship toolkit. Crazy. I'm glad that at least 
something was released, albeit via obscure forum post.

Original comment by tra...@traviswebb.com on 6 Apr 2012 at 10:46

@GoogleCodeExporter
Copy link
Author

I totally agree with you, but I've asked Google this very questions and the 
response was paraphrased..."Adwords is our flagship product".

Original comment by j...@dualsportmaps.com on 6 Apr 2012 at 11:07

@GoogleCodeExporter
Copy link
Author

So, is a final 3.8.0 api ever going to be released?

Original comment by sys...@gmail.com on 30 May 2012 at 9:22

@GoogleCodeExporter
Copy link
Author

I have just tried to start running the samples referenced in Comment 53, 
following the instructions in the README.txt and have the following issue:

com.google.maps.gwt.samples.server.Server

has imports:

import com.google.gse.GoogleServletEngine;
import com.google.gwt.gserver.GwtResourceServlet;
import com.google.net.base.IpScanners;

that are not resolved.

I've searched for these classes and can't seem to find them anywhere.

Any indication as to where to find these would be appreciated.

Thanks!


Original comment by pstron...@gmail.com on 12 Jun 2012 at 5:50

@GoogleCodeExporter
Copy link
Author

I ran into a pretty significant bud with the Pre-Release bindings. You can not 
attache the panel containing the map to another panel. I asked this question on 
stack overflow, but got no response.

http://stackoverflow.com/questions/12489880/gwt-google-apis-gwt-map-3-8-0-pre-th
rows-javascriptexception-map-is-not-define


I switched to branflak's API which seems to work well.

http://gonevertical-apis.appspot.com/

Original comment by rtr...@gmail.com on 2 Oct 2012 at 9:24

@GoogleCodeExporter
Copy link
Author

I've been waiting for the past 2 years for this. The official v2 api is about 
to be deprecated in about 6 month and still no final release and documentation 
for v3.

A bit annoying to pay a license for google maps, and then having to use a 3rd 
party API to actually make something out of it. 

Original comment by sys...@gmail.com on 3 Oct 2012 at 12:24

@GoogleCodeExporter
Copy link
Author

Stepping back on this one, GWT seems to be going nowhere. It's not really used 
by Google itself, you can't even get it to from 
https://developers.google.com/products/

Original comment by dusan.ma...@gmail.com on 3 Oct 2012 at 12:27

@GoogleCodeExporter
Copy link
Author

The maps, completely right. But on the future of GWT, not really true if you 
watch this : http://www.youtube.com/watch?v=VOf27ez_Hvg
Moreover, Google Adwords - the flagship product - is written in GWT, amongst 
others..

Original comment by k...@koma.be on 3 Oct 2012 at 12:34

@GoogleCodeExporter
Copy link
Author

They use GWT for adwords, so it is their main revenue generating toolchain. The 
issue isn't with GWT, its that Google don't use it for maps so they don't see 
the value in continuing to create GWT APIs for their other products. Really, 
its too bad...

Original comment by j...@dualsportmaps.com on 3 Oct 2012 at 12:35

@GoogleCodeExporter
Copy link
Author

Google Flights <http://www.google.com/flights/> is built with GWT *and* makes 
use of Maps so please stop saying they don't use GWT with Maps.
They seem to be using JSNI (at least they don't use AjaxLoader from GWT Google 
APIs, because their callback is called maps_apiv3_load_callback, not 
__gwt_AjaxLoader_onLoad); either that or they rolled their own API (or more 
probably they use the same base as "3.8.0-pre1", but with a hand-rolled or 
customized AjaxLoader).

Original comment by t.broyer on 3 Oct 2012 at 1:54

@GoogleCodeExporter
Copy link
Author

I meant maps as in maps.google.com. Which as far as I can tell is not GWT.

Original comment by j...@dualsportmaps.com on 3 Oct 2012 at 2:00

@GoogleCodeExporter
Copy link
Author

I want to develop a google earth app with GWT. I have seen the gwt-earth-3 
wrapper by Nick Kerr. 
But I am confused right now: If this is "The Official Google API Libraries for 
Google Web Toolkit" why doesn't it have a Google Earth wrapper? Is the 
gwt-earth-3 wrapper by Nick somehow connected to the official libraries?

Original comment by asim...@gmail.com on 28 Oct 2012 at 9:19

@GoogleCodeExporter
Copy link
Author

Hi,
We just received an official mail from google, saying that the v2 API is about 
to be decommissioned. In other words: expect it to stop working soon.

From the email:

"The Google Maps Javascript API V2 was deprecated on May 19, 2010 and will 
continue to work until May 19, 2013. After that date, we will no longer offer 
support for this API and will begin the decommissioning process."

In light of this fact, my personal opinion is that failure to provide a stable 
GWT wrapper until now is gross negligence.

Tomer

Original comment by tom...@gmail.com on 29 Nov 2012 at 8:41

@GoogleCodeExporter
Copy link
Author

Tomer..... could not agree more with you. 
Got the same email, and I am a bit lost as to what to do right now.

Original comment by sys...@gmail.com on 29 Nov 2012 at 12:14

@GoogleCodeExporter
Copy link
Author

Hi,

Have used http://code.google.com/p/gwt-maps3/ , provides som base
functionality.

Original comment by pether.s...@gmail.com on 29 Nov 2012 at 12:26

@GoogleCodeExporter
Copy link
Author

Hi Pether

Will add to my list of alternatives. Still, because I actually pay for a 
license, I would much rather using the official GWT wrapper. If there was one

Original comment by sys...@gmail.com on 29 Nov 2012 at 12:49

@GoogleCodeExporter
Copy link
Author

I can recommend these wrappers for gwt maps v3:

https://github.com/branflake2267/GWT-Maps-V3-Api

They are not official, but I've been using them for production for a while now 
without issues.

Original comment by sarkhee on 29 Nov 2012 at 12:53

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

There is an official binding (see comment 53), why don't you use this one?

it's quite outdated (still maps 3.8) but it seems to (still) work: 
http://code.google.com/p/gwt-google-apis/downloads/detail?name=gwt-maps-3.8.0-pr
e1.zip

Original comment by googelyb...@gmail.com on 29 Nov 2012 at 12:54

@GoogleCodeExporter
Copy link
Author

Could you point me to the API javadoc for this? All googling gets me is the 
link below
and the API for 1.1.0/1.0.4

Original comment by treethin...@gmail.com on 1 Dec 2012 at 10:11

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

The jar linked above also contains the source and hence Javadoc will be 
displayed in your IDE.

I wrote up an example of using this pre-release with HTML5 geolocation here: 

http://blog.vercer.com/2012/12/google-maps-v3-with-gwt-example.html

Original comment by jdpatterson on 16 Dec 2012 at 8:04

@GoogleCodeExporter
Copy link
Author

Hi All,

I am using the very nice GWT V3 API and when I run the sample apps I see all of 
the road and city labels for most countries. But when running in my own 
application (both in development mode and deployed to GAE) some countries do 
not have labels, for instance Ireland and Italy. I added an API key (although 
the sample app does not use one) and that did not help. Any ideas?

Thanks
Mark 

Original comment by thinian...@gmail.com on 29 Dec 2012 at 12:01

@GoogleCodeExporter
Copy link
Author

It's a pity! Nothing is working for me when using this pre release of 3.8.0, I 
just have a blank page, with no error messages... and no map displayed.

Google guys working on GWT MAPS API have to do better than that!

Original comment by dg.sicon...@gmail.com on 7 Mar 2013 at 2:05

@GoogleCodeExporter
Copy link
Author

For the gwt-maps Java API and Javascript V2 API decommissioning date (so far 
May 19), I would like to know if May 19 is a drop dead date, or if there is any 
possibility of postponement - just like the postponement Google did for the 
Geocoding V2 change by six months? The Geocoding postponement was announced 
literally at the last minute. It will really help if we (the licensed users) 
are made aware of any such move beforehand. In our case, we have the coding 
completed and a firm date will help in prioritizing the production deployment, 
among the many other competing priorities.

Original comment by sudd.gh...@gmail.com on 2 Apr 2013 at 3:34

@GoogleCodeExporter
Copy link
Author

Deprecation deadline for Google Maps API v2 has been extended to Nov. 19, 2013. 
 After this date, apps requesting v2 "will be served a special, wrapped version 
of the v3 API instead."  More here - 
https://developers.google.com/maps/documentation/javascript/v2/

Original comment by sjbarb...@gmail.com on 1 May 2013 at 2:59

@GoogleCodeExporter
Copy link
Author

Google's official pre-release (gwt-maps-3.8.0-pre1.zip) does not seem to 
include class MarkerCluster, which we use (with GWT map API v2 wrapper) in our 
application to show clustered markers (Note: our map would contain up to 20k 
markers, scalability is a major requirement) We currently use MarkerCluster 
provided in gwt-maps-utility-1.0.zip (from 
http://code.google.com/p/gwt-maps-utility/downloads/list). I am looking for GWT 
V3 map API wrapper with marker cluster capabilities.

Also, I would like to know what the exact definition of a "simple map" is in 
the following Google note. Specifically, whether a "simple map" includes 
MarkerCluster, street views, StreetViewOverlay, drawing polygons on map and 
etc, which are currently being used in our application):

Google note (https://developers.google.com/maps/documentation/javascript/v2/):
"Note: The Google Maps JavaScript API Version 2 was officially deprecated on 
May 19, 2010. The original deprecation period has been extended from May 19, 
2013 until November 19, 2013. As of this date, all applications requesting v2 
will be served a special, wrapped version of the v3 API instead. We expect this 
wrapped version of the API will work for most simple maps, but we strongly 
encourage you to migrate your code to version 3 of the Maps JavaScript API 
before this date."



Original comment by s...@belairnetworks.com on 20 Jun 2013 at 3:04

@GoogleCodeExporter
Copy link
Author

@81 (belairnetworks.com)

Brandon's binding at https://github.com/branflake2267/GWT-Maps-V3-Api includes 
a MarkerCluster implementation.

It (currently) require you to use that binding rather than the Google one, but 
I recommend that anyway.

Original comment by tver...@gmail.com on 21 Jun 2013 at 6:38

@GoogleCodeExporter
Copy link
Author

I tried Brandon's binding at https://github.com/branflake2267/GWT-Maps-V3-Api. 
The GWT maps v3 api seems to work for our app. However I could NOT get 
MarkerCluster to work and got the following error while trying to use it:

com.google.gwt.core.client.JavaScriptException: (TypeError): 
$wnd.MarkerClusterer is not a constructor

Also, I couldn't find any example for MarkerCluster in Brandon's GWT maps v3 
binding.

Anyone knows  Brandon's 
com.google.gwt.maps.utility.markerclustererplus.client.MarkerCluster works or 
not and how to make it work?

BTW, for GWT maps v2 utility you need to add the following piece of code in 
onModuleLoad() to make the MarkerCluster to work:

if (!GoogleMapsUtility.isLoaded(DefaultPackage.MARKER_CLUSTERER)) 
        {
            GoogleMapsUtility.loadUtilityApi(new Runnable() 
            {
                public void run() {}
            }, DefaultPackage.MARKER_CLUSTERER);
        }
Is there an equivalent mechanism for GWT v3 map utility? 

Thanks in advance.

Original comment by s...@belairnetworks.com on 23 Aug 2013 at 8:47

@GoogleCodeExporter
Copy link
Author

The issue reported in my previous (Aug 23) comment has been resolved. Here are 
what I did:
1) download markerclusterer_compiled.js from 
http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/s
rc/  and put it directory e.g js/
2) add the following in your <gwt proj>.gwt.xml:
<inherits 
name='com.google.gwt.maps.utility.markerclustererplus.MarkerClustererPlus' />
3) add the following in your <gwt proj>.html file:
<script type="text/javascript" src="js/markerclusterer_compiled.js"></script>


Original comment by s...@belairnetworks.com on 30 Aug 2013 at 6:08

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant