Hey folks,Perhaps this was on your radar already, but I didn't know that Google provides an API that serves the latest versions of various AJAX libraries, including YUI, from their somewhat fast content distribution network:http://code.google.com/apis/ajaxlibs/What is the AJAX Libraries API?
The AJAX Libraries API is a content distribution network and loading architecture for the most popular,
open source JavaScript libraries. By using the Google AJAX API Loader's
google.load() method, your application has high speed,
globaly available access to a growing list of the most popular, open source JavaScript libraries including:
jQueryjQuery UIPrototypescript.aculo.usMooToolsDojoSWFObjectYahoo! User Interface Library (YUI)Ext CoreNew!
Google works directly with the key stake holders for each library
effort and accepts the latest stable versions as they are released.
Once we host a release of a given
library, we are committed to hosting that release indefinitely.
The AJAX Libraries API takes the pain out of developing mashups in
JavaScript while using a collection of libraries. We take the pain out
of hosting the libraries,
correctly setting cache headers, staying up to date with the most
recent bug fixes, etc.
<script src="http://www.google.com/jsapi"></script><script> // Load jQuery google.load("jquery", "1"); // on page load complete, fire off a jQuery json-p query // against Google web search google.setOnLoadCallback(function() { $.getJSON("http://ajax.googleapis.com/ajax/services/search/web?q=google&v=1.0&callback=?", // on search completion, process the results function (data) { if (data.responseData.results && data.responseData.results.length > 0) { var results = data.responseData.results; for (var i=0; i < results.length; i++) { // Display each result however you wish alert(results[i].titleNoFormatting); } } }); });</script>
This looks quite nice but I also have to wonder whether it would add too
much overhead for us. Also, we would be dependent on the online Google
libraries unless we could include the whole library archive in the Campsite
package, but that would be also too much overhead for our Campsite package.
I see this more like a tool for the frontend, for the web designers; the
admin interface should not be dependent on anything outside the Campsite
package.
Mugur
On Wed, Sep 23, 2009 at 9:38 PM, wrote:
> Hey folks,
>
> Perhaps this was on your radar already, but I didn't know that Google
> provides an API that serves the latest versions of various AJAX libraries,
> including YUI, from their somewhat fast content distribution network:
>
> http://code.google.com/apis/ajaxlibs/
>
> What is the AJAX Libraries API?
>
> The AJAX Libraries API is a content distribution network and loading
> architecture for the most popular, open source JavaScript libraries. By
> using the Google AJAX API Loader's
> google.load() method, your application has high speed, globaly available
> access to a growing list of the most popular, open source JavaScript
> libraries including:
>
> - jQuery
> - jQuery UI
> - Prototype
> - script.aculo.us
> - MooTools
> - Dojo
> - SWFObject
> - Yahoo! User Interface Library (YUI)
> - Ext Core
> New!
>
> Google works directly with the key stake holders for each library effort
> and accepts the latest stable versions as they are released. Once we host a
> release of a given library, we are committed to hosting that release
> indefinitely.
>
> The AJAX Libraries API takes the pain out of developing mashups in
> JavaScript while using a collection of libraries. We take the pain out of
> hosting the libraries, correctly setting cache headers, staying up to date
> with the most recent bug fixes, etc.
>
>
>
>
>
>
what i like about this, is google versus yahoo... if they have the
*meta* mega abstraction layer, it might provide more long term
development stability?
possibly this is the moment where javascript / ajax has grown through
the ceiling. like php which once was meant to be a templating language.
today it has its own templating engine in php... possible javascript /
ajax is at that level?
all the best, micz
On Wed, 2009-09-30 at 11:48 +0300, Mugur Rus wrote:
> This looks quite nice but I also have to wonder whether it would add
> too much overhead for us. Also, we would be dependent on the online
> Google libraries unless we could include the whole library archive in
> the Campsite package, but that would be also too much overhead for our
> Campsite package.
>
> I see this more like a tool for the frontend, for the web designers;
> the admin interface should not be dependent on anything outside the
> Campsite package.
>
> Mugur
>
>
> On Wed, Sep 23, 2009 at 9:38 PM, wrote:
>
> Hey folks,
>
> Perhaps this was on your radar already, but I didn't know that
> Google provides an API that serves the latest versions of
> various AJAX libraries, including YUI, from their somewhat
> fast content distribution network:
>
> http://code.google.com/apis/ajaxlibs/
>
>
> What is the AJAX Libraries API?
>
> The AJAX Libraries API is a content distribution network and
> loading architecture for the most popular, open source
> JavaScript libraries. By using the Google AJAX API Loader's
> google.load() method, your application has high speed, globaly
> available access to a growing list of the most popular, open
> source JavaScript libraries including:
>
> * jQuery
> * jQuery UI
> * Prototype
> * script.aculo.us
> * MooTools
> * Dojo
> * SWFObject
> * Yahoo! User Interface Library (YUI)
> * Ext CoreNew!
>
> Google works directly with the key stake holders for each
> library effort and accepts the latest stable versions as they
> are released. Once we host a release of a given library, we
> are committed to hosting that release indefinitely.
>
> The AJAX Libraries API takes the pain out of developing
> mashups in JavaScript while using a collection of libraries.
> We take the pain out of hosting the libraries, correctly
> setting cache headers, staying up to date with the most recent
> bug fixes, etc.
>
>
>
>
>
>
>
>
>
Yes, it might provide long term development stability and yes, I would chose
Google any time over Yahoo or Ms. The problem is that you have to be online
ALL the time to access these libraries. If your Internet connection was
broken you have no way of accessing the admin interface. For me this would
be a huge problem, as it would not allow me to work on Campsite while I'm
not online. For a new user checking Campsite on his own laptop this could be
a problem too. Testing Campsite would also be dependent on the Internet
connection. So this would be quite limiting; no matter what you do: develop,
test, check - you MUST always have an Internet connection.
Mugur
On Wed, Sep 30, 2009 at 12:10 PM, Micz Flor wrote:
> what i like about this, is google versus yahoo... if they have the
> *meta* mega abstraction layer, it might provide more long term development
> stability?
>
> possibly this is the moment where javascript / ajax has grown through the
> ceiling. like php which once was meant to be a templating language. today it
> has its own templating engine in php... possible javascript / ajax is at
> that level?
>
> all the best, micz
>
>
> On Wed, 2009-09-30 at 11:48 +0300, Mugur Rus wrote:
>
> This looks quite nice but I also have to wonder whether it would add too
> much overhead for us. Also, we would be dependent on the online Google
> libraries unless we could include the whole library archive in the Campsite
> package, but that would be also too much overhead for our Campsite package.
>
> I see this more like a tool for the frontend, for the web designers; the
> admin interface should not be dependent on anything outside the Campsite
> package.
>
> Mugur
>
> On Wed, Sep 23, 2009 at 9:38 PM, wrote:
>
> Hey folks,
>
> Perhaps this was on your radar already, but I didn't know that Google
> provides an API that serves the latest versions of various AJAX libraries,
> including YUI, from their somewhat fast content distribution network:
>
> http://code.google.com/apis/ajaxlibs/
>
> *What is the AJAX Libraries API?* The AJAX Libraries API is a content
> distribution network and loading architecture for the most popular, open
> source JavaScript libraries. By using the Google AJAX API Loader's
> google.load() method, your application has high speed, globaly available
> access to a growing list of the most popular, open source JavaScript
> libraries including:
>
>
> - jQuery
> - jQuery UI
> - Prototype
> - script.aculo.us
> - MooTools
> - Dojo
> - SWFObject
> - Yahoo! User Interface Library (YUI)
> - Ext Core
> New!
>
>
> Google works directly with the key stake holders for each library effort
> and accepts the latest stable versions as they are released. Once we host a
> release of a given library, we are committed to hosting that release
> indefinitely.
>
> The AJAX Libraries API takes the pain out of developing mashups in
> JavaScript while using a collection of libraries. We take the pain out of
> hosting the libraries, correctly setting cache headers, staying up to date
> with the most recent bug fixes, etc.
>
>
>
>
>
>
>
good point, i didn't know that. one day we all will be online all the
time - if we want it or not, but if we want to cater also for lesser
connected areas, this would be a deal breaker.
On Wed, 2009-09-30 at 12:23 +0300, Mugur Rus wrote:
> Yes, it might provide long term development stability and yes, I would
> chose Google any time over Yahoo or Ms. The problem is that you have
> to be online ALL the time to access these libraries. If your Internet
> connection was broken you have no way of accessing the admin
> interface. For me this would be a huge problem, as it would not allow
> me to work on Campsite while I'm not online. For a new user checking
> Campsite on his own laptop this could be a problem too. Testing
> Campsite would also be dependent on the Internet connection. So this
> would be quite limiting; no matter what you do: develop, test, check -
> you MUST always have an Internet connection.
>
> Mugur
>
>
> On Wed, Sep 30, 2009 at 12:10 PM, Micz Flor
> wrote:
>
> what i like about this, is google versus yahoo... if they
> have the *meta* mega abstraction layer, it might provide more
> long term development stability?
>
> possibly this is the moment where javascript / ajax has grown
> through the ceiling. like php which once was meant to be a
> templating language. today it has its own templating engine in
> php... possible javascript / ajax is at that level?
>
> all the best, micz
>
>
>
>
> On Wed, 2009-09-30 at 11:48 +0300, Mugur Rus wrote:
>
> > This looks quite nice but I also have to wonder whether it
> > would add too much overhead for us. Also, we would be
> > dependent on the online Google libraries unless we could
> > include the whole library archive in the Campsite package,
> > but that would be also too much overhead for our Campsite
> > package.
> >
> > I see this more like a tool for the frontend, for the web
> > designers; the admin interface should not be dependent on
> > anything outside the Campsite package.
> >
> > Mugur
> >
> > On Wed, Sep 23, 2009 at 9:38 PM,
> > wrote:
> >
> > Hey folks,
> >
> > Perhaps this was on your radar already, but I didn't
> > know that Google provides an API that serves the
> > latest versions of various AJAX libraries, including
> > YUI, from their somewhat fast content distribution
> > network:
> >
> > http://code.google.com/apis/ajaxlibs/
> >
> >
> > What is the AJAX Libraries API?
> >
> > The AJAX Libraries API is a content distribution
> > network and loading architecture for the most
> > popular, open source JavaScript libraries. By using
> > the Google AJAX API Loader's google.load() method,
> > your application has high speed, globaly available
> > access to a growing list of the most popular, open
> > source JavaScript libraries including:
> >
> > * jQuery
> > * jQuery UI
> > * Prototype
> > * script.aculo.us
> > * MooTools
> > * Dojo
> > * SWFObject
> > * Yahoo! User Interface Library (YUI)
> > * Ext CoreNew!
> >
> > Google works directly with the key stake holders for
> > each library effort and accepts the latest stable
> > versions as they are released. Once we host a
> > release of a given library, we are committed to
> > hosting that release indefinitely.
> >
> > The AJAX Libraries API takes the pain out of
> > developing mashups in JavaScript while using a
> > collection of libraries. We take the pain out of
> > hosting the libraries, correctly setting cache
> > headers, staying up to date with the most recent bug
> > fixes, etc.
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>