GALGWT for the Maps API deprecated???
6 views
Skip to first unread message
MonkeyMike
May 30, 2008, 4:48:00 PM5/30/08
to Google Web Toolkit, mi...@nileproject.com
Hello...
There was a lot of confusion yesterday at the Google I/O
conference, as I bounced between Googlers from the Maps API team and
the GWT team, asking both about why I haven't been able to find a GWT
wrapper for the Maps API. We currently use a 3rd party library by
mapitz, which isn't so good, and we are looking forward to having
libraries from Google, thermselves.
After learning the term "GALGWT" at the conference, I finally found
myself looking in the right place...
http://code.google.com/p/gwt-google-apis/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount
...but notice that the Maps portion (along with everything else except
for Gears) is deprecated! Doh!
We are anxious to start using this, and I am tempted to pull in the
deprecated version, but I'm sure it is deprecated for a good reason.
Can anyone share that reason? If it is related only to a portion
of the API, then it's quite possible that it might not be relevant to
our application's usage. Also, is there a target for a non-deprecated
version of the API? Very much looking forward to this.
- Monkey Mike
There was a lot of confusion yesterday at the Google I/O
conference, as I bounced between Googlers from the Maps API team and
the GWT team, asking both about why I haven't been able to find a GWT
wrapper for the Maps API. We currently use a 3rd party library by
mapitz, which isn't so good, and we are looking forward to having
libraries from Google, thermselves.
After learning the term "GALGWT" at the conference, I finally found
myself looking in the right place...
http://code.google.com/p/gwt-google-apis/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount
...but notice that the Maps portion (along with everything else except
for Gears) is deprecated! Doh!
We are anxious to start using this, and I am tempted to pull in the
deprecated version, but I'm sure it is deprecated for a good reason.
Can anyone share that reason? If it is related only to a portion
of the API, then it's quite possible that it might not be relevant to
our application's usage. Also, is there a target for a non-deprecated
version of the API? Very much looking forward to this.
- Monkey Mike
markmccall
May 30, 2008, 4:58:52 PM5/30/08
to Google Web Toolkit
Miguel explains why they are deprecated in the last post of this
thread:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/daa9a44079aeeba/ca7e213bbc679640
On May 30, 4:48 pm, MonkeyMike <mikebin...@gmail.com> wrote:
> Hello...
>
> There was a lot of confusion yesterday at the Google I/O
> conference, as I bounced between Googlers from the Maps API team and
> the GWT team, asking both about why I haven't been able to find a GWT
> wrapper for the Maps API. We currently use a 3rd party library by
> mapitz, which isn't so good, and we are looking forward to having
> libraries from Google, thermselves.
>
> After learning the term "GALGWT" at the conference, I finally found
> myself looking in the right place...
>
> http://code.google.com/p/gwt-google-apis/downloads/list?can=1&q=&cols...
thread:
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/daa9a44079aeeba/ca7e213bbc679640
On May 30, 4:48 pm, MonkeyMike <mikebin...@gmail.com> wrote:
> Hello...
>
> There was a lot of confusion yesterday at the Google I/O
> conference, as I bounced between Googlers from the Maps API team and
> the GWT team, asking both about why I haven't been able to find a GWT
> wrapper for the Maps API. We currently use a 3rd party library by
> mapitz, which isn't so good, and we are looking forward to having
> libraries from Google, thermselves.
>
> After learning the term "GALGWT" at the conference, I finally found
> myself looking in the right place...
>
Eric Ayers
May 30, 2008, 5:08:37 PM5/30/08
to Google-We...@googlegroups.com, mi...@nileproject.com
Hi Mike,
I'm glad to hear of your interest. Since these early 'milestone' releases may have bugs, we don't want users to accidentally get pre-release software - that's the only reason they are marked deprecated. I strongly feel that gwt-google-apis r290 is the version that you should start out with if you aren't constrained to the GWT 1.4 release.
We are working toward a release candidate, but don't have a firm date.
-Eric.--
Eric Z. Ayers - GWT Team - Atlanta, GA USA
http://code.google.com/webtoolkit/
I'm glad to hear of your interest. Since these early 'milestone' releases may have bugs, we don't want users to accidentally get pre-release software - that's the only reason they are marked deprecated. I strongly feel that gwt-google-apis r290 is the version that you should start out with if you aren't constrained to the GWT 1.4 release.
We are working toward a release candidate, but don't have a firm date.
-Eric.
Eric Z. Ayers - GWT Team - Atlanta, GA USA
http://code.google.com/webtoolkit/
MonkeyMike
May 30, 2008, 6:46:37 PM5/30/08
to Google Web Toolkit
Hi Eric,
Thanks for the heads-up. I am just about to pull GWT 1.5 into the
product, and so it sounds like once that is done I can start tinkering
with the r290 version of GALGWT for maps.
Thanks again! :)
-Monkey Mike
On May 30, 2:08 pm, "Eric Ayers" <zun...@google.com> wrote:
> Hi Mike,
>
> I'm glad to hear of your interest. Since these early 'milestone' releases
> may have bugs, we don't want users to accidentally get pre-release software
> - that's the only reason they are marked deprecated. I strongly feel that
> gwt-google-apis r290 is the version that you should start out with if you
> aren't constrained to the GWT 1.4 release.
>
> We are working toward a release candidate, but don't have a firm date.
>
> -Eric.
>
>
>
> On Fri, May 30, 2008 at 4:48 PM, MonkeyMike <mikebin...@gmail.com> wrote:
>
> > Hello...
>
> > There was a lot of confusion yesterday at the Google I/O
> > conference, as I bounced between Googlers from the Maps API team and
> > the GWT team, asking both about why I haven't been able to find a GWT
> > wrapper for the Maps API. We currently use a 3rd party library by
> > mapitz, which isn't so good, and we are looking forward to having
> > libraries from Google, thermselves.
>
> > After learning the term "GALGWT" at the conference, I finally found
> > myself looking in the right place...
>
> >http://code.google.com/p/gwt-google-apis/downloads/list?can=1&q=&cols...
Thanks for the heads-up. I am just about to pull GWT 1.5 into the
product, and so it sounds like once that is done I can start tinkering
with the r290 version of GALGWT for maps.
Thanks again! :)
-Monkey Mike
On May 30, 2:08 pm, "Eric Ayers" <zun...@google.com> wrote:
> Hi Mike,
>
> I'm glad to hear of your interest. Since these early 'milestone' releases
> may have bugs, we don't want users to accidentally get pre-release software
> - that's the only reason they are marked deprecated. I strongly feel that
> gwt-google-apis r290 is the version that you should start out with if you
> aren't constrained to the GWT 1.4 release.
>
> We are working toward a release candidate, but don't have a firm date.
>
> -Eric.
>
>
>
> On Fri, May 30, 2008 at 4:48 PM, MonkeyMike <mikebin...@gmail.com> wrote:
>
> > Hello...
>
> > There was a lot of confusion yesterday at the Google I/O
> > conference, as I bounced between Googlers from the Maps API team and
> > the GWT team, asking both about why I haven't been able to find a GWT
> > wrapper for the Maps API. We currently use a 3rd party library by
> > mapitz, which isn't so good, and we are looking forward to having
> > libraries from Google, thermselves.
>
> > After learning the term "GALGWT" at the conference, I finally found
> > myself looking in the right place...
>
MonkeyMike
May 30, 2008, 9:03:47 PM5/30/08
to Google Web Toolkit
Haha! Just pulled GWT 1.5 in, and it turns out that the 1.5 compiler
doesn't like the mapitz library! So a minute ago I was saying that
being able to upgrade to the GALGWT maps library was yet another
reason to upgrade to GWT 1.5... and now I've realized that upgrading
to GWT 1.5 is yet another reason to upgrade to the GALGWT maps
library! It's circular! Ugh...
-Monkey Mike
doesn't like the mapitz library! So a minute ago I was saying that
being able to upgrade to the GALGWT maps library was yet another
reason to upgrade to GWT 1.5... and now I've realized that upgrading
to GWT 1.5 is yet another reason to upgrade to the GALGWT maps
library! It's circular! Ugh...
-Monkey Mike
Reply all
Reply to author
Forward
0 new messages