Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 23, 2006 09:54 PM by Luis Abreu
Jan 26, 2006 12:16 AM|LINK
Jan 26, 2006 02:43 AM|LINK
It's really hard to say without seeing your code. It kind of looks like your tooltips library is initializing at some point using the ids on the page, but it's not expecting the page to change in a major way after it's initialized. Maybe this tooltip library
needs to be reinitialized after an Atlas update panel has been refreshed?
So I don't think it's a conflict as much as this other library not expecting the kind of stuff Atlas does (Atlas uses namespaces to minimize the chances of conflict). For tooltip, did you look at the popup behavior?
Jan 26, 2006 04:09 AM|LINK
Jan 26, 2006 07:45 AM|LINK
The new Atlas javscript definetly causing conflicts
I tried using script.aculo.us (http://script.aculo.us) with atlas, and i'm getting javscript errors too...
The script.aculo.us scripts just works fine
Jan 26, 2006 07:26 PM|LINK
Well, you could also say that script.aculo.us is causing conflicts ;). We really can't ensure compatibility with other libraries that act on a very fundamental level (like extending Object and Function). We use namespaces to avoid the risk of collision,
but there's really no way around the fundamental OOP stuff that we do. I think script.aculo.us relies on the prototype library that's similar to our atlasruntime.js and that's probably where the incompatibility really is.
I can see what scenarios would need such compatibility: using ASP.NET with UpdatePanel on the server and a third party library on the client, but I don't think there's a way we can ensure the compatibility with every other library out there.
Jan 26, 2006 10:13 PM|LINK
Jan 26, 2006 10:35 PM|LINK
How do you maintain compatibility between two libraries that essentially extend the *same* objects? Prototype is not a browser, and it's not a standard either. There is no official documentation that I could find, and we just can't look at the source code
for obvious legal reasons. From some of the unofficial documentation that's floating around on the web, I can confirm that it extends the same objects that Atlas is extending, like for example Array.
Asking for compatibility between Atlas and Prototype is like asking for compatibility between ASP and PHP. I don't see that happening. Sorry.
Jan 26, 2006 11:02 PM|LINK
Jan 26, 2006 11:20 PM|LINK
There sure is a lot of duplication of effort here but you should also know that the design decisions we have to put into Atlas are often far-reaching as there are many constraints that may not be initially visible and that may not exist for other frameworks
(like consistency with the .NET framework wherever possible, MSN using our stuff, etc.). So even if it was possible for us to stand on top of things like Prototype, it would probably not fit our needs.
While it may seem a little silly to say that we can't look at the source code whereas it's plain text that's downloaded by the browser, it doesn't matter from a legal standpoint. We just can't look at it, let alone use it. No more than we can use Reflector
on third party .NET libraries to look at their source code. The technical aspect of it does not matter.
I hope this clarifies.
Jan 27, 2006 04:05 AM|LINK