Hi, This is a small list of (really) non-critical bugs found while using OAT alongside other libraries. This is all in the context of a "description.vsp" page so that can give you an idea on the features being loaded, etc ( var featureList = ["slidebar", "resize"]; )
1. I used another script called /mylibrary/loader.js and OAT went crazy. I assume it tries to figure out its own path by inspecting the "script" elements in the document and trying to match a source ending in "loader.js". In fact, if I renamed my "loader.js" to "xxxloader.js" the framework tried to load "xxxslidebar.js", etc. 2. Several issues arise when loading "jQuery Tools" and OAT, even with jQuery.noConflict() mode. Regards, A -- Aldo Bucchi @aldonline skype:aldo.bucchi http://aldobucchi.com/ PRIVILEGED AND CONFIDENTIAL INFORMATION This message is only for the use of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If you are not the intended recipient, please do not distribute or copy this communication, by e-mail or otherwise. Instead, please notify us immediately by return e-mail.
