Forums

Hi, I have a complex client application based on YUI. This application loads classes on demand without the possibility of knowing in advance what classes are going to be loaded nor the paths of those classes.

A short description of the code before you can see the example is that I load a BaseApp class (extending Y.Base), that class loads by configuration some other classes that are attached to the BaseApp as plugins. The problem is that after I load the classes on demand, the classes also have dependencies to YUI modules as well as local modules.

The problem is that when the second class is loaded, the dependencies are not working. If you switch between the first and the second the same result will happen, meaning that is not an issue of a problem in one of the classes.

The code is here: https://docs.google.com/document/pub?id=1J5VWSLPiNaBRIb1eP-LH_1GoGrYTNZdIqAzYahAIDSs

If I switch from yui 3.3 it will work but in YUI3.4 I will get the following result in mu console:

initializer: BaseApp base_app.js (line 11)
Loaded: pluginModule - PluginOne PluginOne.js (line 1)
Loaded: pluginModule - PluginTwo PluginTwo.js (line 1)
Loaded: WidgetOne widget_one.js (line 1)
yui: NOT loaded: WidgetTwo yui-min.js (line 11)

Any ideas?

IIRC, for custom modules to load requirements from the "requires" attribute in the module file (not in the YUI configuration object), you must declare them inside a group, not directly into the modules property.


Side note: using <DOCTYPE html> means you're not using XML, so you don't need to add a <?xml version="1.0"> tag before the doctype in that case.

By the way, thank you Juan for the side note!
(Soy un ex porteño)

That's not strictly true. Requirements for modules are added if the module is included in the markup at page load, or is executed before a Y.Loader request. But you are right in the general use case; module dependencies are not recalculated as the modules are loading.

This issue is covered by this ticket, and should be fixed for 3.5.0.