thanks
2009/12/4 Michael Geary
> It really makes little difference at all. jQuery makes an array of all your
> "ready" callbacks, and when the document is ready it loops through that
> array and calls each function. So other than that tiny bit of overhead, the
> net effect is exactly the same wh
It really makes little difference at all. jQuery makes an array of all your
"ready" callbacks, and when the document is ready it loops through that
array and calls each function. So other than that tiny bit of overhead, the
net effect is exactly the same whether you put all the code in one ready
fu
thanks to all
On 4 dic, 12:08, Michel Belleville
wrote:
> Basically, my advice would be :
>
> 1. first, load jQuery
> 2. then load jQuery extensions (UI, plugins)
> 3. then load your own domain-specific extensions (method declarations,
> etc.)
> 4. then load your page hooks (in a $
Basically, my advice would be :
1. first, load jQuery
2. then load jQuery extensions (UI, plugins)
3. then load your own domain-specific extensions (method declarations,
etc.)
4. then load your page hooks (in a $(function() { ... }) block so it
starts when the page is complete),
there's no problems with it...
as for "best", that completely applies to the situation, there is no
one, all-encompassing answer for that
On Dec 4, 10:35 am, coolf wrote:
> ok, thanks for the response.
> But what is the best, is it good to have more than a "documen.ready" ?
> it doesn't bring pr
ok, thanks for the response.
But what is the best, is it good to have more than a "documen.ready" ?
it doesn't bring problems?
On 4 dic, 11:33, Andreas Möller wrote:
> > Hello i'm new here, Is it posible?
>
> Yes, it is.
>
> Best regards,
>
> Andreas
6 matches
Mail list logo
