Hey Lee, Lee a écrit : > I am trying to include some atlas controls on the same page that I am > doing a Rico.Accordion. The problem is that if I do this, then the > tab control I am using disappears and all of my Rico stuff stops > working. If I comment out the src in of Rico or Prototype, then atlas > works. And conversely, if I comment out all atlas controls then all > of my Rico stuff works. I would appreciate any suggestions that > anyone may have.
I'm no Atlas expert, but I keep hearing it just breaks every other script around, for instance by extending Object.prototype, and also because stuff like atlascompat.js breaks W3C DOM behavior to make it behave more like MSIE's when in another browser. I hope I'm not spreading FUD here, I'm just repeating things I've been seeing time and again on this list. I was under the impression that Atlas had so many issues that most people went with AjaxPro.Net or some other alternative. But maybe that was back in .NET 1 time... You might want to do a quick scan on Atlas-related articles at, say, Ajaxian.com before committing further to this specific library. AJAX with .NET does not mandate Atlas... -- Christophe Porteneuve aka TDD [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
