Currently, there are a few ways to load in the Maps API:
1) Use maps.google.com/maps?file=api: This puts global classes in your
page like GMarker, GMap, etc.
2) Use maps.google.com/maps?file=googleapi or use the AJAX common
loader: This puts both the global classes in your page as well as
namespaced classes like google.maps.Marker, google.maps.Map, etc.
3) Use maps.google.com/maps?file=googleapionly: This puts just the
namespaced classes in your page.
We introduced namespaces along with the common loader to encourage a
more unified way of coding against Google AJAX APIs, but we kept the
prefixed "G" classes to not confused the current developers. However,
currently it's difficult to write extensions (like the LocalSearch
Control) for developers, as one has to search the DOM for both a
prefixed class or a namespaced class, and then use the appropriate
class. To make it easier for developers to create extensions that work
independent of loading technique and to encourage more developers to
use the common AJAX namespace, we will soon introduce a change that
will also pass down the namespaced class with technique #1.
Let me know if you have any concerns or questions.
One is very tempted to say "If it ain't broke don't fix it!". However
I can see the logic and it means I can get my feet wet by using either
classing for a while without changing the script invocation.
As soon as the AJAX common loader came out I told myself I should
change my code, but inertia can be a very strong force! (and the "If
it ain't broke don't fix it!" philosophy!)
> Currently, there are a few ways to load in the Maps API:
> 1) Use maps.google.com/maps?file=api: This puts global classes in your > page like GMarker, GMap, etc.
> 2) Use maps.google.com/maps?file=googleapi or use the AJAX common > loader: This puts both the global classes in your page as well as > namespaced classes like google.maps.Marker, google.maps.Map, etc.
> 3) Use maps.google.com/maps?file=googleapionly: This puts just the > namespaced classes in your page.
> We introduced namespaces along with the common loader to encourage a > more unified way of coding against Google AJAX APIs, but we kept the > prefixed "G" classes to not confused the current developers. However, > currently it's difficult to write extensions (like the LocalSearch > Control) for developers, as one has to search the DOM for both a > prefixed class or a namespaced class, and then use the appropriate > class. To make it easier for developers to create extensions that work > independent of loading technique and to encourage more developers to > use the common AJAX namespace, we will soon introduce a change that > will also pass down the namespaced class with technique #1.
> Let me know if you have any concerns or questions.
> - pamela
This feels like a coincidence of timing... I was just thinking I might want a GClientLocation or would that be GLoader.clientLocation or something of that sort.
Ok, maybe I'll check out that mountain. I'm sure I'll need to come to Brisbane sometime anyway. :)
Lance- ClientLocation will still only be available to those using the actual AJAX Common Loader (www.google.com/jsapi), as that uses a particular mechanism on their script-serving server that we won't be enabling on ours anytime soon.
On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> wrote:
> pamela (Google Employee) wrote: > > Hi developers-
> > Currently, there are a few ways to load in the Maps API:
> > 1) Use maps.google.com/maps?file=api: This puts global classes in your > > page like GMarker, GMap, etc.
> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common > > loader: This puts both the global classes in your page as well as > > namespaced classes like google.maps.Marker, google.maps.Map, etc.
> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the > > namespaced classes in your page.
> > We introduced namespaces along with the common loader to encourage a > > more unified way of coding against Google AJAX APIs, but we kept the > > prefixed "G" classes to not confused the current developers. However, > > currently it's difficult to write extensions (like the LocalSearch > > Control) for developers, as one has to search the DOM for both a > > prefixed class or a namespaced class, and then use the appropriate > > class. To make it easier for developers to create extensions that work > > independent of loading technique and to encourage more developers to > > use the common AJAX namespace, we will soon introduce a change that > > will also pass down the namespaced class with technique #1.
> > Let me know if you have any concerns or questions.
> > - pamela
> This feels like a coincidence of timing... > I was just thinking I might want a GClientLocation or would that be > GLoader.clientLocation > or something of that sort.
> Ok, maybe I'll check out that mountain. I'm sure I'll need to come to > Brisbane sometime anyway. :)
> Lance- > ClientLocation will still only be available to those using the actual AJAX > Common Loader (www.google.com/jsapi), as that uses a particular mechanism > on their script-serving server that we won't be enabling on ours anytime > soon.
> - pamela
> On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> wrote:
>> pamela (Google Employee) wrote: >> > Hi developers-
>> > Currently, there are a few ways to load in the Maps API:
>> > 1) Use maps.google.com/maps?file=api: This puts global classes in your >> > page like GMarker, GMap, etc.
>> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common >> > loader: This puts both the global classes in your page as well as >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
>> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the >> > namespaced classes in your page.
>> > We introduced namespaces along with the common loader to encourage a >> > more unified way of coding against Google AJAX APIs, but we kept the >> > prefixed "G" classes to not confused the current developers. However, >> > currently it's difficult to write extensions (like the LocalSearch >> > Control) for developers, as one has to search the DOM for both a >> > prefixed class or a namespaced class, and then use the appropriate >> > class. To make it easier for developers to create extensions that work >> > independent of loading technique and to encourage more developers to >> > use the common AJAX namespace, we will soon introduce a change that >> > will also pass down the namespaced class with technique #1.
>> > Let me know if you have any concerns or questions.
>> > - pamela
>> This feels like a coincidence of timing... >> I was just thinking I might want a GClientLocation or would that be >> GLoader.clientLocation >> or something of that sort.
-- Bjorn Brala ---------------- GeoStart.nl- Google maps - Swis Webdesign
This doesn't actually mean there will be no more maps stuff in the
global namespace. If we did that for the normal loader, then
everyone's code would stop working. :/
If you actually want only namespaced classes, then you can request
&file=googleapionly. That's not documented anywhere, however.
- pamela
On Oct 27, 4:32 pm, "Björn Brala" <bbr...@gmail.com> wrote:
> > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to
> > Brisbane sometime anyway. :)
> > Lance-
> > ClientLocation will still only be available to those using the actual AJAX
> > Common Loader (www.google.com/jsapi), as that uses a particular mechanism
> > on their script-serving server that we won't be enabling on ours anytime
> > soon.
> > - pamela
> > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> wrote:
> >> > Currently, there are a few ways to load in the Maps API:
> >> > 1) Use maps.google.com/maps?file=api: This puts global classes in your
> >> > page like GMarker, GMap, etc.
> >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common
> >> > loader: This puts both the global classes in your page as well as
> >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
> >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the
> >> > namespaced classes in your page.
> >> > We introduced namespaces along with the common loader to encourage a
> >> > more unified way of coding against Google AJAX APIs, but we kept the
> >> > prefixed "G" classes to not confused the current developers. However,
> >> > currently it's difficult to write extensions (like the LocalSearch
> >> > Control) for developers, as one has to search the DOM for both a
> >> > prefixed class or a namespaced class, and then use the appropriate
> >> > class. To make it easier for developers to create extensions that work
> >> > independent of loading technique and to encourage more developers to
> >> > use the common AJAX namespace, we will soon introduce a change that
> >> > will also pass down the namespaced class with technique #1.
> >> > Let me know if you have any concerns or questions.
> >> > - pamela
> >> This feels like a coincidence of timing...
> >> I was just thinking I might want a GClientLocation or would that be
> >> GLoader.clientLocation
> >> or something of that sort.
> > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to
> > Brisbane sometime anyway. :)
> > Lance-
> > ClientLocation will still only be available to those using the actual AJAX
> > Common Loader (www.google.com/jsapi), as that uses a particular mechanism
> > on their script-serving server that we won't be enabling on ours anytime
> > soon.
> > - pamela
> > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> wrote:
> >> > Currently, there are a few ways to load in the Maps API:
> >> > 1) Use maps.google.com/maps?file=api: This puts global classes in your
> >> > page like GMarker, GMap, etc.
> >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common
> >> > loader: This puts both the global classes in your page as well as
> >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
> >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the
> >> > namespaced classes in your page.
> >> > We introduced namespaces along with the common loader to encourage a
> >> > more unified way of coding against Google AJAX APIs, but we kept the
> >> > prefixed "G" classes to not confused the current developers. However,
> >> > currently it's difficult to write extensions (like the LocalSearch
> >> > Control) for developers, as one has to search the DOM for both a
> >> > prefixed class or a namespaced class, and then use the appropriate
> >> > class. To make it easier for developers to create extensions that work
> >> > independent of loading technique and to encourage more developers to
> >> > use the common AJAX namespace, we will soon introduce a change that
> >> > will also pass down the namespaced class with technique #1.
> >> > Let me know if you have any concerns or questions.
> >> > - pamela
> >> This feels like a coincidence of timing...
> >> I was just thinking I might want a GClientLocation or would that be
> >> GLoader.clientLocation
> >> or something of that sort.
It would make developing google maps a lot easier if there was no junk in the global namespace :) I understand that it would break most maps if it would be default, but a documented flag would be a very very welcome addidtion, perhaps i should file a feature request.
Im kinda scared to change my whole system on the fact that the "googleapionly" flag will perhaps not even stay availabkle :)
> This doesn't actually mean there will be no more maps stuff in the > global namespace. If we did that for the normal loader, then > everyone's code would stop working. :/ > If you actually want only namespaced classes, then you can request > &file=googleapionly. That's not documented anywhere, however.
> - pamela
> On Oct 27, 4:32 pm, "Björn Brala" <bbr...@gmail.com> wrote: > > Im so happy to read this, finally a proper namespace for the google maps > > stuff :P
> > I've missed that for ages. This will mean there will be no google maps > stuff > > in the global namespace?
> > > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to > > > Brisbane sometime anyway. :)
> > > Lance- > > > ClientLocation will still only be available to those using the actual > AJAX > > > Common Loader (www.google.com/jsapi), as that uses a particular > mechanism > > > on their script-serving server that we won't be enabling on ours > anytime > > > soon.
> > > - pamela
> > > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> > wrote:
> > >> > Currently, there are a few ways to load in the Maps API:
> > >> > 1) Use maps.google.com/maps?file=api: This puts global classes in > your > > >> > page like GMarker, GMap, etc.
> > >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common > > >> > loader: This puts both the global classes in your page as well as > > >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
> > >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the > > >> > namespaced classes in your page.
> > >> > We introduced namespaces along with the common loader to encourage a > > >> > more unified way of coding against Google AJAX APIs, but we kept the > > >> > prefixed "G" classes to not confused the current developers. > However, > > >> > currently it's difficult to write extensions (like the LocalSearch > > >> > Control) for developers, as one has to search the DOM for both a > > >> > prefixed class or a namespaced class, and then use the appropriate > > >> > class. To make it easier for developers to create extensions that > work > > >> > independent of loading technique and to encourage more developers to > > >> > use the common AJAX namespace, we will soon introduce a change that > > >> > will also pass down the namespaced class with technique #1.
> > >> > Let me know if you have any concerns or questions.
> > >> > - pamela
> > >> This feels like a coincidence of timing... > > >> I was just thinking I might want a GClientLocation or would that be > > >> GLoader.clientLocation > > >> or something of that sort.
On Wed, Oct 29, 2008 at 5:02 PM, Björn Brala <bbr...@gmail.com> wrote:
> It would make developing google maps a lot easier if there was no junk in
> the global namespace :) I understand that it would break most maps if it
> would be default, but a documented flag would be a very very welcome
> addidtion, perhaps i should file a feature request.
> Im kinda scared to change my whole system on the fact that the
> "googleapionly" flag will perhaps not even stay availabkle :)
>> This doesn't actually mean there will be no more maps stuff in the
>> global namespace. If we did that for the normal loader, then
>> everyone's code would stop working. :/
>> If you actually want only namespaced classes, then you can request
>> &file=googleapionly. That's not documented anywhere, however.
>> - pamela
>> On Oct 27, 4:32 pm, "Björn Brala" <bbr...@gmail.com> wrote:
>> > Im so happy to read this, finally a proper namespace for the google maps
>> > stuff :P
>> > I've missed that for ages. This will mean there will be no google maps
>> stuff
>> > in the global namespace?
>> > > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to
>> > > Brisbane sometime anyway. :)
>> > > Lance-
>> > > ClientLocation will still only be available to those using the actual
>> AJAX
>> > > Common Loader (www.google.com/jsapi), as that uses a particular
>> mechanism
>> > > on their script-serving server that we won't be enabling on ours
>> anytime
>> > > soon.
>> > > - pamela
>> > > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com>
>> wrote:
>> > >> > Currently, there are a few ways to load in the Maps API:
>> > >> > 1) Use maps.google.com/maps?file=api: This puts global classes in
>> your
>> > >> > page like GMarker, GMap, etc.
>> > >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common
>> > >> > loader: This puts both the global classes in your page as well as
>> > >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
>> > >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the
>> > >> > namespaced classes in your page.
>> > >> > We introduced namespaces along with the common loader to encourage
>> a
>> > >> > more unified way of coding against Google AJAX APIs, but we kept
>> the
>> > >> > prefixed "G" classes to not confused the current developers.
>> However,
>> > >> > currently it's difficult to write extensions (like the LocalSearch
>> > >> > Control) for developers, as one has to search the DOM for both a
>> > >> > prefixed class or a namespaced class, and then use the appropriate
>> > >> > class. To make it easier for developers to create extensions that
>> work
>> > >> > independent of loading technique and to encourage more developers
>> to
>> > >> > use the common AJAX namespace, we will soon introduce a change that
>> > >> > will also pass down the namespaced class with technique #1.
>> > >> > Let me know if you have any concerns or questions.
>> > >> > - pamela
>> > >> This feels like a coincidence of timing...
>> > >> I was just thinking I might want a GClientLocation or would that be
>> > >> GLoader.clientLocation
>> > >> or something of that sort.
> It would make developing google maps a lot easier if there was no junk in > the global namespace :) I understand that it would break most maps if it > would be default, but a documented flag would be a very very welcome > addidtion, perhaps i should file a feature request.
> Im kinda scared to change my whole system on the fact that the > "googleapionly" flag will perhaps not even stay availabkle :)
>> This doesn't actually mean there will be no more maps stuff in the >> global namespace. If we did that for the normal loader, then >> everyone's code would stop working. :/ >> If you actually want only namespaced classes, then you can request >> &file=googleapionly. That's not documented anywhere, however.
>> - pamela
>> On Oct 27, 4:32 pm, "Björn Brala" <bbr...@gmail.com> wrote: >> > Im so happy to read this, finally a proper namespace for the google maps >> > stuff :P
>> > I've missed that for ages. This will mean there will be no google maps >> stuff >> > in the global namespace?
>> > > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to >> > > Brisbane sometime anyway. :)
>> > > Lance- >> > > ClientLocation will still only be available to those using the actual >> AJAX >> > > Common Loader (www.google.com/jsapi), as that uses a particular >> mechanism >> > > on their script-serving server that we won't be enabling on ours >> anytime >> > > soon.
>> > > - pamela
>> > > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> >> wrote:
>> > >> > Currently, there are a few ways to load in the Maps API:
>> > >> > 1) Use maps.google.com/maps?file=api: This puts global classes in >> your >> > >> > page like GMarker, GMap, etc.
>> > >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common >> > >> > loader: This puts both the global classes in your page as well as >> > >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
>> > >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just the >> > >> > namespaced classes in your page.
>> > >> > We introduced namespaces along with the common loader to encourage >> a >> > >> > more unified way of coding against Google AJAX APIs, but we kept >> the >> > >> > prefixed "G" classes to not confused the current developers. >> However, >> > >> > currently it's difficult to write extensions (like the LocalSearch >> > >> > Control) for developers, as one has to search the DOM for both a >> > >> > prefixed class or a namespaced class, and then use the appropriate >> > >> > class. To make it easier for developers to create extensions that >> work >> > >> > independent of loading technique and to encourage more developers >> to >> > >> > use the common AJAX namespace, we will soon introduce a change that >> > >> > will also pass down the namespaced class with technique #1.
>> > >> > Let me know if you have any concerns or questions.
>> > >> > - pamela
>> > >> This feels like a coincidence of timing... >> > >> I was just thinking I might want a GClientLocation or would that be >> > >> GLoader.clientLocation >> > >> or something of that sort.
> Hi Bjorn- > I'll check with the team and see our feelings on documenting support for > googleapionly.
> - pamela
> On Wed, Oct 29, 2008 at 5:02 PM, Björn Brala <bbr...@gmail.com> wrote:
>> It would make developing google maps a lot easier if there was no junk in >> the global namespace :) I understand that it would break most maps if it >> would be default, but a documented flag would be a very very welcome >> addidtion, perhaps i should file a feature request.
>> Im kinda scared to change my whole system on the fact that the >> "googleapionly" flag will perhaps not even stay availabkle :)
>>> This doesn't actually mean there will be no more maps stuff in the >>> global namespace. If we did that for the normal loader, then >>> everyone's code would stop working. :/ >>> If you actually want only namespaced classes, then you can request >>> &file=googleapionly. That's not documented anywhere, however.
>>> - pamela
>>> On Oct 27, 4:32 pm, "Björn Brala" <bbr...@gmail.com> wrote: >>> > Im so happy to read this, finally a proper namespace for the google >>> maps >>> > stuff :P
>>> > I've missed that for ages. This will mean there will be no google maps >>> stuff >>> > in the global namespace?
>>> > > Ok, maybe I'll check out that mountain. I'm sure I'll need to come to >>> > > Brisbane sometime anyway. :)
>>> > > Lance- >>> > > ClientLocation will still only be available to those using the actual >>> AJAX >>> > > Common Loader (www.google.com/jsapi), as that uses a particular >>> mechanism >>> > > on their script-serving server that we won't be enabling on ours >>> anytime >>> > > soon.
>>> > > - pamela
>>> > > On Thu, Oct 23, 2008 at 9:36 PM, Lance Dyas <lance...@inetnebr.com> >>> wrote:
>>> > >> > Currently, there are a few ways to load in the Maps API:
>>> > >> > 1) Use maps.google.com/maps?file=api: This puts global classes in >>> your >>> > >> > page like GMarker, GMap, etc.
>>> > >> > 2) Use maps.google.com/maps?file=googleapi or use the AJAX common >>> > >> > loader: This puts both the global classes in your page as well as >>> > >> > namespaced classes like google.maps.Marker, google.maps.Map, etc.
>>> > >> > 3) Use maps.google.com/maps?file=googleapionly: This puts just >>> the >>> > >> > namespaced classes in your page.
>>> > >> > We introduced namespaces along with the common loader to encourage >>> a >>> > >> > more unified way of coding against Google AJAX APIs, but we kept >>> the >>> > >> > prefixed "G" classes to not confused the current developers. >>> However, >>> > >> > currently it's difficult to write extensions (like the LocalSearch >>> > >> > Control) for developers, as one has to search the DOM for both a >>> > >> > prefixed class or a namespaced class, and then use the >>> appropriate >>> > >> > class. To make it easier for developers to create extensions that >>> work >>> > >> > independent of loading technique and to encourage more developers >>> to >>> > >> > use the common AJAX namespace, we will soon introduce a change >>> that >>> > >> > will also pass down the namespaced class with technique #1.
>>> > >> > Let me know if you have any concerns or questions.
>>> > >> > - pamela
>>> > >> This feels like a coincidence of timing... >>> > >> I was just thinking I might want a GClientLocation or would that be >>> > >> GLoader.clientLocation >>> > >> or something of that sort.
|
