Hi,

you can simply add the prototype.ashx and core.ahsx where you want,
with scriptReplacement you can stop Ajax.NET to render the script
tags.

I'm currently in contact with the prototype.js authors to decide if I
move to prototype.js. The main problem is that I have some methods
implemented a little bit different, and maybe prototype.js must be
changed to this. If they don't want to do this we have to see what we
can do. One more example is the IFrame replacement for the
XMLHttpRequest which is missing in the prototype.js library.

You see, it is not a Ajax.NET problem, and it is not a prototype.js or
scritpaculous problem. Because in JavaScript you can define same
function names everywhere it is a problem.

Keep reading my blog and the Google group here to get informed if I
can move to prototype.js.

Regards,
Michael



On 5/23/06, panik <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> I managed to drill down untill I found the problem. In one of the
> scriptaculous scripts (namely effects.js), there's en Effect.Opacity
> class, that somewhere in it's initialization calls an
> element.getOpacity function.
>
> When I did include the AJAX.NET javascript codes (RegisterTypeForAjax
> (...)), that line went haywire. The getOpacity function was undefined
> on the element object. When I removed the AJAX.NET scripts, all went
> well.
>
> Now, before calling the getOpacity function, the initialization of the
> class calls the well-known prototype $ function like this: this.element
> = $(element);
>
> The AJAX.NET also has a $ function. Now both versions of that $
> function are similar, though they are different in some aspects of
> their inner code. But in essence the function $ is present twice.
>
> I now did one very ugly and quick fix: I renamd the $ function from
> scriptaculous to $SAC, and renamd all calls to that function in all the
> scriptaculous scripts.
>
> And all goes well.
>
> Removing the $ function from the scriptaculous scripts is no option, as
> the AJAX.NET scripts are included later in the page.
>
> Not that I don't really need a sollution now, but can we defined the
> location in the HTML code where the AJAX.NET scripts are included?
>
> cheers and I hope this will eventually help someone,
> v
>
>
> >
>


-- 
Best regards | Schöne Grüße
Michael

Microsoft MVP - Most Valuable Professional
Microsoft MCAD - Certified Application Developer

http://weblogs.asp.net/mschwarz/
http://www.schwarz-interactive.de/
mailto:[EMAIL PROTECTED]

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Ajax.NET Professional" 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/ajaxpro

The latest downloads of Ajax.NET Professional can be found at 
http://www.ajaxpro.info
-~----------~----~----~----~------~----~------~--~---

Reply via email to