I'm done checking everything in, sorry again about the spam, there are issues with the eol-style in the dojo code.
An overview of what I did: We now use dojo loading for all files except Zimbra files. (Those don't work with that system and we will remove them eventually anyway now that Kabuki is dead?) Dojo loading gets files and calls eval() on them. I had to make minor changes to every file and major changes to the google stuff to get them to work in IE as eval() there has some scoping issues. Xap.provides(), Xap.requires() and Xap.kwCompoundRequires() are wrappers around the Dojo calls of the same name. Those are used in a couple of places, for example xap.util.Character uses provides() and the things the use Character use requires() on it. Eventually everything should do the provides()/requires() stuff but I wanted to just put it in a few files as a test and to let people see if it looked OK or not. The bridge classes specified in xap/taghandling/plugin.xml are now loaded dynamically. After people get a chance to digest these changes, provide feedback, etc, if everyone is in agreement I (and anyone else inclined) can begin moving things over to use provides()/requires() and to use the proper xap.* package naming. Some of the doc produced by JSDoc is a bit screwed up, when I changed the constructor style it lost the ability to find the constructor without the @constructor tag, so I will try to make things nice again there. James Margaris
