http://google.com/jsapi source

[Kai Hendry]

Is there an un-obfuscated or unminimized version of http://google.com/jsapi
somewhere?

Closest I could find is:
http://groups.google.com/group/Google-AJAX-Search-API/browse_thread/thread/4fa47c151ddbb39f/0ebb943ec6c987ef?lnk=gst&q=source#0ebb943ec6c987ef

I'm more interested in the loader.


On http://code.google.com/p/google-ajax-apis/ you do advertise an
Apache2 license.

I am interested in re-using the loader paradigm to load (third party)
device APIs by URL.


Kind regards from sunny Surrey,

[Ben Lisbakken]

Kai --

At this point we're not releasing the source of jsapi.  Also the code.google.com address is specifically just for an issue tracker.  We have another repository at http://code.google.com/p/google-ajax-examples/ where we have open source sample code.

Basically any sample code or wizard code that we write to use our services is free for anyone to reuse.  The code we have to provide the services, however, is not open.

Is there some other way I could help you?  Maybe you are interested in the general techniques that jsapi uses?

Regards from sunny Mountain View,
Ben

[Kai Hendry]

Why do Google use:

window.foobar = {}; rather than var foobar= {};

Another example:
http://code.google.com/p/google-ajax-examples/source/browse/trunk/presidentialwithgears/gears_init.js

Unsure why you need to latch onto the http://code.google.com/p/doctype/wiki/WindowObject


Did you experience any issues with your JSAPI WRT to Firefox 3 from
Firefox 2?

I plan to start a free software JS loader project. Or could someone
please point out some existing ones I could leverage?
Code I have so far: http://api.webvm.net/loader.js

Kind regards,

p.s. For Web devs who use VIM see http://wiki.whatwg.org/wiki/IDE

[jgeerdes [AJAX APIs "Guru"]]

The reason Google uses window.foobar instead of var foobar is because
the loader is contained inside of an anonymous function to facilitate
the centralizing of all Google libraries and, if you include
{nooldnames:1} in the load() calls, minimize DOM pollution. So when
they want to make something available in the global scope, they have
to explicitly attach it to the window object. Otherwise, it would be
confined to the scope of the anonymous function.

Jeremy R. Geerdes
Effective website design & development
Des Moines, IA

For more information or a project quote:
http://jgeerdes.home.mchsi.com
jgee...@mchsi.com

If you're in the Des Moines, IA, area, check out Debra Heights
Wesleyan Church!

[Kai Hendry]

http://bp.yahooapis.com/2.0.6/browserplus.js

Yahoo doesn't seem to use the window object and they seem a lot more
"open" than Google.

Besides the window object probably won't be available in non-browser
environments.