That was perfect. Thanks.
On 5/19/08 8:00 AM, "Ariel Flesler" <[EMAIL PROTECTED]> wrote:
>
> //include first
>
> jQuery(function( $ ){
>// $ will be the first jQuery
>$('#bodyframe').corner('tr');
> });
>
> // include second
>
> You can also use jQuery.noConflict();
>
> Cheers
>
//include first
jQuery(function( $ ){
// $ will be the first jQuery
$('#bodyframe').corner('tr');
});
// include second
You can also use jQuery.noConflict();
Cheers
--
Ariel Flesler
http://flesler.blogspot.com/
On 19 mayo, 10:16, Jason Huck <[EMAIL PROTECTED]> wrote:
> Well, it's easy
Well, it's easy to detect whether jQuery is loaded using plain
javascript, but once you've determined that it's not loaded, getting
it loaded in the correct order (particularly so that you can still use
document.ready()) gets tricky. You could create a custom version of
jquery.js that looks like t
You should be able to use jQuery.noConflict() to restore $ to the
first instance of jQuery where the plugins are.
On May 18, 9:33 pm, Shelane <[EMAIL PROTECTED]> wrote:
> if you have this in this order, the plugin call won't work. it will
> give an error that the plugin function is not defined
>
Hey Jason,
I thought it made sense too - the explanation of why it happens.
Yes, it would be ideal if jquery were just added to the portal
templates. However, the developers don't have control over the portal
templates. They are strictly locked down, and there is no way the
manager of the port
That makes sense. jQuery is loaded, then extended by loading a plugin,
but then replaced with a fresh, unaltered copy of jQuery, all of which
takes place before document.ready(), where the (by then nonexistent)
plugin is finally called.
I would consider including the base jQuery file via a stub o
6 matches
Mail list logo
