I love this place.
Thanks so much everyone.
My coding practises just shifted :)
Steve
On Mar 25, 5:55 am, MorningZ wrote:
> To build on James reply
>
> Using more CDNs allow your user's browser to download more
> simultaneously
>
> http://developer.yahoo.com/performance/rules.html#cdn
>
> On
To build on James reply
Using more CDNs allow your user's browser to download more
simultaneously
http://developer.yahoo.com/performance/rules.html#cdn
On Mar 24, 2:33 pm, James wrote:
> I think the idea is that if many sites used the Google hosted script,
> and your visitor happened to visi
I think the idea is that if many sites used the Google hosted script,
and your visitor happened to visit one of them, it's probably already
in their browser cache, so your site will have one less file to load.
Google has servers all over the world, so it's unlikely the service
will be down, but it
Yup, I hear ya all and now understand the issue. Especially Sam's
point that upgrading automatically may break a function somewhere.
Thanks so much for the replies.
Much appreciated.
I guess the last question is "is there any advantage in linking to the
google hosted scripts rather than hostin
@Microbe, you could combine your single domain solution with @Steve's
Google Ajax library suggestion. Rather than linking directly to a
hosted Ajax library, you could link to a JavaScript file hosted by you
on a single domain. In that JavaScript file, call google.load
("jquery", "1.3.2"). When you
I totally agree with Sam don't blindly change working pages with
new versions! You're doing nothing but asking for trouble
On Mar 23, 5:59 am, Sam wrote:
> The risk with linking to a "latest" build is that something will break
> when the linked-to version of jquery changes. Imagine for i
The risk with linking to a "latest" build is that something will break
when the linked-to version of jquery changes. Imagine for instance
that you made heavy use of @selectors, and were running live with
these when the change was made from 1.2 to 1.3. Your site would break.
Such eventualities as t
You can link to the latest major number, for example
http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js
gets you 1.3.2; it will automatically update to the next 1.#.# version
when available.
http://ajax.googleapis.com/ajax/libs/jquery/1.2/jquery.min.js
Gets you 1.2.6 (the latest versio
Hi there,
You can change the url so that it always uses the latest 1.3.x
release ...
http://ajax.googleapis.com/ajax/libs/jquery/1.3/jquery.min.js
or even the latest 1.x release ...
http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js
--Karl
Karl Swedberg
www.englishru
Thanks for that, but if you use it, aren't you linking to a specific
version number?
Their example is "path:
http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js";
So what happens if right though my code I call that file and then
1.3.3 comes out?
You want want to try Google's AJAX library which hosts
the various JavaScript effects library (JQuery, Prototype, YUI,
Mootools)
for you:
http://code.google.com/apis/ajaxlibs/
Hope this helps!
On Mar 22, 12:31 am, Microbe wrote:
> Hey everyone,
>
> I use jquery on a number of sites (all on th
11 matches
Mail list logo
