Eric Miraglia <miraglia@yahoo- inc.com> writes:
> At present, the YUI Loader across instances will only load modules that
> for CSS files; YUI Loader instance knows only about the CSS files that
> it loaded itself.)
> Here's the definitive word from the component's author:
Hmm. So I can expect wasted bandwidth because of multiply-loaded CSS
files. But should I expect any other breakage?
I could probably make do with a single instance, but will I be
guaranteed that all my onSuccess callback functions will get called, or
would I need to worry about that myself?
Think of it this way: YUILoader is my main entry point for creating
widgets. I _always_ create and initialize them from a loader callback,
so that I can be sure that all their dependencies have been loaded. Is
this something that will work?
> On Jun 2, 2008, at 6:10 AM, Jan Rychter wrote:
>> Just checking: I use the YUILoader for lazy-loading of YUI libraries,
>> with actual widget configuration code placed in callback functions.
>> Should I expect any problems if there are multiple loader objects
>> created and running simultaneously? Will they work correctly,
>> e.g. will
>> they only load what hasn't been loaded yet?
>> I would expect them to work correctly, but I thought I'd check. If the
>> above isn't true, I'll need to create and manage a callback queue,
>> would be a pain.