I’ve spent a lot of time lately playing with Atlas & I’m enjoying working with it, despite the huge javascript payload. I wanted to incorporate some script.aculo.us effects into an Atlas page, and noticed this helpful post from huddletogether:
there seems to be a conflict between Scriptmanager and Scriptaculous
you need to place the Scriptaculous after the scriptmanager.
add the following lines of code to get it working:
<body>
<form id=”form1″ runat=”server”>
<atlas:ScriptManager ID=”sm1″ EnablePartialRendering=”true” runat=”Server” />
<script type=”text/javascript” src=”/js/prototype.js”></script>
<script type=”text/javascript” src=”/js/scriptaculous.js?load=effects”></script>
<script type=”text/javascript” src=”/js/lightbox.js”></script>
other html goes here
<body>
I figured there would probably be javascript conflicts (Atlas already uses prototype’s $ syntax). I wonder what else happens when intrepid ASP.NET coders want some fancy effects on their pages?
