hi igor, > if anyone has any better solutions im all ears. the problem is that the > components are encapsulated, so you can never count on any of them to > include the full version of any lib they depend on. and today unfortunately > these libs are so big that they come with multiple files - and on top of > that have all these dynamic loaders.
i know that maintaining such a lib isn't really doable. but why shouldn't libraries actually deliver the whole packages with them and set a common id on it - and it's wicket to decide which location came first? it's no problem of data-redundancy in the jars, but contributing more than once to the browser. --- jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
