Issue 381 in gwt-google-apis: Upgrade to Maps v3
gwt-goo...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 381 by dusan.maliarik: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I would like to see support for Maps v3.
gwt-goo...@googlecode.com
Status: Accepted
Labels: API-Maps
Comment #1 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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?
gwt-goo...@googlecode.com
Comment #2 on issue 381 by dusan.maliarik: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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?
gwt-goo...@googlecode.com
Comment #3 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
There is another open source project out there that has support for a good
number of features you can use:
gwt-goo...@googlecode.com
Comment #4 on issue 381 by tculshaw: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #5 on issue 381 by brendanp...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #6 on issue 381 by cetin.demir1: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I would also like to know when we can expect the third version. Thanks
gwt-goo...@googlecode.com
Comment #7 on issue 381 by pef.gomez: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Hello, any news about this ?
Can I safely start a project with gwt-google-maps-v3, or should I wait for
it to be merge ?
gwt-goo...@googlecode.com
Comment #8 on issue 381 by rasmusdahljoergensen: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
An official statement on GWT API Support and planned releases for Maps V3
would be much appreciated!
gwt-goo...@googlecode.com
Comment #9 on issue 381 by nicolas....@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #10 on issue 381 by huguerre.thomas: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I totally agree. Yesterday, I spent long hours to look for any information
on the internet (no announcement on blog, on google code, ...). Absolutely
no information.
Eric Ayers
--
You received this message because you are subscribed to the Google Groups "galgwt-issue-notifications" group.
To post to this group, send email to galgwt-issue-...@googlegroups.com.
To unsubscribe from this group, send email to galgwt-issue-notifi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/galgwt-issue-notifications?hl=en.
--
Eric Z. Ayers
Google Web Toolkit, Atlanta, GA USA
gwt-goo...@googlecode.com
Comment #11 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #12 on issue 381 by huguerre.thomas: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
And is there any date planned for an official release ? even approximative ?
gwt-goo...@googlecode.com
Comment #13 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I really need this!
Thanks,
Brandon Donnelson
http://gwt-examples.googlecode.com
gwt-goo...@googlecode.com
Comment #14 on issue 381 by terry.je...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Yes. Uncertainty is a poison pill for developers. Please keep us up to date
on the path for the version 3.
gwt-goo...@googlecode.com
Comment #15 on issue 381 by tculs...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #16 on issue 381 by treethin...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I agree completely with comment 15, but it's pretty obvious that this list
is not the place to post these requests, because no-one from Google reads
this list. The proof of that is that none of the requests since,
especially, the Aug 25 post, has been answered.
gwt-goo...@googlecode.com
Comment #17 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #18 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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".
gwt-goo...@googlecode.com
Comment #19 on issue 381 by fili...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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/
gwt-goo...@googlecode.com
Comment #20 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #21 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #22 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Now that's a bit more useful. I disagree with the place for discussion,
this sort of discussion that's going on here should happen in mailing list,
and this issue here should report on progress of matters (detailed!), so,
say, I'd like to contribute, but have no idea where to start, because this
issue here is bloated with complaints about lack of information. So let's
turn it over - tell me where and how can I start contributing to the
solution?
gwt-goo...@googlecode.com
Comment #23 on issue 381 by cow...@bbs.darktech.org: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #24 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #25 on issue 381 by jhmalp...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.)
gwt-goo...@googlecode.com
Comment #26 on issue 381 by racam...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
What is the status of this issue?
gwt-goo...@googlecode.com
Comment #27 on issue 381 by simon.w....@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
With the new limits & pricing that will be introduced on introduced on
October 1st, 2011 this issue should definately get more priority. See
pricing: http://code.google.com/apis/maps/faq.html#tos_pricing
Google will charge 2.5 fold for using the Maps v2 yet at the same time they
do not offer an official GWT Maps API for v3. IMO there should either be a
v3 api for GWT or using v2 should not be punished by making v2 users pay
250% of the v3 price.
gwt-goo...@googlecode.com
Comment #28 on issue 381 by cdwo...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Now that Google Maps v3 supports poly editing
(http://code.google.com/p/gmaps-api-issues/issues/detail?id=2432&can=1&q=poly%20editing&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Stars%20ApiType%20Internal),
can we expect some forward movement with associated GWT bindings? I would
think that poly editing was the big, missing GMap feature that was making
the development of GWT bindings seem premature.
gwt-goo...@googlecode.com
Comment #29 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I have the feeling Google has little interest in further developing GWT
bindings for their APIs. We've been begging for this to happen for a year
and we've gotten nothing. In fact, it makes me very nervous using GWT in
future projects. I feel like it could be killed off at any second like Wave
was...
gwt-goo...@googlecode.com
Comment #30 on issue 381 by jones.no...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I second that.
gwt-goo...@googlecode.com
Comment #31 on issue 381 by e...@centigonsolutions.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
We dropped GWT completely and I'd advise others to as well before you get
too far in, as this does not bode well for anything GWT.
gwt-goo...@googlecode.com
Comment #32 on issue 381 by jacques....@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I agree. I am seriously looking into replacing GWT with play / coffeescript.
gwt-goo...@googlecode.com
Comment #33 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Guys, be reasonable. Would you blame GCC team for lack of development in
libpng ? There simply is not big enough market for GWT Google APIs. GWT
itself, afaik is keeping up quite well. It has HTML5 features, and the core
of it - cross-compilation works very well.
gwt-goo...@googlecode.com
Comment #34 on issue 381 by LinuxC...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I agree with Dusan. Guys, just use gwt-openlayers and you can use any Map
API you like. Replaying GWT with something that has no IDE support is ...
eh .. not very smart.
gwt-goo...@googlecode.com
Comment #35 on issue 381 by r...@simplesmartads.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Google Maps v3 was released May 2009; 2.5 years later, GWT bindings still
do not exist. That is not a subtle hint, that's an emphatic "NO" from
Google.
gwt-goo...@googlecode.com
Comment #36 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I don't think this has anything to do with the market size of GWT Google
APIs. I think it says more about the GWT team not being sufficiently funded
to do some of the basic things, probably because of the market size of GWT.
They been given enough funding to continue developing the core product but
they are not being given enough funding to do any more than that. At some
point in the past they did have the funding to make GWT bindings for their
APIs but I guess the product didn't take off as they hoped and so it's
slowly being drained of life. It's a serious shame because I really cannot
stand working with weakly typed scripting languages for products that will
have a long shelf life. They are "easy" to get into but become a nightmare
to maintain for the same reasons they are easy. For those of us who are
investing for the long term, GWT is (or was) a great product. The absence
of API support from Google speaks loud and clear about their commitment to
its future though. I'm worried because I've got a huge investment in GWT
and I think it's about to circle the drain.
gwt-goo...@googlecode.com
Comment #37 on issue 381 by t.broyer: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
You might have noticed that http://www.google.com/flights/ is built with
GWT and uses Maps v3. So it might rather be that they prefer doing it in
JSNI than with the gwt-google-apis (I haven't looked at the compiled JS
code closely, so I really can't tell). Either that, or they use the
changes/vinays/gwt-google-maps-v3 branch or the gwt-google-maps-v3 project
(or they completed the port and/or wrote a new one internally that they
haven't yet open sourced).
One thing I can say for sure though (it's been said publicly on the GWT
forum, and reinforced privately to me too): Google uses GWT heavily
internally, on big projects; and the GWT community is vibrant. So please
stop throwing FUD on the future of GWT.
gwt-goo...@googlecode.com
Comment #38 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Rather than telling us that Google really cares about GWT, perhaps you
could push our concerns up the chain and try to secure some funding for
creating GWT bindings for your APIs. It should be obvious at this point
that your user base is getting worried about your commitment to the project
because of this oversight.
You cannot make people stop worrying by telling us everything is fine. We
see smoke, so its natural for us to believe there is a fire. You could just
put out the metaphorical fire, by creating the bindings, rather than just
insulting us by saying that smoke is a normal part of life.
We are the vibrant GWT community. We are scared. You need to know about it
or there won't be a vibrant community. This isn't FUD, its an intervention.
We are worried about you.
gwt-goo...@googlecode.com
Comment #39 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Ridiculous, you're bragging about lack of bindings for Maps API, which is
JS. There is well documented and heavily used way of using JS libraries in
GWT. I use Maps v3 in my GWT project thanks to gwt-google-maps-v3, and yes,
it wasn't updated for more than a year. Guess why? No one missed anything
in it. If you miss anything, then please stick with the OSS principles, and
as a developer implement it yourself, and submit a patch. Apparently you're
a developer, so please stop sniffing the smoke, and join the project.
Please read again a comment #20. Good luck
gwt-goo...@googlecode.com
Comment #40 on issue 381 by nico...@justmagic.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Comment #11 is why people don't want to rely on gwt-google-maps-v3. It
explicitly says that the final version will be different than
gwt-google-maps-v3. I try to be careful when I choose my dependencies, and
use official channels when I can, especially if it is explicitly told me
that everything will be rolled out as normal.
The fact is, this issue is still opened instead of being simply
marked "won't fix", while no informations nor advancement is given. It if
would have been closed, some would have just whine a little instead of
raging, and everybody would have jumped happily using gwt-google-maps-v3.
gwt-goo...@googlecode.com
Comment #41 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
A complete rewrite of all Maps related stuff seems like a pretty large
burden to place on users. I know when I started using the Maps V2 API I was
expecting that the V3 API bindings would come out and be a simple swapping
of jars in the project (minus the API key). I've not used this library you
speak of because as its not a Google project. I like to be conservative
when choosing my dependencies.
It's probably naive of me to expect backward compatibility, even from
Google. Just switching from GWT 2.3 to 2.4 crashes all the RequestFactory
clients I have in the field. Yet another significant burden placed on
users. I recall all the inculcation in university on the important of
backward compatibility. I guess that message didn't make it to the
RequestFactory folks. Considering comment #20's suggestion that the likely
way the API would be implemented would be through some automated process,
that makes it unlikely that it will be backward compatible either. As this
threads status is still "accepted" I'm hoping V3 API bindings are create
officially and that backward compatibility is on their mind.
It would be nice if Google would remove the uncertainty from this situation
and post up a timeline and expectation for completion or tell us "we are
not in the business of GWT binding creation anymore". Either way, our
pathes forward would be easier to navigate.
gwt-goo...@googlecode.com
Comment #42 on issue 381 by cdwo...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Up until a couple days ago, Maps V3 was nowhere near the functionality of
Maps V2. And the Maps team can attest that getting V3 to this point took
way longer than they had planned. The guys writing the GWT Google API
bindings are beholden to the milestones of the individual API teams (didn't
I just see preliminary bindings released for Google+?). Why would any of us
prioritize bindings to an API that's very unfinished, especially when the
existing V2 bindings suffice and the deprecation period is pretty far from
over, at least in Google time?
Backward compatibility aside, I'd like to hear more about zundel's idea of
dynamically generating the bindings from documentation. Without
understanding or looking too deeply, this process sounds very reminiscent
of what the Discovery API does. Is there any more discussion of this
concept, vis-a-vis generating Maps bindings? Sounds like the last piece
that's needed is the Maps guys to finish a JSON schema, since I don't see
it in the API Explorer. If that is indeed the case, we should be starting
(and starring) a thread over at Maps to request expedited movement on the
Maps API JSON schema.
gwt-goo...@googlecode.com
Comment #43 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I've begun writing my own maps v3 wrapper. For instance some of my notes
today on the api loading routine.
http://c.gwt-examples.com/javascriptinjection - You can keep an eye on this
site for updates on progress.
Brandon Donnelson
http://gwt-examples.googlecode.com
gwt-goo...@googlecode.com
Comment #44 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
http://c.gwt-examples.com/home/wrapping - evidence of my v3 wrapping
(LatLng) class...
gwt-goo...@googlecode.com
Comment #45 on issue 381 by treethin...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Way cool. Thanks!
gwt-goo...@googlecode.com
Comment #46 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I've heard rumor there is a new maps api in testing internally?
This is my current progress on writing a third party maps v3 api. I'm
walking the classes slowly.
https://docs.google.com/spreadsheet/ccc?key=0AnyjOBpyOTUWdHpQZTl1UWJUUGxEcjBzYlBEcUVGZUE
Note
this is not written in stone and may change.)
Brandon Donnelson
http://c.gwt-examples.com
http://gwt-examples.googlecode.com
gwt-goo...@googlecode.com
Comment #47 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I also heard that rumor, first hand from a Google employee (I don't know if
that makes it more or less reliable though). He said that it was
an "automatically" generated library and currently about a month old.
gwt-goo...@googlecode.com
Comment #48 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
FYI: Update on progress >
- I'm producing some quick demos to flush out some of the rendering basics.
http://gonevertical-apis.appspot.com
- http://c.gwt-examples.com/api/google-maps-v3 - Consolidated links to all
my map stuff
-
https://docs.google.com/spreadsheet/ccc?key=0AnyjOBpyOTUWdHpQZTl1UWJUUGxEcjBzYlBEcUVGZUE
- Build progress
- I can't promise a repository commit date yet. It's possible <= 2[+]
weeks. (no promise yet, but watch the build progress on spreadsheet if your
interested)
gwt-goo...@googlecode.com
Comment #49 on issue 381 by alexis.h...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Will that be integrated in the official GWT Google APIs ?
Have you already some code to play with, before more stable classes ?
Thanks.
gwt-goo...@googlecode.com
Comment #50 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
My first goal at the moment is to write the code. I'll submit it at some
point if it can meet or beat expectations.
I haven't committed my source code yet, but soon. I'm going to finish the
library and StreetView classes and then evaluate if I can release before
wrapping the service classes.
Brandon
gwt-goo...@googlecode.com
Comment #51 on issue 381 by branflak...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Here is my *Alpha* GWT Maps V3 API source and demo.
- Nothing is frozen yet.
- Things will change.
- Its not polished yet.
- I have much work still awaits, but currently its producing good results.
http://code.google.com/p/gwt-maps-api/source/browse/#svn%2Ftrunk%2FApis_Google_Maps%2Fsrc%2Fcom%2Fgoogle%2Fgwt%2Fmaps%2Fclient
-
main source branch
http://gonevertical-apis.appspot.com - demo
On my coding horizon:
- services classes
- demo I can apply selenium testing to
- more... :)
I've decided just to go ahead and move it into the repository sooner than
later even though it's not as far as I'd like. :)
gwt-goo...@googlecode.com
Comment #52 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Hey! That looks great! Awesome job. I didn't look at the sources yet, but,
could you publish some javadoc to give us an idea what the API looks like?
gwt-goo...@googlecode.com
Status: Started
Comment #53 on issue 381 by zun...@google.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
We've worked with the Maps team to create an updated GWT bindings API for
Maps v3. I've updated a pre-release now that you can check out at:
http://code.google.com/p/gwt-google-apis/downloads/detail?name=gwt-maps-3.8.0-pre1.zip
This API is automatically generated from metadata coming of the JS API, so
some
of the conventions might be a little odd to Java programmers. For the
casually curious, you can peruse the javadoc:
http://gwt-google-apis.googlecode.com/svntrunk/javadoc/maps/3.8/index.html
gwt-goo...@googlecode.com
Comment #54 on issue 381 by z...@comerge.net: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Thanks guys!
gwt-goo...@googlecode.com
Comment #55 on issue 381 by tra...@traviswebb.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #56 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I totally agree with you, but I've asked Google this very questions and the
response was paraphrased..."Adwords is our flagship product".
gwt-goo...@googlecode.com
Comment #57 on issue 381 by sys...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
So, is a final 3.8.0 api ever going to be released?
gwt-goo...@googlecode.com
Comment #58 on issue 381 by pstron...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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!
gwt-goo...@googlecode.com
Comment #59 on issue 381 by rtr...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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-throws-javascriptexception-map-is-not-define
I switched to branflak's API which seems to work well.
http://gonevertical-apis.appspot.com/
gwt-goo...@googlecode.com
Comment #60 on issue 381 by sys...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #61 on issue 381 by dusan.ma...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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/
gwt-goo...@googlecode.com
Comment #62 on issue 381 by k...@koma.be: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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..
gwt-goo...@googlecode.com
Comment #63 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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...
gwt-goo...@googlecode.com
Comment #64 on issue 381 by t.broyer: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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).
gwt-goo...@googlecode.com
Comment #65 on issue 381 by ad...@dualsportmaps.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
I meant maps as in maps.google.com. Which as far as I can tell is not GWT.
gwt-goo...@googlecode.com
Comment #66 on issue 381 by asim...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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?
gwt-goo...@googlecode.com
Comment #67 on issue 381 by tom...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #68 on issue 381 by sys...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Tomer..... could not agree more with you.
Got the same email, and I am a bit lost as to what to do right now.
gwt-goo...@googlecode.com
Comment #69 on issue 381 by pether.s...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
Hi,
Have used http://code.google.com/p/gwt-maps3/ , provides som base
functionality.
gwt-goo...@googlecode.com
Comment #70 on issue 381 by sys...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #71 on issue 381 by sark...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #72 on issue 381 by googelyb...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
There is an official binding (see comment 53)?
it's quite outdated (still maps 3.8) but it seems to work:
http://code.google.com/p/gwt-google-apis/downloads/detail?name=gwt-maps-3.8.0-pre1.zip
gwt-goo...@googlecode.com
Comment #73 on issue 381 by googelyb...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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-pre1.zip
gwt-goo...@googlecode.com
Comment #74 on issue 381 by treethin...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #75 on issue 381 by jdpatterson: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
If jar linked above also contains the source and hence Javadoc will be
displayed in your IDE.
I wrote up an example of using the pre-release with HTML5 geolocation here:
http://blog.vercer.com/2012/12/google-maps-v3-with-gwt-example.html
gwt-goo...@googlecode.com
Comment #76 on issue 381 by jdpatterson: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #77 on issue 381 by thin...@mac.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
gwt-goo...@googlecode.com
Comment #78 on issue 381 by dg.sicon...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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!
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
gwt-goo...@googlecode.com
Comment #79 on issue 381 by sudd.gh...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #80 on issue 381 by sjbarb...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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/
gwt-goo...@googlecode.com
Comment #81 on issue 381 by s...@belairnetworks.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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
simple maps, but we strongly encourage you to migrate your code to version
3 of the Maps JavaScript API before this date."
gwt-goo...@googlecode.com
Comment #82 on issue 381 by tver...@gmail.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
@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.
gwt-goo...@googlecode.com
Comment #83 on issue 381 by s...@belairnetworks.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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.
gwt-goo...@googlecode.com
Comment #84 on issue 381 by s...@belairnetworks.com: Upgrade to Maps v3
http://code.google.com/p/gwt-google-apis/issues/detail?id=381
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/src/
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>