Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have
version aliasing implemented, so you'll need to specify the "e" if
you're hard-coding to those version for whatever reason.
There are currently no changes in 2.130d.
As always, please discuss anything in the forum that you think may be
a regression and report in the issue tracker if others confirm your
suspicions.
On Sep 28, 11:54 pm, "pamela (Google Employee)" <pamela....@gmail.com>
wrote:
> Hey developers-
> Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have
> version aliasing implemented, so you'll need to specify the "e" if
> you're hard-coding to those version for whatever reason.
> There are currently no changes in 2.130d.
> As always, please discuss anything in the forum that you think may be
> a regression and report in the issue tracker if others confirm your
> suspicions.
> > Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have
> > version aliasing implemented, so you'll need to specify the "e" if
> > you're hard-coding to those version for whatever reason.
> > There are currently no changes in 2.130d.
> > As always, please discuss anything in the forum that you think may be
> > a regression and report in the issue tracker if others confirm your
> > suspicions.
> > > Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have
> > > version aliasing implemented, so you'll need to specify the "e" if
> > > you're hard-coding to those version for whatever reason.
> > > There are currently no changes in 2.130d.
> > > As always, please discuss anything in the forum that you think may be
> > > a regression and report in the issue tracker if others confirm your
> > > suspicions.
Since v2.118, I applied elapsed time from GMap API js request to
infowindowopen on the test page below and I've been monitoring the
performance of v2.x and v2 against v2.118 (pre-modularization of
GInfoWindow).
> Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have
> version aliasing implemented, so you'll need to specify the "e" if
> you're hard-coding to those version for whatever reason.
> There are currently no changes in 2.130d.
> As always, please discuss anything in the forum that you think may be
> a regression and report in the issue tracker if others confirm your
> suspicions.
>Since v2.118, I applied elapsed time from GMap API js request to >infowindowopen on the test page below and I've been monitoring the >performance of v2.x and v2 against v2.118 (pre-modularization of >GInfoWindow).
One of the other things that affects the speed of that page is that GLog() got modularized in v2.125.
On Thu, Oct 2, 2008 at 3:34 AM, Mike Williams <nos...@econym.demon.co.uk> wrote:
> Wasn't it the1geek who wrote: >>Since v2.118, I applied elapsed time from GMap API js request to >>infowindowopen on the test page below and I've been monitoring the >>performance of v2.x and v2 against v2.118 (pre-modularization of >>GInfoWindow).
> One of the other things that affects the speed of that page is that > GLog() got modularized in v2.125.
Hi all, I would like to mark a spot on Google Map using Djangoo. I have the locations in my Database in Djangoo and would like to mark these spots on Google Map. Please let me know if you know how! Thanks MITS
On Sun, Oct 5, 2008 at 9:03 AM, pamela (Google Employee) <
> The team's aware that additional time is taken to load in modules, and > we have a few ideas for how to reduce that.
> - pamela
> On Thu, Oct 2, 2008 at 3:34 AM, Mike Williams <nos...@econym.demon.co.uk> > wrote:
> > Wasn't it the1geek who wrote: > >>Since v2.118, I applied elapsed time from GMap API js request to > >>infowindowopen on the test page below and I've been monitoring the > >>performance of v2.x and v2 against v2.118 (pre-modularization of > >>GInfoWindow).
> > One of the other things that affects the speed of that page is that > > GLog() got modularized in v2.125.
Farzad Kanani wrote: > Hi all, > I would like to mark a spot on Google Map using Djangoo. I have the > locations in my Database in Djangoo and would like to mark these spots > on Google Map. Please let me know if you know how! > Thanks > MITS
please start a new thread with an appropriate title... or better yep follow the steps.. step one of your answer includes knowing GMarkers and how to use them.(read documentation ... look at various tutorials or any of a million examples folks have posted. and try a basic example of your own). step 2 is knowing django and how to use it thats server side and has very little to do with the api... step 3 is putting those together trust me..it shouldnt be hard if you have step 1 and 2...then step 4 if for some wierd reason step 3 doesnt work. follow the group posting guidelines so we can properly help you. heck even if step 1 doesnt work follow group posting guidelines...
But please do dont expect the group to do step 2 or skip over it all and do step 3 for you.
> On Sun, Oct 5, 2008 at 9:03 AM, pamela (Google Employee) > <pamela...@gmail.com <mailto:pamela...@gmail.com>> wrote:
> Hi Newton-
> The team's aware that additional time is taken to load in modules, and > we have a few ideas for how to reduce that.
> - pamela
> On Thu, Oct 2, 2008 at 3:34 AM, Mike Williams > <nos...@econym.demon.co.uk <mailto:nos...@econym.demon.co.uk>> wrote:
> > Wasn't it the1geek who wrote: > >>Since v2.118, I applied elapsed time from GMap API js request to > >>infowindowopen on the test page below and I've been monitoring the > >>performance of v2.x and v2 against v2.118 (pre-modularization of > >>GInfoWindow).
> > One of the other things that affects the speed of that page is that > > GLog() got modularized in v2.125.
> Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have > version aliasing implemented, so you'll need to specify the "e" if > you're hard-coding to those version for whatever reason.
> There are currently no changes in 2.130d.
> As always, please discuss anything in the forum that you think may be > a regression and report in the issue tracker if others confirm your > suspicions.
