Hi,
> Christof Donat wrote:
> > - either you need to do synchronous loading like JSON does or you need to
> > work
> > with callbacks as I do. Synchronous loading blocks the browser, callbacks
> > are
> > not understood by everyone.
>
> You mention that not everyone understands callbacks (maybe I read it
> wrongly). Well, it would also be true that not everyone understands
> JavaScript, and an even smaller number understand jQuery (however easy it
> may be, the missus just doesn't see the magic that I do).
I just thought of the recurring questions why te following won't work in
jQuery:
$('#myNiceElement').load('http://www.example.com/');
$('#thisElementWillBeCreatedByLoad').css({backgroundColor:'red'});
> Christof Donat wrote:
> > - to load all the scripts your page needs multiple HTTP-Requests are
> > necessary
> > which increases the overhead.
>
> While multiple HTTP-Requests do increase overall overhead, that is based on
> the assumption that the total sum of code loaded is the same as a normal
> page load (ie, the user loads all or nearly all the modules through their
> page interaction). I'll actually give this a bye though, because I'm not
> fully au fait with the performance statistics of multiple on-request HTTP
> requests, versus single all-in-one HTTP Requests.
I totaly agree with you that this is only a problem in case you would load all
the code anyway. As I wrote I use dynamic loading myself, because in my
projects the cons are really weak. In other projects this might be an issue.
Christof
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
