> while this might help one-file js libs like prototype how is it going to > work for libs that load other files themselves? > > you can have the same dojo version in two different components, but they can > include different modules... > > the problem is that those libs try to load their dependencies themselves, > and since they dont always implement includeonce logic we might be sol even > if we do filter on a common id.
Well, if you read the comments in that JIRA issue, I'm asking for people to try to help out finding a good solution. I haven't found the answer yet, but I believe that we should have something better (but additionally/ optionally) than what we have now for common libraries. A simple solution would be to have a project that just ships all the deps on such a JS project, but I don't get a fuzzy feeling about that. Another direction could be names you can register (/resources/yui) and where component libraries can register their root classes for resolving such dependencies. But that may be overengineered. Ideas? Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
